core: Since update to 2023.1 all Shelly 2nd generation devices are no longer responding
The problem
Since Update to HA 2023.1 all of my 2nd gen Shellys are no longer available in HA. But i can access them via Web Browser means they are still connected to WLAN
What version of Home Assistant Core has the issue?
2023.1
What was the last working version of Home Assistant Core?
2022.12
What type of installation are you running?
Home Assistant OS
Integration causing the issue
shelly
Link to integration documentation on our website
https://www.home-assistant.io/integrations/shelly
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: homeassistant.config_entries
Source: config_entries.py:1133
First occurred: 06:53:03 (5 occurrences)
Last logged: 08:56:22
Config entry 'Außensteckdose Waschraum' for shelly integration not ready yet: DeviceConnectionError(DeviceConnectionError(TimeoutError())); Retrying in background
Logger: homeassistant.config_entries
Source: components/shelly/init.py:274
First occurred: 06:51:44 (2 occurrences)
Last logged: 06:51:44
Error setting up entry Shelly-Router for shelly
Error setting up entry Außensteckdose Garage for shelly
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aioshelly/common.py", line 74, in get_info
async with aiohttp_session.get(
File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 1138, in aenter
self._resp = await self._coro
File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 466, in _request
with timer:
File "/usr/local/lib/python3.10/site-packages/aiohttp/helpers.py", line 721, in exit
raise asyncio.TimeoutError from None
asyncio.exceptions.TimeoutError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aioshelly/rpc_device/device.py", line 136, in initialize
self.shelly = await get_info(self.aiohttp_session, self.options.ip_address)
File "/usr/local/lib/python3.10/site-packages/aioshelly/common.py", line 83, in get_info
raise error from err
aioshelly.exceptions.DeviceConnectionError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/shelly/init.py", line 112, in async_setup_entry
return await _async_setup_rpc_entry(hass, entry)
File "/usr/src/homeassistant/homeassistant/components/shelly/init.py", line 274, in _async_setup_rpc_entry
await device.initialize()
File "/usr/local/lib/python3.10/site-packages/aioshelly/rpc_device/device.py", line 169, in initialize
await self._disconnect_websocket()
File "/usr/local/lib/python3.10/site-packages/aioshelly/rpc_device/device.py", line 190, in _disconnect_websocket
self._unsub_ws()
File "/usr/local/lib/python3.10/site-packages/aioshelly/rpc_device/wsrpc.py", line 447, in
return lambda: self.subscriptions.pop(ip)
KeyError: '192.168.33.1
Logger: homeassistant
Source: components/shelly/bluetooth/init.py:54
First occurred: 07:00:33 (1 occurrences)
Last logged: 07:00:33
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aioshelly/rpc_device/device.py", line 275, in call_rpc
return await self._wsrpc.call(method, params)
File "/usr/local/lib/python3.10/site-packages/aioshelly/rpc_device/wsrpc.py", line 347, in call
resp = await self._rpc_call(method, params, timeout)
File "/usr/local/lib/python3.10/site-packages/aioshelly/rpc_device/wsrpc.py", line 379, in _rpc_call
resp: dict[str, Any] = await call.resolve
aioshelly.exceptions.DeviceConnectionError: <aioshelly.rpc_device.wsrpc.RPCCall object at 0x7f95e90f10>
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/shelly/coordinator.py", line 405, in _async_update_listener
await self._async_run_connected_events()
File "/usr/src/homeassistant/homeassistant/components/shelly/coordinator.py", line 512, in _async_run_connected_events
await self._async_connect_ble_scanner()
File "/usr/src/homeassistant/homeassistant/components/shelly/coordinator.py", line 535, in _async_connect_ble_scanner
await async_connect_scanner(self.hass, self, ble_scanner_mode)
File "/usr/src/homeassistant/homeassistant/components/shelly/bluetooth/init.py", line 54, in async_connect_scanner
await async_start_scanner(
File "/usr/local/lib/python3.10/site-packages/aioshelly/ble/init.py", line 83, in async_start_scanner
await device.script_start(ble_script_id)
File "/usr/local/lib/python3.10/site-packages/aioshelly/rpc_device/device.py", line 239, in script_start
await self.call_rpc("Script.Start", {"id": script_id})
File "/usr/local/lib/python3.10/site-packages/aioshelly/rpc_device/device.py", line 281, in call_rpc
raise DeviceConnectionError from err
aioshelly.exceptions.DeviceConnectionError
Additional information
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 23 (12 by maintainers)
Commits related to this issue
- Reject the WiFI AP IP when considering to update a shelly config entry from zeroconf fixes #85180 — committed to bdraco/home-assistant by bdraco a year ago
- Reject the WiFI AP when considering to update a shelly config entry from zeroconf (#85265) Reject the WiFI AP IP when considering to update a shelly config entry from zeroconf fixes #85180 — committed to home-assistant/core by bdraco a year ago
- Reject the WiFI AP when considering to update a shelly config entry from zeroconf (#85265) Reject the WiFI AP IP when considering to update a shelly config entry from zeroconf fixes #85180 — committed to home-assistant/core by bdraco a year ago
- Reject the WiFI AP when considering to update a shelly config entry from zeroconf (#85265) Reject the WiFI AP IP when considering to update a shelly config entry from zeroconf fixes #85180 — committed to rlippmann/core by bdraco a year ago
- Reject the WiFI AP when considering to update a shelly config entry from zeroconf (#85265) Reject the WiFI AP IP when considering to update a shelly config entry from zeroconf fixes #85180 — committed to SplinterHead/core by bdraco a year ago
Thank you all for your excellent support! I can confirm 2023.1.1 fixed the issue.