your router is the default dns.
172.30.32.0/23 is the hassio subnet in docker, in which all addons including deconz are running. everything is as it should be.
I just did the update of the Deconz add-on to 5.3.5. After reading the changelog, it was actually a downgrade though?
However, now HASS is not able to connect to any of the DeconZ entities anymore, while in Phoscon they are all there and work. So something is wrong with the latest update of the add-on and it breaks it connection somehow to HASS (integration still shows up and is not removed).
On Github seems Iâm not the only one experiencing this?
Iâve rebooted the HASS server in itâs entirety as well, but the entities in HASS do not connect back and show as unavailable.
Only error I see in the log so far:
Logger: homeassistant.helpers.service
Source: helpers/service.py:423
First occurred: 5:24:57 PM (2 occurrences)
Last logged: 5:32:12 PM
Unable to find referenced entities light.attic_light_5, light.attic_light_6, light.attic_light_7, light.attic_light_8
Unable to find referenced entities cover.window_covering_device_18, cover.window_covering_device_19
In the Supervisor log I do see the following (Docker IP of Deconz):
20-06-04 16:06:47 ERROR (SyncWorker_9) [asyncio] Unclosed connection
client_connection: Connection<ConnectionKey(host='172.30.33.1', port=8099, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None)>
How can I best troubleshoot to provide some more useful info?
Itâs a quite urgent matter because now all my zigbee lights and devices are not working with HASS in the house 
which are almost all the lights I haveâŚ
me neither. Have not resolved the issue but I have the same problem
1 Like
My deconz addon sometimes just stops running. It have happened once every week the last 3 weeks. I just start the addon and everything works just perfect. Running Home assisstant 114.3. Any idea to why and how to fix?
Itâs indeed a bug, my add-on stops too
HI! I have some problem with a newly connected Xiaomi motion sensor.
general setup: Hassio in Raspberry Pi 4 using a SSD.
It was working before migrating on bootable SSD. recovering the configuration I had problems with all sensors and lights.
Using a USB calbe between PI and Conbee II the connections work again.
Only my Xiaomi motion sensor makes trouble: I deleted it and reconnected (which worked).
Status changes are visible within Deconz.
Hassio says it cannot connect:
I tried to update the devices (integration -deconz-update) but no changeâŚ
Any suggestions from anyone?
hello
ive problems with my Sonoff ZBMINI. i read, that the problem is solved with beta 2.10.x.
installed is 2.09. how can i upgrade deconz to 2.10beta on my HA System (Raspberry4) ?
hi,
just had a power failure and afterwards hassio isnât able anymore to load the deconz integration. Errors are:
Logger: homeassistant.setup
Source: setup.py:162
First occurred: 00:10:23 (1 occurrences)
Last logged: 00:10:23Setup failed for custom integration deconz: Unable to import component: cannot import name âLinkButtonNotPressedâ from âpydeconz.errorsâ (/usr/local/lib/python3.9/site-packages/pydeconz/errors.py)
Logger: homeassistant.config
Source: config.py:454
First occurred: 00:10:25 (1 occurrences)
Last logged: 00:10:25
Invalid config for [automation]: Integration âdeconzâ does not support device automation triggers. Got OrderedDict([(âhomeassistantâ, OrderedDict([(âauth_providersâ, [OrderedDict([(âtypeâ, âhomeassistantâ)])])])), (âloggerâ, OrderedDict([(âdefaultâ, âinfoâ)])), (âpython_scriptâ, {}), (âdefault_configâ, {}), (âhttpâ, OrderedDict([(âssl_certificateâ, â/ssl/fullchain.pemâ), (âssl_keyâ, â/ssl/privkey.pemâ)])), (âttsâ, [OrderedDict([(âplatformâ, âgoogle_translateâ)])]), (âgroupâ, {}), (âautomationâ, [OrderedDict([(âidâ, â1578252647726â), (âaliasâ, âTurn the light on when motion is detectedâ), ('des⌠(See /config/configuration.yaml, line 25).
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: homeassistant
Source: custom_components/deconz/config_flow.py:229
Integration: deconz
First occurred: 00:10:31 (1 occurrences)
Last logged: 00:10:31Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File â/usr/src/homeassistant/homeassistant/components/hassio/discovery.pyâ, line 102, in async_process_new
await self.hass.config_entries.flow.async_init(
File â/usr/src/homeassistant/homeassistant/data_entry_flow.pyâ, line 205, in async_init
flow, result = await task
File â/usr/src/homeassistant/homeassistant/data_entry_flow.pyâ, line 232, in _async_init
result = await self._async_handle_step(flow, flow.init_step, data, init_done)
File â/usr/src/homeassistant/homeassistant/data_entry_flow.pyâ, line 335, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File â/config/custom_components/deconz/config_flow.pyâ, line 229, in async_step_hassio
self.bridge_id = normalize_bridge_id(discovery_info[CONF_SERIAL])
TypeError: âHassioServiceInfoâ object is not subscriptable
Updated all components, but the error still persists 
- Phoscon-GW 2.15.03 / 21.4.2022 26720700
- HA-Core 2022.5.4
- HA-Supervisor 2022.05.2
- HA OS 8.0
Any hint how to solve this issue?
If youâre using the Deconz addon, make sure the correct usb device is still being used in the add on configuration.
Some users have had this problem following the HAOS 8.0 upgrade.
Uuups my failure⌠Due to a previous issue I had to use a patched version of deconz as custom component. The power loss and restart of the system caused an update of some other components to which my custom component isnât compatible anymore.
Luckily the original issue in deconz is fixed in the meanwhile and anything works like a charm again 
1 Like