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!
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?
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.
As deconz is working on its support for additional components they just released a version which can pair with and expose smoke/fire detectors. I paired a Xiaomi smoke detector which produces the following json using the REST API:
I’m not sure how stable it is already or if they change the type from ZHAFire to something else but hope, that the snippet is a good start for supporting it in the deconz component as well.
Spent the evening with an upgrade my my HA system and it’s surrounding components. Did, a snapshot of my virtual machine and started the upgrade!
Firmware upgrade - Worked!
Upgrade to deconz 2.05.05 with a manual Dockerfile based on your repository - Fail!
Use the snapshot to get back, thinking I had messed up the deconz database
Tried it again
spent 45minutes trying to understand, reverting settings, trying different versions etc…
Took a break for 5minutes and looked back on what I’ve done, realised I was trying to start the new deconz container with the same “docker create” command as I previous had used, didn’t realize it was incorrect the whole time and I actually changed it but forgot to update my own documentation
Now I’m running the image from your repository (2.05.01) and latest firmware on the stick (at least phoscon and the old webpage doesn’t tell me about an update)
Phoscon has some nice new features and I’m going to try to upgrade deconz to 0.5 to get my water and smoke sensors included as well.
Thanks for the awesome work Joch and all you others contributing to deconz and HA!
@joch - I hadn’t seen that you had made a Docker image… nice work! I’ve gotten one of my own working - https://hub.docker.com/r/marthoc/deconz/. We should collaborate! Does yours currently work with Conbee and RaspBee? Having gotten the Conbee working, RaspBee is my next step - shouldn’t be difficult, I have both pieces of hardware.
2.05.05 running with the latest firmware, had about 80% of my devices missing after 20 minutes of uptime and i had to get som sleep, thought that i would need to rescan alot of devices. But waking up this morning and checking HA for unavailable devices showed 0!
Great work with docker! Looking forward to run deconz in a container. @marthocoo did something great that is a real necessity. The option to specify port and websocket port. When running a few dockers it’s important to be able to change ports. And since the component is taking whatever port that deconz reports just doing a portforward in the container isnt enough