Ambient Weather Station: Failed setup, will retry: One or more namespaces failed to connect

[grantalewis]

The problem

Integration fails to load after restarting, reloading, etc. Data is correctly reporting from the weather station to Ambient phone app, to pwsweather.com, and to Weather Underground.

What version of Home Assistant Core has the issue?

core-2024.11.3

What was the last working version of Home Assistant Core?

core-2024.11.3

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Ambient Weather Station

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ambient_station

Diagnostics information

home-assistant_ambient_station_2024-12-02T11-50-35.114Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-12-02 06:42:33.580 INFO (MainThread) [aioambient] WebSocket connection accepted with {'sid': 'yoETGPXFeOSkcT8gAZLZ', 'upgrades': [], 'pingInterval': 25000, 'pingTimeout': 20000}
2024-12-02 06:42:33.581 INFO (MainThread) [aioambient] Engine.IO connection established
2024-12-02 06:42:33.581 INFO (MainThread) [aioambient] Sending packet MESSAGE data 0{}
2024-12-02 06:42:34.582 INFO (MainThread) [aioambient] Sending packet CLOSE data None
2024-12-02 06:42:34.582 INFO (MainThread) [aioambient] Engine.IO connection dropped
2024-12-02 06:42:34.584 INFO (MainThread) [aioambient] Exiting write loop task
2024-12-02 06:42:34.584 WARNING (MainThread) [aioambient] Server sent close packet data None, aborting
2024-12-02 06:42:34.584 INFO (MainThread) [aioambient] Waiting for write loop task to end
2024-12-02 06:42:34.584 INFO (MainThread) [aioambient] Exiting read loop task
2024-12-02 06:42:34.885 INFO (MainThread) [aioambient] Connection failed, new attempt in 4.98 seconds
2024-12-02 06:42:39.869 INFO (MainThread) [aioambient] Attempting WebSocket connection to wss://rt2.ambientweather.net/socket.io/?api=1&applicationKey=[redacted]&transport=websocket&EIO=4
2024-12-02 06:42:40.412 INFO (MainThread) [aioambient] WebSocket connection accepted with {'sid': 'pK6nHOqgW__Oqdn3AN33', 'upgrades': [], 'pingInterval': 25000, 'pingTimeout': 20000}
2024-12-02 06:42:40.412 INFO (MainThread) [aioambient] Engine.IO connection established
2024-12-02 06:42:40.413 INFO (MainThread) [aioambient] Sending packet MESSAGE data 0{}
2024-12-02 06:42:41.414 INFO (MainThread) [aioambient] Sending packet CLOSE data None
2024-12-02 06:42:41.414 INFO (MainThread) [aioambient] Engine.IO connection dropped
2024-12-02 06:42:41.416 INFO (MainThread) [aioambient] Exiting write loop task
2024-12-02 06:42:41.416 WARNING (MainThread) [aioambient] Server sent close packet data None, aborting
2024-12-02 06:42:41.417 INFO (MainThread) [aioambient] Waiting for write loop task to end
2024-12-02 06:42:41.417 INFO (MainThread) [aioambient] Exiting read loop task

Additional information

No response

[home-assistant]

Hey there @bachya, mind taking a look at this issue as it has been labeled with an integration (ambient_station) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ambient_station can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign ambient_station Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

ambient_station documentation
ambient_station source
_{^{(message by IssueLinks)}}

[pwhiteside80]

Started having this issue as well yesterday

[rallysport67]

