In terms of updating the firmware, I’m slowly putting the pieces together, but making progress.
I downloaded the latest deCONZ… .GCF firmware file.
I downloaded the latest GCFFlasher and unzipped.
I downloaded version 2.12.28 (32 bit that they link to) of the VCP DDriver , however there is no .dll file.
I downloaded the latest 32 bit version (2.12.36.4 ) and there is a .dll file in the i386 folder (I just guessed and downloaded this version since the original didnt contain a file called ftd2xx.dll).
I copied this ftd2xx.dll into the GCFFlasher folder and replaced the original.
I Shift-Clicked inside this folder to click the option of opening the powershell (but not sure how to open as admin).
I took out the conbee ii stick for 10 seconds, then inserted and waited 10 seconds.
I ran the command .\GCFFlasher -l which requires the extra .\.
It prints info on the Conbee.
I noticed the instructions online for the firmware reference the “COM” part of the print. Mine says COM3 (instead of COM7 like in the example).
I use paste the code from the instructions into a note editor
I change the COM7 to COM3, and I also add the .\ before the command, so I have .\GCFFlasher -d COM3 -t 60 -f ../firmware/deCONZ_ConBeeII_0x26720700.bin.GCF
I paste that into the powershell and hit enter and get these results:
The two things that could be possible is that the .dll file isnt working (since it did not exist in the zip file they recommended, I had to guess and try another one).
OR I am not in admin mode in the powershell, because I did not see an option to run it in that mode when I Shift-Clicked.
UPDATE: I figured out that if you download the link to the 2.12.28 file in the instructions, it does not come with a ftd2xx.dll file, but if you manually find that file in the VCP drivers, the zip file you download DOES include the ftd2xx.dll file.
However, replacing with this version of .dll file did not change the outcome error when I tried the steps again.
UPDATE 2:
I am now thinking that it is having a problem finding this deconz…GCF file. It is just sitting in my downloads folder and isnt in any “/firmware/” directory.
How is the powershell supposed to know where to find this GCF File? Do I have to place it somewhere manually first?
During the night my deconz integration decided to enter a boot loop, and from what i can gather, it seems to think it wants to upgrade the firmware, but the firmware is upgraded, so it errors out and gets restarted by watchdog. How do i resolve this?
Here’s the lines i managed to extract from the docker log:
10:10:54:001 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26660700.bin.GCF
10:10:54:001 GW firmware version: 0x26680700
10:10:54:001 GW firmware version is up to date: 0x26680700
10:10:55:191 ZCL attribute report 0x0017880106490F58 for cluster: 0x0402, ep: 0x02, frame control: 0x08, mfcode: 0x0000
[10:10:59] INFO: Starting VNC server (local/yes)…
2021/11/27 10:10:59 [notice] 314#314: signal 15 (SIGTERM) received from 306, exiting
2021/11/27 10:10:59 [notice] 1441#1441: exiting
2021/11/27 10:10:59 [notice] 1441#1441: exit
In exit
Closing socket listening at 127.0.0.1:5901
2021/11/27 10:10:59 [notice] 314#314: signal 17 (SIGCHLD) received from 1441
2021/11/27 10:10:59 [notice] 314#314: worker process 1441 exited with code 0
2021/11/27 10:10:59 [notice] 314#314: exit
Thank you!
I was finally able to update the firmware. I’ll need to see if that fixed my deconz situation tomorrow
And to anyone finding this bc they had issues knowing what to do for these steps, you remove that firmware part of the path but you also have to put the GCF file in the GCFFlasher directory.
And you may also need to use the .\ at the start of the shell lines you paste, along some other details I wrote above.
Hi,
my HA is sometimes not showing the real value from Deconz.
Here is an example: look at the line Current Temperature Setpoint in Deconz Thermostat Cluster Attributes
and in HA near Auto in bold
Any Idea ?
When I look in the integration page, there is no debug option for Deconz.
In the Supervisor page, there are some in the Deconz setup page, like dbg_apps=1, dbg_info=1, dbg_zcl=0 and dbg_zdp=0. Should I change all the values to 1 ?
I suppose the log are in Deconz plugin logs, not in Hass log ?
I don’t see somthing interesting in Deconz plugin logs
Somehow my DeCONZ application add-on stopped rebooting itself some hours after my post last saturday. Well… this evening it decided to start rebootlooping again… Is there any way to FIX THIS?!
So I am running HA OS on a Pi 4 with a Conbee II stick and using Deconz. Whenever there is an update to HA (or my Pi loses power by accident) I lose the connection to everything under “Lights” in Phoscon (my lightbulbs and smart plugs). Then I have to search for them again, and add the names for each device again, which is quite annoying. The strange thing is that everything else in Phoscon is still connected - all sensors immediately show up and with the correct names and all. So it is only the devices under “Lights”. I have tried waiting for a couple of hours to see if they would reconnect by themselves, but that didn’t work.
I do not have any logs for it at the moment, but I will of course try to get them when I experience the issue the next time.
But has anyone seen any fix posted for this issue anywhere?
Oh, and by the way the firmware is of course updated
Iirc this is that when both hass and deconz restart lights take longer to load for deconz and hass requests data before loading is complete. I haven’t noticed this for a long time and I think deconz improved the loading as well. When this happens first thing to try is to see if a reload of the deConz integration solves the issue. Then you can report back
Ok. Do you have your conbee on an extension cord? That’s typically the most common issue with devices behaving badly is when you don’t have an extension cord
