Hi,
I’ve just moved from the marthoc add on to the official one. I’m surprised to see that my conbee doesn’t have a firmware update available, since it’s been ages since I updated it.
The phoscon web Ui says my firmware version is 26330500
Can anyone confirm if that seems right? I tried looking for information on the latest version but was unable to find any.
Thanks,
James
Hi guys,
Switched from a Raspi 3 with Hassio install (image, no docker) to Intel NUC. On the NUC I am using hassion in docker enviroment with poratiner as management tool.
Now I recognized that deconz is shown twice on my integrations site. One is filled with my sensors and light, the other one (when I configzre it) is empty and does not show any devices. To keep it clean I want to delete this deconz integration entry, because it’s useless. But how can I do it and why is there a second integration listed without any devices. I am using just 1 conbee2 stick, so no other deconz gateway is available.
Maybe somebody has a tip to remove it?
Thank’s in advance!
Thanks - that deconz II looks more current than my current firmware, but I think I have the original deconz stick.
I’ll go ask on their site.
Your firmware is the latest for the ConBee original (see bottom of list)
Try removing ssdp: from your config
There’s no ssdp in my config. 
I guess I have to delete:
default_config:
Did not work. If I delete the default_config the sudebar entries: map, log, history and preferences are gone.
you can always configure those componenets manually, but anyway, ssdp is not the culprit
this is maybe related:
Hi all,
I am trying to update my conbee-II stick firmware running 264A0700. Reading the wiki it only mentions the marthoc’s deCONZ Docker image and there it say’s at step 3:
Invoke the firmware update script: docker run -it --rm --entrypoint "/firmware-update.sh" --privileged --cap-add=ALL -v /dev:/dev -v /lib/modules:/lib/modules -v /sys:/sys marthoc/deconz
Is this the same way to do when running the Hassio Core Add-on: deCONZ?
Kind regards
I thought it was supposed to be possible through the phoscon web UI in the official add on?
Thanks - I was confused by the reference to Rpi in the filenames, I thought it meant a specific recovery pi implementation.
So i read that too, but if it’s not possible then it must be done manually. In my situation it says it’s up to date in the app
Why does deCONZ check the firmware like every 6-10 minutes?
15:17:41:410 GW firmware version: 0x264a0700
15:17:41:410 GW firmware version is up to date: 0x264a0700
…
15:09:41:404 GW firmware version: 0x264a0700
15:09:41:404 GW firmware version is up to date: 0x264a0700
…
15:01:41:409 GW firmware version: 0x264a0700
15:01:41:409 GW firmware version is up to date: 0x264a0700
I have an issue with conbee II and firmware 26490700 with a xiaomi aqara motion sensor.
I can discover the sensor and I can see it in the deconz ui and in the HA but the sensor was refreshed 19 hours ago.
The sensor is new and the battery level is 100%.
How can I collect data to find the issue?
Thanks for this, I do actually recall reading this somewhere but it never occurred to me that this was the issue, I always assumed that it was the bulb itself that applied the transition when changing brightness as opposed to the controlling device (ikea bridge, hue bridge, or deconz).
Yep I think maintaining control is better than smooth transitions for now, hopefully there will be an ikea bulb firmware update to fix this.
Anything new on this? I have the same issue. I’m on an RPI 3 b+ running deConz in a docker on hassio.
Device: /dev/ttyAMA0
Firmware File: deCONZ_Rpi_0x26330500.bin.GCF
Are the above device and firmware values correct?
Enter Y to proceed, any other entry to exit: y
Flashing...
/usr/bin/GCFFlasher_internal.bin: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libwiringPi.so)
Flashing Error! Please re-run this script...
# ls -lh /lib/libc.so.6
lrwxrwxrwx 1 root root 12 May 10 2019 /lib/libc.so.6 -> libc-2.28.so
# strings /lib/libc.so.6 | grep GLIBC
GLIBC_2.4
GLIBC_2.5
GLIBC_2.6
GLIBC_2.7
GLIBC_2.8
GLIBC_2.9
GLIBC_2.10
GLIBC_2.11
GLIBC_2.12
GLIBC_2.13
GLIBC_2.14
GLIBC_2.15
GLIBC_2.16
GLIBC_2.17
GLIBC_2.18
GLIBC_2.22
GLIBC_2.23
GLIBC_2.24
GLIBC_2.25
GLIBC_2.26
GLIBC_2.27
GLIBC_2.28
GLIBC_PRIVATE
Hi there,
I did addon upgrade from 3.8 to 4.1 and lost connection to deconz so I restored from backup version 3.8 and it is up again but I have lost all zigbee paired devices. This is really wrong. Do I need to re-pair all from zero or I can restore it somehow? I thought that backup will do that.
After updating to 4.1 it seems my devices are working but I can’t connect to phoscon. It’s stuck in a “searching gateway” screen.
I have made a huge mistake updating from 3.8 to 4.1. I had quite an established zigbee device set up with 26 devices. Now all my devices are gone.
Hassio log:
2019-12-20 08:03:34 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz.local.hass.io
2019-12-20 08:03:34 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 5 seconds.
2019-12-20 08:03:41 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz.local.hass.io
2019-12-20 08:03:41 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 10 seconds.
2019-12-20 08:03:52 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz.local.hass.io
2019-12-20 08:03:52 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 20 seconds.
2019-12-20 08:04:13 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz.local.hass.io
2019-12-20 08:04:13 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 40 seconds.
2019-12-20 08:04:54 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz.local.hass.io
2019-12-20 08:04:54 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 80 seconds.
2019-12-20 08:04:56 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:05:03 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:05:11 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:05:20 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:05:28 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:05:40 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:05:50 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:06:01 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:06:13 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:06:15 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz.local.hass.io
2019-12-20 08:06:15 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 80 seconds.
2019-12-20 08:06:26 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:07:36 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz.local.hass.io
2019-12-20 08:07:36 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 80 seconds.
2019-12-20 08:08:57 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz.local.hass.io
2019-12-20 08:08:57 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 80 seconds.
2019-12-20 08:10:08 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:10:15 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.0.11
2019-12-20 08:10:18 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz.local.hass.io
2019-12-20 08:10:18 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 80 seconds.
2019-12-20 08:11:39 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz.local.hass.io
2019-12-20 08:11:39 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 80 seconds.
I have tried logging in and out of deconz and had no success, even tried reinstalling the add-on, i have hassio version 0.103.2.
please help!