Posted a PR that solves the service issue. https://github.com/home-assistant/home-assistant/pull/12067
@Robban, so far my things works pretty good. I have one suggestion which i never got to make in my module. A service that can be called in automations so that it refreshes the items from deConz. In my case some lights get’s Powered off so if i restart HASS in a point where the light are not on then they won’t be shown in HASS until it get’s restarted. I think it would be nice to have a service that i can call from automation on a interval that refreshes the entites from deConz.
2 Likes
Can you check if your devices generate a web socket event like ‘added’ or similar? Then it would behave the same as adding new devices which I’ve planned to support
So I’m not sure if this is the best place to ask this, but I’m interested in replacing my Xiaomi Gateway with a Conbee Stick, but I would like to know how the latency of when a sensor is triggered to it updating in HASS is using deCONZ and Conbee.
In particular I have a number of Aqara Human Body Sensors that are on busy doorways and the current method of using the Xiaomi Gateway has about a 2 minute reset time once the motion sensor is triggered. This makes it basically unusable to detect people coming through the doorway if they are within 2 minutes of each other. Is the Conbee and deConz better?
That is probably a configuration issue with your motion detector, normally you can change how long it should keep high.
I know people change that value for hue and trådfri motion sensors
According to another thread, there is no way to change it, the best you can do is to manually change the code to get HA to poll the gateway every 5 secs instead of every 30 secs (default). The problem is that the motion sensor only updates the gateway every minute or so and there is no guarantee that HA and the gateway are polling are in sync, so HA could miss the update.
That’s why I want to know if this Conbee + deCONZ setup is a better alternative
Sorry I can’t answer that since I don’t have one of those sensors. I like deconz but I don’t know if it will magically fix the behavior or not. Maybe you can create an issue in their GitHub and ask this question, they should be able to answer on the implementation of deconz.
I have a working Docker container for Conbee, which has replaced my virtual machine. I’m sure it can be useful for someone. 
See https://hub.docker.com/r/joch/deconz/ for instructions.
Does it also work to upgrade the firmware?
Not sure, since I’m on the latest version right now, but I’ll check once an update is out.
Nice job! I’ll give it a try right now.
Update: Migrated my config from my ubuntu server by copying all the files in /home/pi/.local/share/dresden-elektronik/deCONZ/ to a folder on my docker host. Created the container with the command found on dockerhub.
After it was started I needed to get a new API KEY, the discovery function wouldn’t work so i used Postman in google chrome to create an API call.
There is documentation to be found here: https://dresden-elektronik.github.io/deconz-rest-doc/configuration/#aquireapikey
Just copy the example request data and replace the username with something you want as API KEY, can be a regular password, then hit post and it will be configured.
Works really good!
Just upgraded the firmware (pushed the new deconz docker image yesterday) and it seems to have worked fine!
Edit: I stand corrected. Seems to be an issue!
Edit2: it can be flashed through docker like this:
docker stop deconz
rmmod ftdi_sio
docker run --rm -ti --privileged=true --device /dev/ttyUSB0:/dev/ttyUSB0 -v /dev/bus/usb:/dev/bus/usb joch/deconz GCFFlasher_internal -d 0 -f /usr/share/deCONZ/firmware/deCONZ_Rpi_0x261d0500.bin.GCF
It will output the following (ignore the not found warnings, it’s fine
/usr/bin/GCFFlasher_internal: 9: /usr/bin/GCFFlasher_internal: rmmod: not found
/usr/bin/GCFFlasher_internal: 10: /usr/bin/GCFFlasher_internal: rmmod: not found
GCFFlasher V2_11 (c) dresden elektronik ingenieurtechnik gmbh 2017/12/10
using firmware file: /usr/share/deCONZ/firmware/deCONZ_Rpi_0x261d0500.bin.GCF
reset via FTDI
flashing 123252 bytes: |=============================|
verify: ....
SUCCESS
/usr/bin/GCFFlasher_internal: 14: /usr/bin/GCFFlasher_internal: modprobe: not found
/usr/bin/GCFFlasher_internal: 15: /usr/bin/GCFFlasher_internal: modprobe: not found
Then restart:
modprobe ftdi_sio
docker restart deconz
I’ll add this to the readme for the docker image repo!
1 Like
What’s the best way to use ConBee via emulated Hue or deCONZ component?
deconz component of course
But otherwise it would be the hue component, not the emulated hue.
I’m using this theme https://hastebin.com/kuzonibale.cs and I’m trying to figure out why a specific kind of lights populated from the deconz komponent has “blue” as active color.
I have several lights from deconz, and the 4 lights that are blue have 1 thing in common, the entity is a group from deconz, they consist of several lights.
light.hall_taklampa contains 4 real lights ( light.hall_taklampa_1, _2, _3 and _4)
And I guess I need to set the correct active color for these kind of groups. Anyone who’s had the same issue and knows what code i need to use in my theme config?
and here is from the deconz gui
First off; which version of deconz are you running? I remember people talking about that issue a few months ago
2.04.99
We need debug data to go further with this. Can you enable debug in logger component?
This is an issue in deCONZ at the moment AFAIK (there are two issues I know of on this issue, one is mine - https://github.com/dresden-elektronik/deconz-rest-plugin/issues/415 references both issues).
The problem is that the deCONZ REST API is applying x,y colour attributes to (seemingly) all groups of lights, whether that group contains colour lights or not. The consequence is that a group of white-only lights are having x,y 0,0 applied. So groups of lights in deCONZ have a blue icon on the HA frontend (and will show a colour-picker if the group is clicked on).
I think this is an issue that needs fixing on the REST API side.
Is the info from @marthocoo enough or do you need more information? The problem he describes is exactly what I suffer from as well.