Skip to content
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

Open
Thepyropc opened this issue Aug 29, 2022 · 2 comments
Open

Need help with sensor being unavalible #68

Thepyropc opened this issue Aug 29, 2022 · 2 comments

Comments

@Thepyropc
Copy link

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:

  • platform: weatheralerts
    state: IL
    zone: "013"
    county: "043"`

2022-08-29 10_55_49-Developer Tools – Home Assistant
i have a lot more code if needed just didnt wanna make it to long on my initial post.

@jlverhagen
Copy link
Collaborator

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 weatheralerts in the home-assistant.log file for clues and post those log entries here if you can't figure out what's going on based on the log entries.

@Technodad
Copy link

I'm seeing similar symptoms - the update.weatheralerts_update entity continuously shows shows "Unavailable" in the history and the last Logbook entries are:

Weatheralerts update  turned off
10:47:18 PM - 12 hours ago
Weatheralerts update  became unavailable
10:47:16 PM - 12 hours ago

My configuration.yaml:

sensor:
  platform: weatheralerts
  state: ME
  zone: 23
  county: 31

The relevant log entries, from right after a restart:

config grep weather home-assistant.log   
2022-09-05 09:58:18.213 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration weatheralerts which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant   
2022-09-05 09:58:57.560 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform weatheralerts is taking over 10 seconds.   
2022-09-05 09:58:57.878 WARNING (MainThread) [custom_components.weatheralerts.sensor] [TimeoutError]  
2022-09-05 09:58:58.105 WARNING (MainThread) [homeassistant.components.sensor] Platform weatheralerts not ready yet: None; Retrying in background in 30 seconds   
2022-09-05 09:59:36.288 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform weatheralerts is taking over 10 seconds.   
➜  config

There currently is an active alert for Maine zone MEZ23:

<feed
xmlns = 'http://www.w3.org/2005/Atom'
xmlns:cap = 'urn:oasis:names:tc:emergency:cap:1.1'
xmlns:ha = 'http://www.alerting.net/namespace/index_1.0'
>
<!-- http-date = Mon, 05 Sep 2022 07:24:00 GMT -->
<id>https://alerts.weather.gov/cap/me.php?x=0</id>
<logo>http://alerts.weather.gov/images/xml_logo.gif</logo>
<generator>NWS CAP Server</generator>
<updated>2022-09-05T03:24:00-04:00</updated>
<author>
<name>[email protected]</name>
</author>
<title>Current Watches, Warnings and Advisories for Maine Issued by the National Weather Service</title>
<link href="https://alerts.weather.gov/cap/me.php?x=0"/>
<entry>
<id>https://alerts.weather.gov/cap/wwacapget.php?x=ME12640BDD2710.FloodWatch.12640BED2340ME.GYXFFAGYX.7e0474e490c53559659c8b946e9efb12</id>
<updated>2022-09-05T03:24:00-04:00</updated>
<published>2022-09-05T03:24:00-04:00</published>
<author>
<name>[email protected]</name>
</author>
<title>Flood Watch issued September 05 at 3:24AM EDT by NWS</title>
<link href="https://alerts.weather.gov/cap/wwacapget.php?x=ME12640BDD2710.FloodWatch.12640BED2340ME.GYXFFAGYX.7e0474e490c53559659c8b946e9efb12"/>
<summary>.A frontal zone draped across the Northeast is combining with a very humid airmass to produce a heavy rainfall threat across the region today into Tuesday with multiple rounds of rain and embedded thunderstorms. Training and slow movement of showers combined with pockets of convectively enhanced rainfall rates may lead to flooding in the Watch area.</summary>
<cap:event>Flood Watch</cap:event>
<cap:effective>2022-09-05T03:24:00-04:00</cap:effective>
<cap:expires>2022-09-06T08:00:00-04:00</cap:expires>
<cap:status>Actual</cap:status>
<cap:msgType>Alert</cap:msgType>
<cap:category>Met</cap:category>
<cap:urgency>Future</cap:urgency>
<cap:severity>Moderate</cap:severity>
<cap:certainty>Possible</cap:certainty>
<cap:areaDesc>Androscoggin; Central Interior Cumberland; Coastal Cumberland; Coastal York; Interior Cumberland Highlands; Interior York; Kennebec; Knox; Lincoln; Sagadahoc; Southern Oxford</cap:areaDesc>
<cap:polygon></cap:polygon>
<cap:geocode>
<valueName>FIPS6</valueName>
<value>023001 023005 023011 023013 023015 023017 023023 023031</value>
<valueName>UGC</valueName>
<value>MEZ012 MEZ018 MEZ019 MEZ020 MEZ021 MEZ023 MEZ024 MEZ025 MEZ026 MEZ027 MEZ033</value>
</cap:geocode>
<cap:parameter>
<valueName>VTEC</valueName>
<value>/O.NEW.KGYX.FA.A.0002.220905T0724Z-220906T1200Z/
/00000.0.ER.000000T0000Z.000000T0000Z.000000T0000Z.OO/</value>
</cap:parameter>
</entry>
</feed>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants