Deconz for Hass.io

Robban · April 26, 2018, 6:27am

Check component documentation

mongo116 · April 26, 2018, 10:33am

I’ve setup DeCONZ with hass.io and I can see the xiaomi sensors I have, and that part is all working fine. Is there a way to have the temperature from these devices show in Home Assistant? I can see the temperature in Phoscon and also on the restapi response, but most of the devices only show battery level as an additional attribute, if that. I figured if I can pull back the temperature of window / door sensors, then I can use these with my boiler for automation.

gjong · April 26, 2018, 1:24pm

I noticed the exact same thing with the aqara contact sensor. It shows a temperature reading in Phoscon, but I confirmed with the webshop that the contact sensor does not have any temperature sensor in it. So it might be an issue with deCONZ reading an attribute from the contact sensor that is not for temperature and mapping it as a temperature reading?

mongo116 · April 26, 2018, 2:51pm

Ah ok, would have been nice to have it, but at least knowing will stop me wanting to display it

Thanks…

Robban · April 26, 2018, 3:36pm

There have been requests for this. A asked that they bring it up as a feature request on deconz github first. No response on the request yet though

Ulisses_Nogueira · May 14, 2018, 10:48pm

Guys, how could you install Deconz for Hass.io?

I’ve installed the add-on, on the Overview tab appears:

On Configuration -> Integrations appers:

But when I click on CONFIGURE, I get this messages:

AND

Any help? Tks

Robban · May 15, 2018, 5:42am

You need to go in to settings of deconz and enable internet discoverability. Which you can turn off once the setup is completed. You can also configure deconz through your configuration.yaml if you don’t get it to work.

I will update the documentation with this, I have also been planning to add a fallback mode where the user inputs all data manually.

Ulisses_Nogueira · May 15, 2018, 7:30am

Hi Robban, thanks for your help again.

It’s not possible to access the menu on webapp.

There is no “Menu”, the only option is a Search for Lights buttom that don’t find my Philips Hue Bulbs.

I’m also trying to use a REST client to get the API, but it’s not working also.

Robban · May 15, 2018, 8:32am

Do you have another zigbee hub? My conbee doesn’t look like that on the login screen from what I can remember

Ulisses_Nogueira · May 15, 2018, 8:45am

No, I don’t.

I’ve just brought the Raspbee and plugged it on my Raspberry Pi running Hassio.

Robban · May 15, 2018, 9:11am

Two things that can be done here:

Talk to @marthocoo about help debugging the container
Enable debug per component documentation and see what logs you get when starting and trying to set up the configurations, I can help you analysing these logs

Ulisses_Nogueira · May 15, 2018, 9:54am

Here’s the log.

10:45:30:427 HTTP Server listen on address 0.0.0.0, port: 8080, root: /usr/share/deCONZ/webapp/
10:45:30:828 dev /dev/ttyAMA0
10:45:30:828 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
10:45:31:040 parent process /bin/sh
10:45:31:040 gw run mode: normal
10:45:31:041 sd-card cid: 035344534333324780ffffffff012125
10:45:31:062 don't close database yet, keep open for 900 seconds
10:45:31:062 Daylight now: goldenHour1, status: 160
10:45:31:064 started websocket server at port 8443
10:45:31:068 discovery updated announce interval to 10 minutes
10:45:31:072 found node plugin: libde_rest_plugin.so - REST API Plugin
10:45:31:082 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
10:45:31:113 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
10:45:31:418 dev /dev/ttyAMA0
10:45:31:956 device state timeout ignored in state 2
10:45:32:000 device state timeout ignored in state 2
10:45:33:954 device state timeout ignored in state 2
10:45:34:954 device state timeout ignored in state 2
10:45:35:955 device state timeout ignored in state 2
10:45:36:440 dev /dev/ttyAMA0
10:45:36:442 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_Rpi_0x261f0500.bin.GCF
10:45:36:629 Announced to internet
10:45:36:630 discovery server date: Tue, 15 May 2018 09:45:36 GMT
10:45:36:630 	 local time seems to be ok
10:45:36:630 discovery found version 2.04.35 for update channel stable
10:45:36:954 device state timeout (handled)
10:45:37:454 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
10:45:37:454 device state timeout ignored in state 4
10:45:40:954 Daylight now: goldenHour1, status: 160
10:45:50:954 Daylight now: goldenHour1, status: 160
10:46:00:954 Daylight now: goldenHour1, status: 160
10:46:09:564 scan finished
10:46:10:954 Daylight now: goldenHour1, status: 160
10:46:20:953 Daylight now: goldenHour1, status: 160
10:46:30:954 Daylight now: goldenHour1, status: 160
10:46:40:953 Daylight now: goldenHour1, status: 160
10:46:50:953 Daylight now: goldenHour1, status: 160
10:47:00:954 Daylight now: goldenHour1, status: 160
10:47:10:954 Daylight now: goldenHour1, status: 160
10:47:20:954 Daylight now: goldenHour1, status: 160
10:47:30:953 Daylight now: goldenHour1, status: 160
10:47:40:954 Daylight now: goldenHour1, status: 160
10:47:46:438 dev /dev/ttyAMA0
10:47:50:954 Daylight now: goldenHour1, status: 160
10:48:00:954 Daylight now: goldenHour1, status: 160
10:48:07:477 Content not completely loaded (got 0 of 0), wait 20ms
10:48:10:954 Daylight now: goldenHour1, status: 160
10:48:15:670 Content not completely loaded (got 0 of 0), wait 20ms
10:48:20:954 Daylight now: goldenHour1, status: 160
10:48:30:954 Daylight now: goldenHour1, status: 160
10:48:40:954 Daylight now: goldenHour1, status: 160
10:48:50:954 Daylight now: goldenHour1, status: 160
10:49:00:958 Daylight now: goldenHour1, status: 160
10:49:10:954 Daylight now: goldenHour1, status: 160
10:49:20:954 Daylight now: goldenHour1, status: 160
10:49:30:953 Daylight now: goldenHour1, status: 160
10:49:40:954 Daylight now: goldenHour1, status: 160
10:49:50:954 Daylight now: goldenHour1, status: 160
10:49:56:412 dev /dev/ttyAMA0
10:50:00:958 Daylight now: goldenHour1, status: 160
10:50:10:953 Daylight now: goldenHour1, status: 160
10:50:20:953 Daylight now: goldenHour1, status: 160
10:50:30:954 Daylight now: goldenHour1, status: 160
10:50:40:954 Daylight now: goldenHour1, status: 160
10:50:50:954 Daylight now: goldenHour1, status: 160
10:51:00:954 Daylight now: goldenHour1, status: 160
10:51:10:954 Daylight now: goldenHour1, status: 160
10:51:20:954 Daylight now: goldenHour1, status: 160
10:51:30:954 Daylight now: goldenHour1, status: 160
10:51:40:954 Daylight now: goldenHour1, status: 160
10:51:42:822 Invalid admin password hash: $1$8282jdkm$w.o6XjJEGLzAYkVqLPAYx1
10:51:45:984 created username: 8788EA7BA1, devicetype: Phoscon#B1451x953
10:51:47:587 New websocket 192.168.1.92:51312 (state: 3) 
10:51:50:953 Daylight now: goldenHour1, status: 160
10:51:50:954 save zll database items 0x00000004

Robban · May 15, 2018, 10:55am

I meant the log from home assistant.

Can you add more logging to deconz as well?

gjong · May 15, 2018, 11:08am

If you don’t have any lights that can be added then follow the instructions given in https://github.com/dresden-elektronik/deconz-rest-plugin/issues/551. This will allow you to complete the setup of deCONZ and enable the internet discovery.

marthocoo · May 15, 2018, 11:09am

It’s not discovering your RaspBee - you need to disable Bluetooth on the Pi. Put the SD card in your computer, and on the boot volume find config.txt - add the following two lines to the end of config.txt using a text editor:

enable_uart=1
dtoverlay=pi3-disable-bt

Ulisses_Nogueira · May 15, 2018, 11:36am

@gjong, I did it. Now I can access the configuration page.

@marthocoo, I also did it. But nothing different happens.

On configuration page its not finding my Philips Hue Bulbs.

gjong · May 15, 2018, 1:49pm

The problem is that the deCONZ cannot find the hardware (you can see this by the firmware being set to 00000000). So you are probably facing a problem with the Raspbee not being detected. Can you check in the hassio server that the hardware is available under /dev/devTTY0?

Also see the instructions I included for the hassio addon:

Enable the UART

Shutdown the PI
Remove the SD Card and insert in a PC
Open the config.txt in the drive that automatically mounts
Add the following lines at the bottom of the file

enable_uart=1
dtoverlay=pi3-disable-btroot

Ulisses_Nogueira · May 15, 2018, 2:03pm

Sorry, but…

How can I “check in the hassio server that the hardware is available under /dev/devTTY0?”

I’m trying
core-ssh:~# hassio hw info but having this error:
Error decoding json invalid character ‘:’ after top-level value: 405: Method Not Allowed

Robban · May 15, 2018, 4:42pm

I’ve got this issue with my conbee and others have reported it as well. So that is not an indication whether or not the hardware is identified

Ulisses_Nogueira · May 15, 2018, 4:50pm

How did you solve this?

Add-On log.

17:43:09:525 dev /dev/ttyAMA0
17:43:12:145 Daylight now: solarNoon, status: 170
17:43:22:144 Daylight now: solarNoon, status: 170
17:43:32:145 Daylight now: solarNoon, status: 170
17:43:42:144 Daylight now: solarNoon, status: 170
17:43:52:145 Daylight now: solarNoon, status: 170
17:44:02:145 Daylight now: solarNoon, status: 170
17:44:12:145 Daylight now: solarNoon, status: 170
17:44:13:466 Announced to internet
17:44:13:467 discovery server date: Tue, 15 May 2018 16:44:13 GMT
17:44:13:467 	 local time seems to be ok
17:44:22:144 Daylight now: solarNoon, status: 170
17:44:32:144 Daylight now: solarNoon, status: 170
17:44:42:145 Daylight now: solarNoon, status: 170
17:44:52:144 Daylight now: solarNoon, status: 170
17:45:02:145 Daylight now: solarNoon, status: 170
17:45:12:144 Daylight now: solarNoon, status: 170
17:45:19:623 dev /dev/ttyAMA0
17:45:22:145 Daylight now: solarNoon, status: 170
17:45:32:145 Daylight now: solarNoon, status: 170
17:45:42:145 Daylight now: solarNoon, status: 170
17:45:52:145 Daylight now: solarNoon, status: 170
17:46:02:145 Daylight now: solarNoon, status: 170
17:46:12:144 Daylight now: solarNoon, status: 170
17:46:22:146 Daylight now: solarNoon, status: 170
17:46:32:145 Daylight now: solarNoon, status: 170

I’ve this about deCONZ on Hassio log.

2018-05-15 15:37:22 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/flow to 85.245.106.154 (auth: True)
2018-05-15 15:37:22 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/entry to 85.245.106.154 (auth: True)
2018-05-15 15:37:22 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/flow_handlers to 85.245.106.154 (auth: True)
2018-05-15 15:37:22 INFO (MainThread) [homeassistant.components.http.view] Serving /api/cloud/account to 85.245.106.154 (auth: True)
2018-05-15 15:37:23 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/flow/904d8ae7dcf14de881c540b5f044061b to 85.245.106.154 (auth: True)
2018-05-15 15:37:24 INFO (SyncWorker_2) [homeassistant.components.device_tracker.nmap_tracker] Scanning...
2018-05-15 15:37:24 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/flow/904d8ae7dcf14de881c540b5f044061b to 85.245.106.154 (auth: True)
2018-05-15 15:37:24 DEBUG (MainThread) [pydeconz.utils] Sending {'auth': None, 'data': b'{"devicetype": "pydeconz"}'} to http://192.168.1.71:8080/api
2018-05-15 15:37:24 ERROR (MainThread) [pydeconz.utils] HTTP status 403, response [{"error":{"address":"/","description":"link button not pressed","type":101}}].
2018-05-15 15:37:25 DEBUG (SyncWorker_9) [mpd.base] Calling MPD status()
2018-05-15 15:37:25 DEBUG (SyncWorker_9) [mpd.base] Calling MPD currentsong()
2018-05-15 15:37:27 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/flow/5120cc977cd2437b885f39f2916d48f5 to 85.245.106.154 (auth: True)
2018-05-15 15:37:28 INFO (MainThread) [homeassistant.components.http.view] Serving /api/config/config_entries/flow/5120cc977cd2437b885f39f2916d48f5 to 85.245.106.154 (auth: True)
2018-05-15 15:37:28 DEBUG (MainThread) [pydeconz.utils] Sending {'auth': None, 'data': b'{"devicetype": "pydeconz"}'} to http://192.168.1.71:80/api
2018-05-15 15:37:28 ERROR (MainThread) [pydeconz.utils] Error getting deCONZ data from http://192.168.1.71:80/api.
2018-05-15 15:37:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sun.sun, old_state=<state sun.sun=above_horizon; next_dawn=2018-05-16T04:53:59+00:00, next_dusk=2018-05-15T20:10:49+00:00, next_midnight=2018-05-16T00:32:54+00:00, next_noon=2018-05-16T12:32:54+00:00, next_rising=2018-05-16T05:23:57+00:00, next_setting=2018-05-15T19:40:56+00:00, elevation=56.86, azimuth=242.55, friendly_name=Sun @ 2018-05-15T15:31:09.948771+01:00>, new_state=<state sun.sun=above_horizon; next_dawn=2018-05-16T04:53:59+00:00, next_dusk=2018-05-15T20:10:49+00:00, next_midnight=2018-05-16T00:32:54+00:00, next_noon=2018-05-16T12:32:54+00:00, next_rising=2018-05-16T05:23:57+00:00, next_setting=2018-05-15T19:40:56+00:00, elevation=56.69, azimuth=242.85, friendly_name=Sun @ 2018-05-15T15:31:09.948771+01:00>>
2018-05-15 15:37:30 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1884052464: Sending {'id': 19, 'type': 'event', 'event': {'event_type': 'state_changed', 'data': {'entity_id': 'sun.sun', 'old_state': <state sun.sun=above_horizon; next_dawn=2018-05-16T04:53:59+00:00, next_dusk=2018-05-15T20:10:49+00:00, next_midnight=2018-05-16T00:32:54+00:00, next_noon=2018-05-16T12:32:54+00:00, next_rising=2018-05-16T05:23:57+00:00, next_setting=2018-05-15T19:40:56+00:00, elevation=56.86, azimuth=242.55, friendly_name=Sun @ 2018-05-15T15:31:09.948771+01:00>, 'new_state': <state sun.sun=above_horizon; next_dawn=2018-05-16T04:53:59+00:00, next_dusk=2018-05-15T20:10:49+00:00, next_midnight=2018-05-16T00:32:54+00:00, next_noon=2018-05-16T12:32:54+00:00, next_rising=2018-05-16T05:23:57+00:00, next_setting=2018-05-15T19:40:56+00:00, elevation=56.69, azimuth=242.85, friendly_name=Sun @ 2018-05-15T15:31:09.948771+01:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2018, 5, 15, 14, 37, 30, 606863, tzinfo=<UTC>)}}
2018-05-15 15:37:30 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1886154928: Sending {'id': 2, 'type': 'event', 'event': {'event_type': 'state_changed', 'data': {'entity_id': 'sun.sun', 'old_state': <state sun.sun=above_horizon; next_dawn=2018-05-16T04:53:59+00:00, next_dusk=2018-05-15T20:10:49+00:00, next_midnight=2018-05-16T00:32:54+00:00, next_noon=2018-05-16T12:32:54+00:00, next_rising=2018-05-16T05:23:57+00:00, next_setting=2018-05-15T19:40:56+00:00, elevation=56.86, azimuth=242.55, friendly_name=Sun @ 2018-05-15T15:31:09.948771+01:00>, 'new_state': <state sun.sun=above_horizon; next_dawn=2018-05-16T04:53:59+00:00, next_dusk=2018-05-15T20:10:49+00:00, next_midnight=2018-05-16T00:32:54+00:00, next_noon=2018-05-16T12:32:54+00:00, next_rising=2018-05-16T05:23:57+00:00, next_setting=2018-05-15T19:40:56+00:00, elevation=56.69, azimuth=242.85, friendly_name=Sun @ 2018-05-15T15:31:09.948771+01:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2018, 5, 15, 14, 37, 30, 606863, tzinfo=<UTC>)}}
 2018-05-15 15:37:35 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=device_tracker.ipaddeulisseslan, old_state=<state device_tracker.ipaddeulisseslan=home; source_type=router, latitude=38.7278727, longitude=-9.164085, gps_accuracy=0, scanner=NmapDeviceScanner, ip=192.168.1.73, friendly_name=iPad-de-Ulisses.lan @ 2018-05-15T15:31:48.551310+01:00>, new_state=<state device_tracker.ipaddeulisseslan=not_home; source_type=router, scanner=NmapDeviceScanner, ip=192.168.1.73, friendly_name=iPad-de-Ulisses.lan @ 2018-05-15T15:37:35.603615+01:00>>
