doubleohwhatever

Nope no changes. I switched to another WB station and then back to the one I usually use and that fixed the problem. It's as if the one value just got stuck. I haven't noticed it happening since but I also don't use the climate module for anything other than the temperature anymore.

I haven't had that particular issue but I've experienced other issues. For example, about a month ago I discovered that several of the plants in the yard were looking rather poor. It turned out that the "Rain Today" value was stuck at two inches and the sprinklers weren't being turned on. I honestly don't have a clue whether it's a bug in the climate module where data gets "stuck" or if it's an issue with the data provided by weather bug (I'd guess the latter). I just don't use the climate module for anything but temperature anymore. I've never had an issue with that data being incorrect.

Ooh, now that's an idea. The ISY could grab an RSS feed periodically and load variables with the data. For example: <?xml version="1.0" encoding="ISO-8859-1" ?> variable1 value1 temp 74 humidity 69 Alternatively, variables could be loaded with data via a rest api. Something like this: X.X.X.X/rest/set/variable-name/value/ I think that would be an excellent feature to have. I still think it would be a good idea to allow us to set a custom rss feed for the weatherbug module though. I have no clue what the ISY code is like but that should be a fairly simple and quick feature to add. You'd need a function to make sure the required data can be obtained from the feed supplied (test the feed on saving changes after enabling the custom feed, etc) and perhaps a checkbox making the user confirm that they know it's an advanced feature and they know what they're doing. The test function would prevent any bad data from getting into the ISY system and the checkbox would allow you to take a hands-off approach towards support for the feature (just point users to a demo template). An alternative solution would be to allow us to provide an xml feed in the exact same format used for the /rest/climate feed. The fields provided by our custom xml feed would override the weatherbug data. Any fields not included in our xml feed would be pulled from weatherbug. Whatever is easiest to implement gets my vote.

Weatherbug chose to use RSS instead of a custom API. Therefore they have no claim on the format since RSS uses a standard XML format. The only thing you can't include in a duplicate feed is the phrase "weatherbug" and their images. So basically just strip out everything but the weather data fields and you're good to go. I can whip up a 100% legal to use template if you'd like.

Ah, gotcha. How about allowing us to set a custom RSS feed then? You could either create a demo feed that we could use as a template or require that we provide a feed in the weatherbug format. I think that would satisfy the needs of the more advanced users without requiring a lot of work on your end.

I'd love to see this as well since I own several davis stations. However, I think integrating with Weather Underground would be even better as that would eliminate the need to integrate with different weather stations directly.