Well I have tried everything I can, rinse, repeat, repeat, rinse, and everything in between and it still does not refresh. If I create a rule I can get it to refresh.
EDIT: Error seems to have gone away. Don't see any refresh still.
@thomas.c.howard I wanted to let you know that the error has gone away. The refresh seems to be working but it is at a 5 min. interval and not the 1 min. it is set to.
1 Like
Good to hear. This could be a limitation of the Ambient Weather device. Example: wind updates every 5 seconds (per configuration) but temperature updates every five minutes...
Ok great! Thanks for all your help.
I have fixed some issues and added many attributes to the Ambient Weather Device.
I moved the refresh rate from the parent to the child device is the which is the proper place to have it.
If you want to try it out Hubitat-Ambient-Weather/BETA at master · sgrayban/Hubitat-Ambient-Weather · GitHub
I am getting the same refresh issue, is there updated code, the GitHub link above seems to be dead.
Thanks
Matt
The GitHub link in the post above yours is not the driver that’s discussed in the rest of this thread.
Try the link to the driver thread referenced further above, and then the GitHub link in that thread.
Edit: also I wonder how many user accounts scott grayban has in this forum 
.
I updated the driver and app code and it is still not refreshing, should the app and driver be uninstalled then re-added or is this a known issue.
Thanks
Matt
This seems to be a server side issue. Ambient API hasn't been refreshing since the beginning of the stay at home orders. I'm guessing there's something wrong on their server and no one around to fix it.
I use this alternate driver and it hasn't been working for the last two weeks either.
The above appears to actually be his regular account, which I believe that he requested be anonymized and more or less deactivated after fallout from a misunderstanding with me. Sorry, everyone? 
His Inovelli account (both here and there) appears to have had the same done to it, presumably by Inovelli's own request, as I assume that the employee they dismissed, apparently for treating people in the exact way I warned him about in both public and private messages to no avail, was him. That I swear I did not have anything to do with. 
(I should also publicly state that I have never had anything against him and think his contributions to the community have been a net positive and would welcome him back if he chooses to do so personally.)
2 Likes
I have successful polls from the Ambient servers (using my driver) as of this morning. Including a manual refresh just to confirm. The date matches and the data seems accurate to our weather outside.
Of course I never got a response from Ambient about some way to "test" them or get a more detailed message to provide to users if their servers were offline. Their Facebook group does not mention anything up front about the server problems anymore. So maybe they finally got this fixed?
I will watch mine today too see if it refreshes on it's own.
Thanks
Thanks for clarifying, Robert. I noticed some of that discussion here you mentioned but wasn’t aware Innovelli had taken action against one of their employees as described in your link to their forum.
@Quantumchaos your best bet when having issues with a community-developed driver or app is actually to follow the advice mentioned above:
Since every community driver can be a little different, if the developer has a release thread for their driver, posting in that thread both increases the likelihood of the dev seeing your question in the first place, and also saves others’ time from trying to figure out which driver is even being discussed.
In your case, I think it’s still unclear whether you’re using @thomas.c.howard’s driver or @snell’s.
I got a few socket puppets here 
1 Like
