yeah comming from fhem, so HA looks easy peasy to me
Another question.
After a reboot HA docker container got other internal 172 addresses and messed up the deconz integration!, sure i can edit the file like described here: Docker automatically allocated IPs getting messed up? - #22 by johnflorin
and put in the “core-deconz” in.
But like stated in the thead above, after update it’s got messed up again.
How do you handle this?
So nobody know?
Just open an terminal on HA an ping core-deconz. When you get an answer all is good.
Edit the 172 IP in the config file and replace it with core-deconz. Restart HA and you good to go.
Up until next Update!?
Are you running deconz as an addon or standalone?
As addon, set all up yesterday. All was working fine until the update today. The IP address of the container changed and HA core could not connect to the old one.
Anyone experiencing performance/stability issues with latest HA/deconz?
Symptoms that I’m facing since ~2 weeks, so I’m not sure if this is related to HA/OS/deconz, as all updates come more-less the same time:
2022-02-12 20:31:47 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall light.turn_off (c:ad79298f4149644096f5ef488b2bd5ec): entity_id=['light.library_1', 'light.library_2', 'light.library_3'], params=>
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/pydeconz/api.py", line 146, in request
return await self._request("put", path=field, json=data)
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 141, in request
return await self._request(
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 167, in _request
_raise_on_error(response)
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 264, in _raise_on_error
raise_error(data["error"])
File "/usr/local/lib/python3.9/site-packages/pydeconz/errors.py", line 59, in raise_error
raise cls("{} {}".format(error["address"], error["description"]))
pydeconz.errors.BridgeBusy: /lights/11/state/on Internal error, 951
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/pydeconz/api.py", line 146, in request
return await self._request("put", path=field, json=data)
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 141, in request
return await self._request(
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 167, in _request
_raise_on_error(response)
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 264, in _raise_on_error
raise_error(data["error"])
File "/usr/local/lib/python3.9/site-packages/pydeconz/errors.py", line 59, in raise_error
raise cls("{} {}".format(error["address"], error["description"]))
pydeconz.errors.BridgeBusy: /lights/11/state/on Internal error, 951
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/pydeconz/api.py", line 146, in request
return await self._request("put", path=field, json=data)
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 141, in request
return await self._request(
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 167, in _request
_raise_on_error(response)
File "/usr/local/lib/python3.9/site-packages/pydeconz/gateway.py", line 264, in _raise_on_error
raise_error(data["error"])
File "/usr/local/lib/python3.9/site-packages/pydeconz/errors.py", line 59, in raise_error
raise cls("{} {}".format(error["address"], error["description"]))
pydeconz.errors.BridgeBusy: /lights/11/state/on Internal error, 951
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/core.py", line 1648, in catch_exceptions
await coro_or_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1667, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 668, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 930, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 705, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 513, in async_handle_light_off_service
await light.async_turn_off(**filter_turn_off_params(light, params))
File "/usr/src/homeassistant/homeassistant/components/deconz/light.py", line 247, in async_turn_off
await self._device.set_state(**data)
File "/usr/local/lib/python3.9/site-packages/pydeconz/light.py", line 241, in set_state
return await self.request(field=f"{self.deconz_id}/state", data=data)
File "/usr/local/lib/python3.9/site-packages/pydeconz/api.py", line 159, in request
return await self.request(field, data, tries)
File "/usr/local/lib/python3.9/site-packages/pydeconz/api.py", line 159, in request
return await self.request(field, data, tries)
File "/usr/local/lib/python3.9/site-packages/pydeconz/api.py", line 162, in request
raise BridgeBusy
pydeconz.errors.BridgeBusy
seems to indicate that there is something wrong with the Conbee II stick performance? Any idea of what is ahppening here?
That means there is some queueing or waiting going on in the bridge, there is a command queue of ~20 and this can be filled if you turn off all devices at the same time. Pydeconz does a retry per command that gets this error.
That would be strange, really. Good example of situation when I noticed problem quite regualarly is in the morning (~6:30AM, when I get up and it still dark), I move from badroom to hall and light does not turn on or does it with delay (single bulb, not much load). So for sure there was no prior action (beside motion detection in bedroom, that does not trigger any action, sensor is installed for safety only). So I’d not expect any large queue of events being processed… To me it seems more like system ‘waking up’ after extended (few hours) break. Next time I enter hall (just few minutes later) and no problem with proper automation execution. Until recent updates system had no issues with processing all of the normal activities at house, I do not generate so big number of events to be handled, perhaps one every few seconds in the peak (unless system itself is busy with all sensors updates or so, but I think it is rather up to sensor to trigger update).
That’s what the error suggests, next step would be to look at the logs on Deconz side, but I have very limited knowledge of that myself.
Is this addon using the websocket (where Events gets pushed from deconz) rather than polling the api?
Thx
Yes the websocket is the primary source for state changes
Nice, thx!
I tried to reset system (full reboot, including EWXi host) and ‘restart’ of Conbee itself (disconnectinr/reconnecting to computer), but this did not helped… maybe the frequency of errors decreased a bit, but did not dissapeared. What is confusing is that it was introduced with recent updates (HA, OS, Deconz), previously I had some responsivness issues but less frequent and never throwing such errors in the log 
I tried to check phoscon logs, but these seems not to contain any usefull info. Perhaps something can be found on deconz side, but I did not found any access to logs…
It can still be an issue on deconz side. Unless you’ve added a lot of extra integrations on ha side i think it is on deconz side. Next step for you would be to get help viewing logs on deconz side and see if something is misbehaving
I did not found any way to see deconz logs… but I made some experiments. What I come up with I changed source routing in deconz configuaration to be controlled on application level (if I properly understand how it work), setting up minimal LQI to 150 and number of hops to 5:
Since then everything started to work fine again and no more errors in the log. Anyone else used this option? Any experience or suggestions for finetuning?
is this issue maybe the same?
I got the problem since 1-2 weeks.
Thanks for the hint with the log - but I cannot find a option to show/save the log at settings-integrations…?
Sorry, I have no input as on the configuration aspects on deCONZ side
I use source routing since 6 months and it’s rock solid. I configured 4 hops and LQI 160 so nearly the same parameters
Thanks! For me it is just few days, but no single glitch since change 
I’ll probably play a bit with LQI and number of hops to squeeze the most from the system, but already very glad from this move.
I believe, the hops depends a little from the amount of plugged devices (routers) you have.
I do have much more than sensors or switches and so most of my links never touched more than two devices until the target point. So I went with 4 in order to be safe.
