When I got my new computer, I downloaded SRT. When I tried to log-in, SRT couldn't connect to my server. I waited a few hours, and then I restarted my computer. SRT has worked great since that time. I think that it was a problem with Dish. I hate going to their website. SRT is so much nicer to use. Thanks!
If you wouldn't mind, what was the problem? I can include it in the error message.
"Pat"
Sep 22, 2:36 PM
I got it to work. Please disregard my previous message. Thanks.
"Pat"
Sep 22, 10:55 AM
I just got a new computer. I downloaded srt, but when I try to log-in, I get this error message: "Could not connect to your dns. Check your firewall and internet connection." I'm online and I turned my firewall off. I still couldn't log-in. I have Dish. Thanks.
"Rick"
Aug 21, 9:04 PM
I've installed the new version. Dish is always changing things. Thanks again.
Alright, I've pushed up v1.4.172, which should "fail correctly" in the event the usage can't be read. I'll keep looking into why exactly that issue occurs, but I'm pretty sure it's just a Dish thing...
"Rick"
Aug 21, 3:52 PM
Thanks for all your help. I appreciate it.
"Rick"
Aug 21, 3:49 PM
OK....I did what you asked. I don't mind doing whatever it takes to solve the problem. I really like SRT. Thanks!
Thanks for that. Unfortunately, the secondary system is getting the same "ATTRIBUTE ERROR E11" message in place of a number for the Any Time value, so it looks like the meter is just being "spotty". I'll add some code to prevent this problem from displaying as a "0", though, as it should simply fail to update the usage. You may want to try sending usage requests less often (say every hour or two) to see if that improves the issue. I'll get a new version out to fix the "0" thing ASAP, though. Sorry again!
Ah, it's the old "ATTRIBUTE ERROR E11" message. If you wouldn't mind doing the same thing again (downloading the installer at the same location and updating SRT with it [new version should be v1.4.171.2], running it and clicking the notice), I can see if there's some issue with the secondary meter reading code which is used when that error shows up... Sorry to make you do this twice, I didn't expect it to be using the fallback code.
