Same issue here fixed adding a blank line after the config.
UPDATE:
I’ve gotten all of the lights into deCONZ by manually resetting each hue bulb.
To do so, I had to flip the light switch off-on, then using the hue dimmer switch depress both the on and off buttons simultaneously for 10 seconds until lights stop blinking.
Now on to the next problem… deCONZ won’t create new groups.
One was created for the dimmer switch automatically and is visible in HA. However, when I click “+ Add Group” the pop-up displays, then when I click submit, nothing.
Am I the only one having this problem in deCONZ?
I seem to be having the same problem. Here is my config.txt file - is this correct?
kernel=u-boot.bin
disable_splash=1
dtparam=audio=on
enable_uart=1
dtoverlay=pi3-disable-bt
Any help would be greatly appreciated.
Whats the issue you’re having? 6 months in between posts, the cause might be different.
I am trying to get deCONZ working for the first time on Hass.io. I am trying for 36 hours but no success.
I dont know where I stand at present. Here are two screen-shots which might give you a clue as to how much progress I have made to date.
It seems that the Raspbee is not found?
Robban,
I managed to get deCONZ working. I am not sure what I did differently apart from do a HA update from v 82.0 to 83.1. I then removed deCONZ and reinstalled again. Working now.
Thanks.
Great that you solved it!
Hi there,
got a similar issue over here.
Following this guide I was able to add those too lines to the config.txt, but still it says that the raspbee isn’t connected:
Hassio HW info:
DeCONZ Config:
Any hint how to track this issue down?
How can I access the deconz log files?
Currently I’m using a 2A 5W supply.
Do I really need a 2,5A one ?
Many thanks in advance!
I think there is a comment about an extra new line in regards to getting this fixed
Hey Robban, thanks for the hint.
I had already one extra line included, added another one (just in case):
No luck with that one, still not connected 
How can I open the deconz related log files?
I don’t use Hassio, but there are commands to use docker to read logs from containers. You might need to improve logging for the add-on though
Hey Robban, thanks for your quick reply.
I know this post, one of those who gave me the hint related to ssh 
Meanwhile I was able to test if its related to my 2A power supply - not.
Very frustrating thing.
I’ll try if it works with a fresh install. If not I’ll probably gonna switch to hasspian 
//edit:
Just in case someone got the same issues:
- save a fresh snapshot on your system
- fresh hassOS install + snapshot import
- System-SSH configuration:
Use a USB drive formatted with FAT, ext4, or NTFS and name it CONFIG (case sensitive). Create an authorized_keys file containing your public key, and place it in the root of the USB drive. From the UI, navigate to the hass.io system page and choose “Import from USB”. You can now access your device as root over SSH on port 22222. Alternatively, the file will be imported from the USB when the hass.io device is rebooted.
- System-SSH:
ssh [email protected] -p 22222 -i .ssh/YOUR Private Key File
login
vi /mnt/boot/config.txt
enable_uart=1
dtoverlay=pi3-miniuart-bt
(blank line)
reboot
-
deCONZ setup:
Install deCONZ Add-onhttp://hassio.local:8123/hassio/store
Config
{ "device": "/dev/ttyAMA0" }
Solved it for me 
My setup:
- pi3
- 2A power supply
Note:
I’ve used dtoverlay=pi3-miniuart-bt instead of dtoverlay=pi3-disable-bt*.
1 Like
What do I need to write instead of this? My file Name? “authorized_keys”?
Sorry, HA community mails landed in my spam folder, dafuq.
The answer ist yes, but I guess that you’ve already solved it by yourself 
Hi,
I am running a pi4 with Raspee. It is on Firmware 26050500. I am trying to update the Firmware to the latest version 26330500. Unfortunately without luck. The firmware update runs smoothly. However, after the update the Phoscon App will say firmware not connected and - after a while - show the old firmware version again.
I have checked the log on hassio. The suspicious line in the log reads: “GW firmware update exit code 1”.
Does anybody know what this means. This has been keeping me from updating the FW and integrating bulbs and switches for more than 2 month now. I don’t know what else to do. I have even added 2 blank lines at the end of the log.
Thanks for any recommendation!
Theo
I am having a very similar issue (among others) with hass.io deCONZ.
I’ve been able to get the raspbee recognized. At one point, I had deCONZ bridged with devices showing up, but that has stopped working and I’ve not been able to get it working again yet; will try completely removing and setting up deCONZ. Also, I’ve tried to upgrade the firmware and the process declares itself successful, but “GW firmware update exit code 1” appears in the add-on log and the firmware version is not updated.
The other major issue I’ve encountered is that I’ve been able to add 4 Keen Home Smart Vents, but after that, I’m unable to add anymore at all. No clue why yet.
Using pi3B+ HA 100.3 with raspbee.
I too had no end of problems when I first got my Conbee.
Fimware wouldn’t update etc.
In the end I connected it to my windows laptop and did it manually with the GCFFlasher command line.
After that it worked fine.
1 Like
Hi, have you managed to solve this? Encountering the same thing atmz