I guess the device is not properly supported or only partially paired of something
It originates from this deconz/pydeconz/models at 9e9b1de1ac0c4f3c71190e643d927bbb09f01b8e · Kane610/deconz · GitHubinit.py#L159
Nothing that can be done on integration side though
but its coming from the zigbee usb stick itself i think? its an official deconz model v1
If i look in diagfile, i dont see any unknown devices, only the conbee1
Aah ok it’s the stick. It’s still a bug on deconz side though. I think there is an issue reported on it
ok, i just ignore for now then 
Are you sure it reports power monitoring?
You can try open up deconz searching for sensors or lights if it has only been partially paired.
Else it’s probably not fully supported and you should put up a request for device support
I have the Conbee II stick on a Raspberry Pi 4. I want to update the firmware
But the update is reported as succesfully but it still shows the old firmware.
What do I wrong?
And it shows that the update is available (so it is not installed)
When I restart the system or addon I see in the log:
07:41:07:447 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26720700.bin.GCF
07:41:07:448 GW firmware version shall be updated to: 0x26720700
FW upgrades from add on always fail. In fact it fails in majority of cases when soert dockerized or virtualized instance of deconz is installed. Even deconz itself recognized tis and in newer versions of software this option is removed. If you want to update FW the best way is to use Windows or Linux machine with deconz (or minimal install install just for update) installed. This way USB ports are accessible directly on OS level, without any additional virtualization layer in between and everything works fine. Whole process is described here.
Thanks it worked on a Windows pc.
Hi folks, I used deconz for a long time, and then recently whilst changing my Raspbee over to a different Rpi W2, I decided to test out zigbee2mqtt. The interface is wonderful, and pairing is simple. The UI is a cut above deconz…
BUT I’ve found some lights now to be unreliable! I have to press ON several times in HA for the light to come on. I never had that issue with deconz, and frankly it seems wrong that it should be broken on one and not the other. FWIW the lights are LED strips off a few Tradfri drivers.
I know I know functionality is more important than UI sugar, but still, if I can get away with not having to rebuild and re-pair everything with deconz that would be nice. Maybe I’m asking the wrong crowd, but also maybe someone here has had a similar experience 
This is the wrong thread to ask for Zigbee2MQTT support. I hope it works out for you.
Sure man 
I’m not asking for support.
There’s a high chance that someone in 3.5k messages has had a similar experience, and if that’s not you, then great for you.
I have added recently some hue dimmers to the Conbee II stick for some custom functionallity.
Before this I had only aqara battery devices connected to the stick and some other battery devices (door/windows sensor/motion/scene switch).
Also I have a lot of Hue lights connected to the Hue Bridge. I was always thinking that the Hue lights also repeated the signal for the devices that were connected to the Conbee stick.
But what I have read is that it are 2 seperate zigbee networks and that they don’t repeat the signals to the different networks only in there own network.
So I have added also an Ikea repeater to the conbee stick to have a better zignee network.
The Hue dimmers that I have added are new and have almost full battery. But what I noticed is that when I press the dim buttons on 1 Hue dimmer the lights goes to red (of the dimmer).
This is the graph of the Zigbee network:
You see that the Hue Dimmers had automatically seen the Ikea Repeater and send their signal to them.
But I have no knowledge about the numbers of the lines you see in the graph. It seems to me that the aqara battery devices are all better without the repeater than the Hue Dimmers with the repeater?
Hi!
Recently, I tried to get external encrypted access to my HA working, using the Duck DNS Add-on. I reversed the changed I’d made when I found that both internal and external access were not possible for some reason. Immediately after this, devices via deCONZ were greyed out in HA and the integration displayed an error. The Phoscon UI is still accessible. The deCONZ application through VNC isn’t.
I tried:
/config/.storage/core.config_entries to the one displayed in Phoscon.This got rid of the “greyedoutness” and the error on the integration page, but when I try to turn on or off a light, after a few seconds an error appears “Failed to call service light/turn_on.” In the error log, I found this:
Logger: homeassistant.components.websocket_api.http.connection
Source: components/deconz/light.py:234
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: February 17, 2023 at 16:28:16 (6 occurrences)
Last logged: 11:48:43
[2628862328]
[2620692200]
[2628768672]
[2620713808]
[2634037208]
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 142, in request_with_retry
return await self.request(method, path, json)
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 167, in request
response: dict[str, Any] = await self._request(
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 194, in _request
_raise_on_error(response)
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 225, in _raise_on_error
raise_error(data["error"])
File "/usr/local/lib/python3.10/site-packages/pydeconz/errors.py", line 73, in raise_error
raise cls(
pydeconz.errors.BridgeBusy: 901 /lights/5/state/on Internal error, 951
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 142, in request_with_retry
return await self.request(method, path, json)
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 167, in request
response: dict[str, Any] = await self._request(
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 194, in _request
_raise_on_error(response)
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 225, in _raise_on_error
raise_error(data["error"])
File "/usr/local/lib/python3.10/site-packages/pydeconz/errors.py", line 73, in raise_error
raise cls(
pydeconz.errors.BridgeBusy: 901 /lights/5/state/on Internal error, 951
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 142, in request_with_retry
return await self.request(method, path, json)
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 167, in request
response: dict[str, Any] = await self._request(
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 194, in _request
_raise_on_error(response)
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 225, in _raise_on_error
raise_error(data["error"])
File "/usr/local/lib/python3.10/site-packages/pydeconz/errors.py", line 73, in raise_error
raise cls(
pydeconz.errors.BridgeBusy: 901 /lights/5/state/on Internal error, 951
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 200, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1787, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1824, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 680, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 968, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 720, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 571, in async_handle_light_on_service
await light.async_turn_on(**filter_turn_on_params(light, params))
File "/usr/src/homeassistant/homeassistant/components/deconz/light.py", line 234, in async_turn_on
await self.api.set_state(id=self._device.resource_id, **data)
File "/usr/local/lib/python3.10/site-packages/pydeconz/interfaces/lights.py", line 174, in set_state
return await self.gateway.request_with_retry(
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 155, in request_with_retry
return await self.request_with_retry(method, path, json, tries)
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 155, in request_with_retry
return await self.request_with_retry(method, path, json, tries)
File "/usr/local/lib/python3.10/site-packages/pydeconz/gateway.py", line 158, in request_with_retry
raise BridgeBusy
pydeconz.errors.BridgeBusy
config_entries again, but to the same result.Anyone got any ideas to try, avoiding having to completely reset the Conbee stick? Would be much appreciated! Thank you.
Hello all!
Another month and another release of Home Assistant so here comes another release log on Phoscon forum for the HA deCONZ integration
Here are the changes coming with Home Assistant 2023.3.0
Nearly no action from me at all on the Home Assistant front, new role at work has left me brain drained in the evening , hoping to be back doing stuff shortly as I get more into it. This release fixes some python related issues, no new features…
I’ve gotten requests to buy me a coffee, I’m on Github Sponsors if you appreciate my work.
Cheers!
/Robban
For feature requests of the integration post an issue at pydeconz github
Can Transition block other commands?
Since beginning of this year (2023) I cannot switch_off some IKEA Tradfri bulbs anyore. I am using deCONZ add-on and HASSOS. Everything worked fine before. Now I found out that it is probably related to the transitions.
Below automation (not complete for clarity reasons) runs every 5 minutes and changes brightness and color temp with a transition of 300 seconds (5 minutes). So the lights are constantly and very smoothly changing over time. This worked very well and the transitions are invisible to me.
trigger:
- platform: time_pattern
minutes: /5
action:
- service: light.turn_on
data:
entity_id: "{{ template that get some light ids }}"
brightness: "{{ states('sensor.cl_brightness') | int }}"
kelvin: "{{ states('sensor.cl_color_temp') | int }}"
transition: "300"
initial_state: true
mode: single
The issue is that some of the bulbs that have this automation cannot be switched off anymore since early this year. The only way to switching off is powering off and on the lights and then I can control them again using HA. Also restarting HA did sometimes help. However after some time (some minutes?) it didn’t work any more.
Today I changed the transition time in this automation to a much shorter time and I was able to switched off the lamp.
Could it be that while a transition is running no other commands can be done, or is it more complex, as I have exactly 5 minutes transition time and trigger again after 5 minutes. As there is some processing time, each new transition time comes before the previous has ended, things will not work anymore?
To test that, I change the transition time to 245 seconds (4minv, 45 sec). So far things work much better. My question is now, is there some kind of queuing in HA, deCONZ, Ikea bulb, or Zigbee which was recently introduced that can cause commands to be dropped or only to be executed later? Or something else that might explain what I am encountering here?
devices via deCONZ were greyed out in HA and the integration displayed an error. The Phoscon UI is still accessible. The deCONZ application through VNC isn’t.
For anyone with the same issue: I found my solution here:
https://community.home-assistant.io/t/fix-ip-autoupdate-for-deconz-with-conbee-ii/405616/5?u=in_theory
After looking into this weird behavior a bit more, I found that I cannot switch off the TRADFRI bulb E27 WS globe clear 806lm bulbs when a transition is still running, however when I change the color temperature first (without a transition time) and then switch off the bulb, it works. If I change the brightness, I still cannot switch off the bulbs. Only when changing color temp it works. So far I only have seen this with these IKEA bulbs, so it might be an IKEA issue.
So my workaround is shown in below script, adding a color temp change first.
sequence:
- service: light.turn_on
data:
kelvin: 2100
target:
entity_id:
- light.ikeabulb1
- light.ikeabulb2
- service: light.turn_off
target:
entity_id:
- light.ikeabulb1
- light.ikeabulb2
data: {}
Hi.
I’m having trouble with some custom generated ddf files. It works with Jeedom & Deconz api seems to gives correct result on the problematic device endpoint ( ZHAPower )
I get correctly the Current and Power, but the Voltage entity is not generated.
Deconz Api:
{
"config": {
"on": true,
"reachable": true
},
"etag": "983f704e6e23a8dcd1d77ce403bc4304",
"lastannounced": "2023-03-07T19:34:50Z",
"lastseen": "2023-03-08T11:36Z",
"manufacturername": "LiXee",
"modelid": "ZLinky_TIC",
"name": "Linky",
"state": {
"current": 14,
"lastupdated": "2023-03-08T11:36:41.068",
"power": 3066,
"voltage": 224
},
"swversion": "4001-0011",
"type": "ZHAPower",
"uniqueid": "00:15:8d:00:06:38:e1:3c-01-0b04"
}
I don’t see what could be wrong here.
Edit: ok nothing is wrong. The missing properties are attributes. I wasn’t aware of those.
A bit boilerplaty to get attributes as sensor but I got it
after about 4years of perfect running my conbee ii has decided to stop working today
i done the home assistant 2023.03.6 update this morning all was good, up until 10hours later the zigbee just dropped off stopped working.
i rebooted home assistant and still same, unplugged it moved it to another usb port still the same
it starts up then says fatal error then shuts down.
ive even downgraded back to 2023.03.5 and still does the same, i also had a supervisor update today around 4pm but the deconz packed up around 1.30pm according to the doorbell sensor on home assistant
any ideas?
22:23:26:786 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2122275-if00 / serialno: , ConBee II
[22:23:27] INFO: Service restart after closing
[22:23:27] INFO: Starting VNC server (local/yes)...
[22:23:27] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
2023/03/23 22:23:27 [notice] 119#119: signal 15 (SIGTERM) received from 114, exiting
2023/03/23 22:23:27 [notice] 1664#1664: exiting
2023/03/23 22:23:27 [notice] 1664#1664: exit
In exit
2023/03/23 22:23:27 [notice] 119#119: signal 17 (SIGCHLD) received from 1664
2023/03/23 22:23:27 [notice] 119#119: worker process 1664 exited with code 0
2023/03/23 22:23:27 [notice] 119#119: exit
Closing socket listening at 127.0.0.1:5901
s6-svwait: fatal: supervisor died
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
I’m having exactly the same issue. The Deconz plugin failed today and now it won’t start. I’ve reverted to backups, used different ports, and I’m getting very similar error messages.
I’ve noticed that the Phoscon website is also down.
Does anyone have any ideas what is causing it as I can’t control my lights or heating at the moment!