My Shelly Wall Display was always well integrated. Now it was suddenly no longer accessible. I have already deleted it, reset it and tried to add it again. However, now I get the error: already_in_progress Here is the log message:
Logger: homeassistant.config_entries
Quelle: config_entries.py:637
Erstmals aufgetreten: 9. Februar 2025 um 09:48:39 (7 Vorkommnisse)
Zuletzt protokolliert: 9. Februar 2025 um 09:54:11
Error setting up entry Shelly Wall Display Mario for shelly
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 637, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/shelly/__init__.py", line 121, in async_setup_entry
return await _async_setup_rpc_entry(hass, entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/shelly/__init__.py", line 262, in _async_setup_rpc_entry
await device.initialize()
File "/usr/local/lib/python3.13/site-packages/aioshelly/rpc_device/device.py", line 198, in initialize
await self._connect_websocket()
File "/usr/local/lib/python3.13/site-packages/aioshelly/rpc_device/device.py", line 211, in _connect_websocket
await self._init_calls()
File "/usr/local/lib/python3.13/site-packages/aioshelly/rpc_device/device.py", line 325, in _init_calls
self._parse_dynamic_components(all_pages)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aioshelly/rpc_device/device.py", line 565, in _parse_dynamic_components
item["key"]: {**item["config"], **item["attrs"]}
~~~~^^^^^^^^^
KeyError: 'attrs'
I’m not sure what the original problem was. In my case the Shelly Wall Display itself is working, except I am not able to display a HA dashboard on the display. This occurred after update to fw 2.3.4. (20250212-115015/2.3.4-a71e59c7) De HA integration still works, the device is still visible and I can operate the built in switch with HA. But the HA dashboard fails to load, presents a white screen. Tried reload the HA server configuration, reboot, factory reset but no luck.
Here some log info:
[2025-02-24 20:33:13.824][HomeAssistant] HA discovery started
[2025-02-24 20:33:14.031][Generic] Found HA service: Thuis at null:0
[2025-02-24 20:33:14.061][HomeAssistant] HA discovered: http://192.168.188.32:8123
{location_name=[B@cecf09f, base_url=[B@c2d15ec, external_url=null, internal_url=[B@c686db5, uuid=[B@8e20c4a, version=[B@339f7bb, requires_api_password=[B@ecba4d8}
[2025-02-24 20:33:18.826][HomeAssistant] HA discovery stopped
[2025-02-24 20:33:20.980][HomeAssistant] ?? item is checked, it’s instance is {“name”:“Thuis”,“scheme”:“http”,“address”:“192.168.188.32”,“port”:8123,“path”:“/”,“query”:“”}, the instance is configured, but I will not process it. (Insert Ryan Raynolds’ ‘But why’ meme here)
(the last line is also part of the log
My problem is not solved by updates of HA. I have the latest updates on HA installed, since yesterday even on beta. Please help, thank you!
I managed to solve the problem. I enabled ADB and connect to the Wall Display. I did not change anything as far as I know. But logging into the Wall Display and running the deamon probably solved the problem. The other possibility is changes to my wifi network; I upgraded one of my AP’s so probably the Wall Display and/or Home Assistant changed subnet.
ich habe auch das Problem, dass der Homeassistant Bildschirm am Walldisplay weiss bleibt. Na Neustart des Displays ist es manchmal wieder da…nach einiger Zeit wieder weiss.
I have the same problem… the walldisplay shows nothing anymore, it is trying to load the dashboard but stops immediately… tried factory reset, restart and also disconnect power from the display… also a downgrade of homeassistant was no successfull…
I had the same issue (Wall Display 1, gen 2; 2.3.6-66e97e33; HA 2025.4.4) and was able to resolve it once I allowed the WallDisplay through the firewall. When I re-enabled the fw and restarted the display, the white screen reappeard. Also, disabling the Shelly Cloud seems to have fixed the issue, i.e. no cloud and firewall blocking internet access.
