Problem with WeatherSnoop 2.2.6

[JGTracy]

WeatherSnoop 2.2.6 does not work with Indigo 6.0.9 running on Mavericks. I get error messages like:

2014-01-29 15:59:35 WeatherSnoop Error exception in deviceStartComm(DavisWeather): invalid literal for int() with base 10: '0.0'
2014-01-29 15:59:35 Application WebServer client connected
2014-01-29 15:59:35 WebServer started on port 8176 -- digest authentication enabled

I had to switch to WeatherSnoop 3. All seems well now. Please note: WS 3 is not an upgrade from 2.x.x but a new program that must be bought all over again.

[jay (support)]

Is 2.2.6 a beta? I don't see it listed on their website yet.

(split into a separate topic)

[JGTracy]

I think 2.2.6 is a beta. The following statement was in an email response from the WS developer;

Code: Select all

There are issues with 2.2.4 and 2.2.5 on Mavericks. We've posted a preflight of 2.2.6 at <<snip>> which takes care of the Sparkle issue.

I presume the term "preflight" means "beta".

My disconnect between WS and Indigo occurred when I installed Mavericks so I assumed the problem was part of the "issues" mentioned, but maybe not. After installing 2.2.6 without getting the expected connection back, I noticed that I needed to start the server in WS preferences. This may have been the problem with the WS 2.2.4 version that I had been running. I did not go back and check, but I expect the int() versus real problem may have been an issue there also.

[jay (support)]

I've sent an email to them. It does appear that the value changed from an int to a float at some point - and my guess is that it's specific to the Davis weather station you're using since I can't reproduce it here with the station I have (not a Davis).

And, yes, his preflights are pre-releases (betas).

[boisy]

John,

Can you post the XML response to the 2.2.6 server? As I told Jay in email, I don't recall changing an integer type to a float, but obviously something is wrong.

[JGTracy]

Sorry. I'm running WeatherSnoop 3 now. The log file excerpt that I posted earlier is all I have on the error.

[jay (support)]

Well, I guess we'll just have to wait until the issue comes up with someone else. Thanks for the help.

[AlaskaDave]

I've been having issues with the plug-in (2.0.2) running WeatherSnoop Agent 2.2.6 on my MacMini. The plug-in does not respond when setting values for creating/troubleshooting a device. Bummer that previous owners of 2x can not upgrade at a discount. Is it confirmed that the WeatherSnoop plug-in requires WeatherSnoop 3x? My Mac is running 10.8.5.

[jay (support)]

WeatherSnoop 2 is still supported - at least, we didn't change anything in the plugin that would make it stop working. I just tested with 2.1.5 and it works fine. Oddly, when I do a check for updates it says 2.1.5 is the latest version.

I just downloaded 2.2.6 - it doesn't appear to be serving any data over HTTP (it just hangs when I try and hit it via the browser), so the problem is with 2.2.6 and not the plugin. I'll send them an email to see if we can figure out what's going on.

[boisy]

Hi,

I've verified that there is an issue with 2.2.6 and HTTP services for some agents. There isn't a workaround, and it will require an update. I'll try to get something out by the weekend.

[jay (support)]

Thanks for the update Boisy.

[boisy]

Well, I got to it sooner than I expected.

Please download the latest test build at http://www.weathersnoop.com/downloads/W ... tBuild.zip. This has the fix for the HTTP server issue as well as another bug fix and significant improvements in communicating with serial-based stations.

[jay (support)]

Great turnaround, thanks!

[boisy]

Just a follow-up:

I've reworked the pre-flight distribution a bit and updated the URL for WeatherSnoop 2. Get the latest at:

http://www.weathersnoop.com/downloads/W ... Flight.zip

And also, the "Check for Updates..." feature in the WeatherSnoop menu will continue to provide an avenue for updates.

[MountainEars]

How's about for preflight version 2.2.7 706? I just moved to a new computer, was asked to run this version, but Indigo doesn't seem to be able to talk to it. I have the HTTP publishing working, I can pull up the page, but the state for it in Indigo is showing Data Unavailable. Doesn't look like it is reporting issues in the event log.