Network unreachable is either your local network/ISP having issues OR NWS having issues on their end.
1 Like
The log says network unreachable to api.weather.gov. Yet if i pop that imto my browser, it comes back as status āokā.
I even spun up another instance of HA in another location, and get the same problem, so its not only on my network. Dont know what to make of this.
You said itās still only an intermittent issue correct?
If yes (or I guess in any case) itās going to be hard to really narrow down the problem.
Iām not seeing it here so it canāt be an integration problem.
Maybe try with a different set of location settings that doesnāt use the same NWS field office. So try something far away from where you are. If that works then you know itās an issue with the local NWS and not just the NWS API in general.
Its renains unavailable for several hours, then for very short periods, comes back. A few nights ago it came back for several hours. I have tried a few random locations with the same result.
For the hell of it, would yoy try the one im using for my location? PAC089,PAZ055.
I sure will. Iāll let you know what I see.
Well, after 3 days of testing I can say that I havenāt had any issues reaching the NWS API for your location.
If youāve had any issues since then that definitely rules out the NWS as the failure. It has to be on your end somehow.
Are you using any sort of VPN?
Strangly enough, about the same time as you answered with this, it stabilized. Its been working since thank god. I hate not having that working. Thanks for checking on that for me.more importantly, thanks for that add on! Possibilities are endless.
1 Like
Any tried to use telegram for the push messages? Messages dont seem to pass for some reason. No error or anything, message just wont push thru. Pushover seems to work ok.
I use pushover, pushbullet and the mobile app and that all works for me.
Iāve never tried telegram so I donāt know anything about it.
Hello all- quick question as I am re doing my HA instance right now, I have always used a integration called weatheralerts which worked fine but the project does not seem to be active anymore, still works fine as far as I can see but eventually it will stop if no one is maintaining it. Anyway I have come upon this project and have been trying to read up on it! Seems to be similar and obviously active. Could anyone that may be familiar with both integrations give me a quick comparison. TIA.
Thereās no comparison. This is the one you want. I used both for a long while and found this is the best option with an active group providing each other with working options. Plus, ongoing updates have been made with user feedback.
Thanks. So no issues with automation triggers using this? Currently the way I use weatheralerts, (after adjusting some of the YAML) based on a specific event like a tornado warning /alerts it will set off actions. I assume this is no issue and I could do the same?
Yes, look for recent examples in this thread and on the GitHub page. Iāve used it in the past to trigger Google Home speakers and turn lights on red for tornado warnings.
3 Likes
yes.
look here for examples:
Thanks so much!
1 Like
@finity Iāve thrown in a PR thatāll help with the Weather.gov API being flaky and re-triggering some peopleās alert automations.
Did the most recent change not solve that problem?
Itās never happened for me so I couldnāt really test it but it seemed as if it should work.
This change makes the availability no longer flip the sensor unavailable.
Thereās a few other quality of life changes too, I outlined them in the PR 
1 Like
what does the SensorEntityDescription do?
This is how HA ādescribesā sensors internally.
Itās so you can use less of the @property bits by using self._attr_<stuff>
1 Like