-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need help with sensor being unavalible #68
Comments
If you have quotes on the zone and county numbers in your weatheralerts yaml configuration, try removing the quotes and just leave the 3 digit numbers, restart Home Assistant, and see if that fixes the issue. This can also happen when Home Assistant is restarted during a period when the weather.gov weather alert API is experiencing an extended outage. The weatheralerts integration tries several times to connect during Home Assistant startup and will eventually fail if it can't connect to the weather.gov weather alert API. In that case, you'd have to wait until the weather.gov API is responding normally, and then restart Home Assistant. There should be some indication in the home-assistant.log file about what may be preventing the integration from properly initializing. If the above instructions don't work, see if you can find references to |
I'm seeing similar symptoms - the update.weatheralerts_update entity continuously shows shows "Unavailable" in the history and the last Logbook entries are:
My
The relevant log entries, from right after a restart:
There currently is an active alert for Maine zone MEZ23:
|
So i am not sure why my sensor is not working it constantly just says unavailable as a status. any ideas?
`# weather Alerts Haccs Pt 1
#url https://alerts.weather.gov/
sensor:
state: IL
zone: "013"
county: "043"`
i have a lot more code if needed just didnt wanna make it to long on my initial post.
The text was updated successfully, but these errors were encountered: