Hass.io + deCONZ + RaspBee = Flailure

[b_automated (Brandon)]

Hey all,

Got myself a RaspBee, installed it on my rpi3, added deCONZ, restarted the rpi3. I have a dozen hue bulbs, dimmer switch and motion sensor all working with a hue bridge at present. It seems that deCONZ is both working and not working.

With discovery enabled, I can go to Configuration -> Integrations and under Configured I see:

deCONZ-0000000000000000
Integration: deCONZ
Added by: discovery
State: loaded

From what I’ve read deCONZ should read the MAC address of the RaspBee and update the bridgeid from 0000000000000000 to something with fewer zeros. That doesn’t seem to be happening.

When I go to deCONZ add-on details and launch Phoscon at http://hassio.local:8080/pwa it finds my gateway. I log in and it searches for lights and finds none. After clicking through a few popups I can access Hamburger -> Settings -> Gateway:

After clicking update: (sorry, limited to one picture)

Version      2.04.35
Firmware     00000000

Update finished.

Not what I was expecting…

deCONZ add-on Log:

[Hass.io] Starting deCONZ Hass.io Addon...
[Hass.io] Current deCONZ version: 2.05.25
[Hass.io] Web UI port: 8080
[Hass.io] Websockets port: 8443
libpng warning: iCCP: known incorrect sRGB profile
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
10:54:01:483 HTTP Server listen on address 0.0.0.0, port: 8080, root: /usr/share/deCONZ/webapp/
10:54:02:329 dev /dev/ttyAMA0
10:54:02:329 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
10:54:02:515 parent process /bin/sh
10:54:02:516 gw run mode: normal
10:54:02:516 sd-card cid: 1b534d454231515430ffffffff01141d
10:54:02:522 don't close database yet, keep open for 900 seconds
10:54:02:523 don't close database yet, keep open for 900 seconds
10:54:02:525 started websocket server at port 8443
10:54:02:525 create default username and password
10:54:02:529 discovery updated announce interval to 10 minutes
10:54:02:532 found node plugin: libde_rest_plugin.so - REST API Plugin
10:54:02:536 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
10:54:02:552 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
10:54:02:837 dev /dev/ttyAMA0
10:54:03:358 device state timeout ignored in state 2
10:54:04:308 device state timeout ignored in state 2
10:54:05:258 device state timeout ignored in state 2
10:54:06:208 device state timeout ignored in state 2
10:54:07:186 device state timeout ignored in state 2
10:54:07:273 save zll database items 0x0000008C
10:54:07:329 database saved in 56 ms
10:54:07:546 sync() in 217 ms
10:54:07:546 don't close database yet, keep open for 900 seconds
10:54:07:991 dev /dev/ttyAMA0
10:54:07:992 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_Rpi_0x261f0500.bin.GCF
10:54:08:260 Announced to internet
10:54:08:262 discovery server date: Fri, 18 May 2018 16:54:08 GMT
10:54:08:262 	 local time seems to be ok
10:54:08:262 discovery found version 2.04.35 for update channel stable
10:54:08:518 device state timeout (handled)
10:54:08:648 New websocket 10.0.0.20:53978 (state: 3) 
10:54:09:043 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
10:54:09:043 device state timeout ignored in state 4
10:54:11:316 New websocket 10.0.0.42:50758 (state: 3) 
10:54:29:788 scan skip host .20
10:54:29:800 found gateway 10.0.0.21:80
10:54:30:230 Websocket disconnected 10.0.0.42:50758 (state: 0) 
10:54:34:579 New websocket 10.0.0.42:50761 (state: 3) 
10:54:41:387 scan finished
10:54:41:998 Websocket disconnected 10.0.0.42:50761 (state: 0) 
10:54:45:997 New websocket 10.0.0.42:50764 (state: 3) 
10:54:48:998 save zll database items 0x00000008
10:54:49:078 database saved in 80 ms
10:54:49:290 sync() in 211 ms
10:54:49:290 don't close database yet, keep open for 900 seconds
10:54:55:843 GW firmware start update (device not connected)
10:54:56:370 GCFFlasher V2_11 (c) dresden elektronik ingenieurtechnik gmbh 2017/12/10
no device specified use RaspBee (/dev/ttyAMA0)
using firmware file: /usr/share/deCONZ/firmware/deCONZ_Rpi_0x261f0500.bin.GCF 
10:54:56:370 GW firmware update exit code 1
10:54:57:189 Wait reconnect after firmware update
10:54:58:189 Wait reconnect after firmware update
10:54:59:189 Wait reconnect after firmware update
10:55:00:188 Wait reconnect after firmware update
10:55:01:188 Wait reconnect after firmware update
10:55:02:188 Wait reconnect after firmware update
10:55:03:189 Wait reconnect after firmware update
10:55:04:189 Wait reconnect after firmware update
10:55:05:189 Wait reconnect after firmware update
10:55:06:188 Wait reconnect after firmware update
10:55:06:654 dev /dev/ttyAMA0
10:55:07:190 Wait reconnect after firmware update
10:55:08:189 Wait reconnect after firmware update
10:55:09:189 Wait reconnect after firmware update
10:55:10:189 Wait reconnect after firmware update
10:55:11:189 Wait reconnect after firmware update
10:55:12:188 Wait reconnect after firmware update
10:55:13:188 Wait reconnect after firmware update
10:55:14:188 Wait reconnect after firmware update
10:55:15:188 Wait reconnect after firmware update
10:55:16:189 Wait reconnect after firmware update
10:55:17:189 Wait reconnect after firmware update
10:55:18:189 Wait reconnect after firmware update
10:55:19:189 Wait reconnect after firmware update
10:55:20:190 Wait reconnect after firmware update
10:55:21:189 Wait reconnect after firmware update
10:55:22:189 Wait reconnect after firmware update
10:55:23:188 Wait reconnect after firmware update
10:55:24:189 Wait reconnect after firmware update
10:55:25:188 Wait reconnect after firmware update
10:55:26:189 Wait reconnect after firmware update
10:55:27:189 Wait reconnect after firmware update
10:55:28:189 Wait reconnect after firmware update
10:55:29:189 Wait reconnect after firmware update
10:55:30:189 Wait reconnect after firmware update
10:55:31:189 Wait reconnect after firmware update
10:55:32:189 Wait reconnect after firmware update
10:55:33:186 save zll database items 0x00000200
10:55:33:187 database saved in 0 ms
10:55:33:469 sync() in 282 ms
10:55:33:469 don't close database yet, keep open for 900 seconds
10:55:33:472 Wait reconnect after firmware update
10:55:34:189 Wait reconnect after firmware update
10:55:35:188 Wait reconnect after firmware update
10:55:36:189 Wait reconnect after firmware update
10:55:37:189 Wait reconnect after firmware update
10:55:38:188 Wait reconnect after firmware update
10:55:39:189 Wait reconnect after firmware update
10:55:40:189 Wait reconnect after firmware update
10:55:41:189 Wait reconnect after firmware update
10:55:42:189 Wait reconnect after firmware update
10:55:43:189 Wait reconnect after firmware update
10:55:44:189 Wait reconnect after firmware update
10:55:45:189 Wait reconnect after firmware update
10:55:46:188 Wait reconnect after firmware update
10:55:47:189 Wait reconnect after firmware update
10:55:48:189 Wait reconnect after firmware update
10:55:49:189 Wait reconnect after firmware update
10:55:50:188 Wait reconnect after firmware update
10:55:51:189 Wait reconnect after firmware update
10:55:52:189 Wait reconnect after firmware update
10:55:53:189 Wait reconnect after firmware update
10:55:54:188 Wait reconnect after firmware update
10:55:55:189 Wait reconnect after firmware update
10:55:56:189 Wait reconnect after firmware update
10:55:57:189 Wait reconnect after firmware update
10:55:58:188 Wait reconnect after firmware update
10:55:59:189 Wait reconnect after firmware update
10:56:00:188 Wait reconnect after firmware update
10:56:01:189 Wait reconnect after firmware update
10:56:02:189 Wait reconnect after firmware update
10:56:03:188 Wait reconnect after firmware update
10:56:04:190 Wait reconnect after firmware update
10:56:05:188 Wait reconnect after firmware update
10:56:06:189 Wait reconnect after firmware update
10:56:07:189 Wait reconnect after firmware update
10:56:08:189 Wait reconnect after firmware update
10:56:09:189 Wait reconnect after firmware update
10:56:10:189 Wait reconnect after firmware update
10:56:11:188 Wait reconnect after firmware update
10:56:12:190 Wait reconnect after firmware update
10:56:13:186 Wait reconnect after firmware update
10:56:14:671 dev /dev/ttyAMA0
10:56:15:187 device state timeout ignored in state 2
10:56:16:186 device state timeout ignored in state 2
10:56:17:186 device state timeout ignored in state 2
10:56:18:187 device state timeout ignored in state 2
10:56:19:186 device state timeout ignored in state 2
10:56:20:186 device state timeout (handled)
10:56:20:687 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state

Home Assistant Log:

2018-05-18 10:02:11DEBUG (MainThread)[  
   pydeconz.utils
]Sending{  

}to http://10.0.0.20:8080/api/D1D13B0952 
2018-05-18 10:02:11DEBUG (MainThread)[  
   pydeconz.utils
]HTTP request response:{  
   'config':{  
      'UTC':'2018-05-18T16:02:11',
      'apiversion':'1.0.9',
      'backup':{  
         'errorcode':0,
         'status':'idle'
      },
      'bridgeid':'0000000000000000',
      'datastoreversion':'60',
      'dhcp':True,
      'factorynew':False,
      'fwversion':'0x00000000',
      'gateway':'10.0.0.1',
      'internetservices':{  
         'remoteaccess':'disconnected'
      },
      'ipaddress':'10.0.0.20',
      'linkbutton':False,
      'localtime':'2018-05-18T10:02:11',
      'mac':'b8:27:eb:e2:9d:7c',
      'modelid':'deCONZ',
      'name':'RaspBee',
      'netmask':'255.0.0.0',
      'networkopenduration':60,
      'panid':0,
      'portalconnection':'disconnected',
      'portalservices':False,
      'portalstate':{  
         'communication':'disconnected',
         'incoming':False,
         'outgoing':False,
         'signedon':False
      },
      'proxyaddress':'none',
      'proxyport':0,
      'replacesbridgeid':None,
      'rfconnected':False,
      'starterkitid':'',
      'swupdate':{  
         'checkforupdate':False,
         'devicetypes':{  
            'bridge':False,
            'lights':[  

            ],
            'sensors':[  

            ]
         },
         'notify':False,
         'text':'',
         'updatestate':0,
         'url':''
      },
      'swupdate2':{  
         'autoinstall':{  
            'on':False,
            'updatetime':''
         },
         'bridge':{  
            'lastinstall':'',
            'state':'allreadytoinstall'
         },
         'checkforupdate':False,
         'install':False,
         'lastchange':'',
         'lastinstall':'',
         'state':'allreadytoinstall'
      },
      'swversion':'2.5.25',
      'timeformat':'12h',
      'timezone':'Etc/GMT+6',
      'uuid':'a7ccdb48-9150-48d1-b7ce-a32e317d526a',
      'websocketnotifyall':True,
      'websocketport':8443,
      'whitelist':{  
         '3579FD42C4':{  
            'create date':'2018-05-18T15:15:04',
            'last use date':'2018-05-18T15:36:31',
            'name':'Phoscon#B1274x706'
         },
         '35BC4CB3A1':{  
            'create date':'2018-05-18T15:51:55',
            'last use date':'2018-05-18T15:51:59',
            'name':'Phoscon#B1274x706'
         },
         '878CEA02B4':{  
            'create date':'2018-05-18T15:56:38',
            'last use date':'2018-05-18T15:56:42',
            'name':'Phoscon#B1274x706'
         },
         'D1D13B0952':{  
            'create date':'2018-05-18T15:36:26',
            'last use date':'2018-05-18T16:02:11',
            'name':'pydeconz'
         },
         'D96BA8D5BE':{  
            'create date':'2018-05-18T06:26:41',
            'last use date':'2018-05-18T14:35:35',
            'name':'Phoscon#B1274x706'
         }
      },
      'zigbeechannel':0
   },
   'groups':{  

   },
   'lights':{  

   },
   'resourcelinks':{  

   },
   'rules':{  

   },
   'schedules':{  

   },
   'sensors':{  
      '1':{  
         'config':{  
            'configured':True,
            'on':True,
            'sunriseoffset':30,
            'sunsetoffset':-30
         },
         'etag':'822086f7e77b809546926001c9794157',
         'manufacturername':'Philips',
         'modelid':'PHDL00',
         'name':'Daylight',
         'state':{  
            'daylight':True,
            'lastupdated':'2018-05-18T15:53:58',
            'status':160
         },
         'swversion':'1.0',
         'type':'Daylight',
         'uniqueid':'00:00:00:00:00:00:00:00-01'
      }
   }
}2018-05-1810:02:11DEBUG (MainThread)[  
   pydeconz.config
]Deconz config loaded{  
   '_apiversion':'1.0.9',
   '_bridgeid':'0000000000000000',
   '_linkbutton':False,
   '_modelid':'deCONZ',
   '_name':'RaspBee',
   '_networkopenduration':60,
   '_panid':0,
   '_swversion':'2.5.25',
   '_uuid':'a7ccdb48-9150-48d1-b7ce-a32e317d526a',
   '_websocketport':8443,
   '_zigbeechannel':0
}2018-05-1810:02:11DEBUG (MainThread)[  
   pydeconz.deconzdevice
]Daylight created as{  
   '_daylight':True,
   '_status':160,
   '_battery':None,
   '_ep':None,
   '_on':True,
   '_reachable':None,
   '_sensor_class':None,
   '_sensor_icon':None,
   '_sensor_unit':None,
   '_deconz_id':'/sensors/1',
   '_etag':'822086f7e77b809546926001c9794157',
   '_manufacturername':'Philips',
   '_modelid':'PHDL00',
   '_name':'Daylight',
   '_swversion':'1.0',
   '_type':'Daylight',
   '_uniqueid':'00:00:00:00:00:00:00:00-01',
   '_async_callback':[  

   ]
}

So it’s failing to update the firmware. I’d call it a downgrade, but when I log out and log back in, it’s back to version 2.05.25.

Doesn’t seem like it’s working. Now here’s the hitch, when I check each of the device tabs I get a surprise…

Devices
Lights - NOTHING
Switches - NOTHING
Sensors - Daylight Sensor!!!

So, I’m led to believe the RaspBee works, and deCONZ could work but somethings not right.

If you’ve got any experience with this or any ideas please chime in!

[b_automated (Brandon)]

Update:

Using this tip from @gjong in the thread Deconz for Hass.io I added the following to my config.txt file.

enable_uart=1
dtoverlay=pi3-disable-bt

Now, is this progress, hard to say.

deCONZ has a bridgeid, but it also changed the state of both the hue and deCONZ to setup_error.

Not sure what the significance of that is. Still no lights or switches. Just the one sensor.

And in a possibly related instance, Samba share stopped working.

[Robban]

I’d recommend you to start looking at the logs. If nothing is showing follow instructions to enable debug for deconz component from component documentation

[b_automated (Brandon)]

Making progress now!

The trick was making sure there was a blank line after the addendum to config.txt

enable_uart=1
dtoverlay=pi3-disable-bt
[blank line]

With discovery enabled I was able to follow the deCONZ instructions provided.

I now have a motion sensor AND dimmer!

But alas, still no lights.

[Robban]

Would you mind creating an issue with marthocs deconz docker github and add what you did to solve this?

[b_automated (Brandon)]

No problem. Hopefully this thread helps someone else as well!

[Robban]

Your shared experience will help improve documentation for other users

[rafuz]

Same issue here fixed adding a blank line after the config.

[b_automated (Brandon)]

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.

[b_automated (Brandon)]

Am I the only one having this problem in deCONZ?

[greencharlie100]

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.

[Robban]

Whats the issue you’re having? 6 months in between posts, the cause might be different.

[greencharlie100]

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?

[greencharlie100]

Another image:

[greencharlie100]

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.

[Robban]

Great that you solved it!

[fleusner]

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!

[Robban]

I think there is a comment about an extra new line in regards to getting this fixed

[fleusner]

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?

[Robban]

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

HA on Raspberry Pi 3B+ with RaspBee

Solved by myself Install Hassio Enable SSH https://developers.home-assistant.io/docs/en/hassio_debugging.html 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 US…