2018-05-15 15:37:35 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1884052464: Sending {'id': 19, 'type': 'event', 'event': {'event_type': 'state_changed', 'data': {'entity_id': 'device_tracker.ipaddeulisseslan', 'old_state': <state device_tracker.ipaddeulisseslan=home; source_type=router, latitude=38.7278727, longitude=-9.164085, gps_accuracy=0, scanner=NmapDeviceScanner, ip=192.168.1.73, friendly_name=iPad-de-Ulisses.lan @ 2018-05-15T15:31:48.551310+01:00>, 'new_state': <state device_tracker.ipaddeulisseslan=not_home; source_type=router, scanner=NmapDeviceScanner, ip=192.168.1.73, friendly_name=iPad-de-Ulisses.lan @ 2018-05-15T15:37:35.603615+01:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2018, 5, 15, 14, 37, 35, 603779, tzinfo=<UTC>)}}
2018-05-15 15:37:35 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1886154928: Sending {'id': 2, 'type': 'event', 'event': {'event_type': 'state_changed', 'data': {'entity_id': 'device_tracker.ipaddeulisseslan', 'old_state': <state device_tracker.ipaddeulisseslan=home; source_type=router, latitude=38.7278727, longitude=-9.164085, gps_accuracy=0, scanner=NmapDeviceScanner, ip=192.168.1.73, friendly_name=iPad-de-Ulisses.lan @ 2018-05-15T15:31:48.551310+01:00>, 'new_state': <state device_tracker.ipaddeulisseslan=not_home; source_type=router, scanner=NmapDeviceScanner, ip=192.168.1.73, friendly_name=iPad-de-Ulisses.lan @ 2018-05-15T15:37:35.603615+01:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2018, 5, 15, 14, 37, 35, 603779, tzinfo=<UTC>)}}


2018-05-15 17:42:06 INFO (MainThread) [homeassistant.components.http.view] Serving /api/hassio/addons/69bb46cb_deconz/info to 85.245.106.154 (auth: True)
2018-05-15 17:42:06 INFO (MainThread) [homeassistant.components.http.view] Serving /api/hassio/addons/69bb46cb_deconz/logs to 85.245.106.154 (auth: True)