Same problem here started yesterday mid afternoon US Eastern Standard Time. Failed Setup, will retry: One or more namespaces failed to connect. I generated a new API key and used that but still having the same issue. (Don't know if API is related or not but it is something I did try.) Thanks

[LegacyR]

Also started seeing this issue sometime yesterday. I think API is still working as I also kick my weather station to pwsweather.

[ki4hrg]

Same issue here. Initially thought it was an Ambient-side issue but data is uploading normally elsewhere and a check using the Ambient API explorer doesn’t return any issues (though I was only checking that the api was up, not any configuration issues with the integration on HA’s side).

[jterfehr2000]

Same issue, seems to have started in last 12-24 hours. Failed setup, will retry: One or more namespaces failed to connect

[netguy101]

Happening for me as well starting sometime mid-yesterday. Deleted Hub and attempted to re-add without success.

[astroman68]

Same here, started failing last night @ approx 6pm est. I too use the API in other places (Waybar weather integration) on three other devices that all continue to work.

[imonitormyhome]

Same here, same time frame, testing with the browser returns updated API data.

[larryb31]

Same issue

[jeddytier4]

Logger: aioambient
Source: runner.py:189
First occurred: 8:57:38 AM (12 occurrences)
Last logged: 9:02:29 AM

Server sent close packet data None, aborting

This was logged alongside the failure. I did enable debug logging, but haven't found any additional details in the logs.

[jcnoetzel]

Ditto with the issue and no help in the logs

[bobbeims]

+1

[petergreenorust]

Same issue in Sweden!

[HAhokie94]

Same issue.

[ultrathew]

Same issue. Started in the last 12 hours or so. In the US. All is working locally and on Ambient Weather’s site and app.

[Dhostetter]

Same issue after rebooting this morning. Site and app still working fine.

[vanyacooper]

Same issue here. I did notice Ambient Weather now has a premium subscription service pop-up that I had to click through in case that is related.

[infinitytec]

Same here, started failing last night @ approx 6pm est. I too use the API in other places (Waybar weather integration) on three other devices that all continue to work.

Interesting, because for me it quit working at about 6 PM CST.

[bobbeims]

I have another app that uses the AWN API that also appears to be failing: my Rachio sprinkler controller. There’s no debug interface in that app such that I can see an error log, but the sprinkler failed to apply a freeze skip even though the temp was below freezing all night.

So the issue may be in the AWN service rather than the HA integration.

[infinitytec]

I just set up the Ambient Weather Network integration (which grabs the publicly-available data from a station) and that one works. I set it to my weather station as well.

[grantalewis]

I have another app that uses the AWN API that also appears to be failing: my Rachio sprinkler controller. There’s no debug interface in that app such that I can see an error log, but the sprinkler failed to apply a freeze skip even though the temp was below freezing all night.

So the issue may be in the AWN service rather than the HA integration.

FWIW, I also have a Rachio -- a Gen 2 Rachio-31DDF8. It's currently working fine with Home Assistant.

[bobbeims]

FWIW, I also have a Rachio -- a Gen 2 Rachio-31DDF8. It's currently working fine with Home Assistant.

Sorry for the confusion. I didn’t mean that Rachio integration with Home Assistant is not working. I meant the integration from my Rachio account to the AWN servers appears to have failed, too.

Folks who don’t live in a rural area like I do probably never fiddle with that integration.

[mnneely]

I’ll add to the pile of people having the same issue. I had to restart HA for another update, and after restarting, the namespace error popped up for this integration.

[petep0p]

same issue here. I'm only a week or so into HA, so i assumed it was something i did. nuked my whole system and started over but no dice.

notably, my API key for AmbientCWOP does not appear to have any issue; station is currently reporting there. that service does not require an application key, so if it's a key problem, then it would seem to be related to the application key rather than the API key.

edit: just for sh*ts and giggles, created a new application key and did not mention HA in the notes. it did not solve anything.

edit: running latest update on Home Assistant Green

[carltonsisk]

Same issue as well

[scotte]

Like everyone, same problem on my setup.

[warnmar10]

Ditto: Started yesterday about 4 PM CST. The data is collected and passed to ambientweather.net, it shows up on the console, only homeassistant is choking.

[astroman68]

I just set up the Ambient Weather Network integration (which grabs the publicly-available data from a station) and that one works. I set it to my weather station as well.

I just went ahead and switched to this. Pulls the exact same information and I don't need keys to make it work. The only difference I see is it updates slightly slower. Looks like about 5 minute data pulls and that is good enough for me. I didn't even have to edit my cards (at least in my case) everything just started populating again. There will be some sensors you will have to enable that are disabled by default if you are using them on any of your cards.

[astroman68]

Same here, started failing last night @ approx 6pm est. I too use the API in other places (Waybar weather integration) on three other devices that all continue to work.

Interesting, because for me it quit working at about 6 PM CST.

Correction. It stopped for me at exactly 7:05:44 PM EST on the 1st.