Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee) Topic is solved

[Thorgal789]

Hello,and thx ^^.

Wich one IP have you used ?
You can use Localhost or 127.0.0.1, both adress works same, local IP, they works without Network.

The future modification will be for theses ones that have domoticz on other machine than deconz.

Because I have make tries, on my side I m using 127.0.0.1, and I can disconnect my router (I plug out the ethernet cable from raspberry), all is still working.

[akhome]

I used the IP of the Pi, cause 'localhost' as a word wasn't working. Many Thanks for your tip, with IP 127.0.0.1 it's working perfectly without ethernet cable or after the router got switched off.

Need to think about sticking to Deconz now, even I would like to add a real Hue Bridge for simplicity of the light/scenes setup.

[Thorgal789]

I m not a "pro" with deCONZ, but I don"t see what can have the Hue bridge that deCONZ don't have, they use the same API (deconz copy their API), and Phoscon have new features every week > https://doc.phoscon.de/app/doc.html?ref=gh&cl=20543

BTW, on my side, I prefer use domoticz to make scene.

[akhome]

Hue has the entertainment API, more Apps that support it, a better WAF and most important I think stability of some connections should be better. Hue seems to be the best consumer effect lighting system available, but if it comes to home automation Deconz is far supperior. I think Hue allone isn't useable as a smart lighting System, if your not willing to make a lot of compromises and spend a lot of money. I don't want to remove all light switches and replace all bulps, plan to exchange the swtches with Xiami wired Zigbee Switches and add RGB effect lighting to some free standing lamps as well as via LED strips.
Both don't support the kind of rules/automations I want, that requires Domoticz anyway.

I had to try at least 20 times (with updates for both in between) until finally my Harmony found Deconz and could control it. I gave up several times in between and waited a few weeks for the next update. Currently not using the latest version of Deconz, cause I read about some issues and don't want to break anything until an update brings a few real improvements. I still would recommend Deconz to anyone willing to spend some time setting it up for a cheap smarthome installation. My main reason to get the raspbee was that it could make the connection between quite cheap Xiaomi Sensors, open source Software with great rules/scrips and lights of several brands. With Deconz it's possible to connect and monitor a lot by using affordable sensors and switches.

Before I got the raspbee, I thought Domoticz would be the right "rules engine" for me.
Since your plugin wasn't available at that time and I had some issues with the first install I ended up trying 3 alternatives.
With no Linux experience it was a lot of work to get all this setups done. I can afterwards say that I learned a lot, but also that tinkering with complex rules/scrips to get the automations I want to work is much more fun to me.
If it wouldn't limit automations to a terrible scripting language and a super limited alpha status grafical interface I might have choosen to use HA, how easily it connects to several hardware and the design of the main interface are fantastic. OH is a combination of several alpha status interfaces, seems to be great for people completly ignorring any of this and just use it file based. Had some great expiriences with ioBroker that allows to progam and react on anything with Blockly, but sice it shows too much data and takes too much resources/RAM I tried again with Domoticz and I'm very happy with it's possiblities now. For me the only issue is that variables can't be used in the events/rules to trigger anything, I just use dummy switches instead.

Anything I need for the main light setup will run via Deconz/Domoticz combination in the near future including motion and contact sensors that already contol waterpump and coffee machine.
For effect lights I'm still unsure how I will set them up.

[Thorgal789]

Lol, yeah the deconz update are something special, same anxiety here ^^.
I know, there is backup, I can roolback, and bugs will be fixed the next week, but I m always 3/4 version late, and everytime I make an update it's like I defused a bomb.

For API, deconz mimic hue API , their objective is Philips Hue applications to work unaltered with deCONZ.

I don't have HUE hardware, so I can't make test, I know philips have better hardware but I thought deconz one was better than that, your problem with Harmony was because a missing feature (touchlink ?) or random working mode ?

[Minglarn]

Hi... Just updating my testing period and how I moved on..

Well... installed deConz plugin to same RPI as domoticz... After a couple of hours I noticed that the CPU usage was sky rocket.. around 30% where it should bee more like 2.5% .. Could be a coincidence but after a test run for 2 weeks I see a big difference.. Installed my cpu usage gets high... de installed and it gets low again..

And when installed on my Domoticz RPI3 it sometimes drops the sensors.. Think it's a bug in the Conbee FW, but seems to work without dropouts when running on my RPI1 ..

So i deiced to move the Conbee usb stick to a old RPI1 i've laying round.. Installed the deConz and attached the USB. Works like a charm ..

But I must say...

[Thorgal789]

Hello,
Strange, you have the same deCONZ version on the Pi1 and the Pi3 ? On my side I m still on 2.05.55
Apparently its not because of firmware. You have see if it's deconz or domoticz that take so much cpu usage ?
30% is really too much, you have see this issue https://github.com/dresden-elektronik/d ... ssues/1255 ?

So now you have domoticz on the PI3 and deconz on the PI1, or you are using only deCONZ ? On your previous test, have you used 'localhost' or your local IP in the hardware configuration ?
BTW, you have edited the python file yourself ? because on the actual version it's not possible to use this kind of configuration.

[Minglarn]

I've disabled the deCONZ package on my Domoticz and installed it on a old RPI.
Don't really know how to check for deconz-latest.deb version.

And yes... It's installed on a separate RPI (RPI1 actually) and the USB is attached to that one.
The version is:

0Skärmklipp.JPG (15.02 KiB) Viewed 7855 times

The new version was running on my Domoticz a couple of days.... but the CPU was still high.. after disabling it went down to approx 2% again.
And yes... The Domoticz on RP3 and deCONZ on a RP1.
So Domoticz is requesting info from my RP1 and I've this settings in my hardware page:

00Skärmklipp.JPG (14.92 KiB) Viewed 7855 times

where my RP1 is using the IP: 192.168.1.181
and Domoticz is using: 192.168.1.59

No editing the code whatsoever..

[Thorgal789]

To see deconz version.
- on deCONZ : Help / about deconz.
- on phoscon : Setting / gateway (like you have done).

ATM on the PI1, you have the lasted one (with the corrective, but it don't mean it is without bug).

But I can't understand why it works on your side, see some posts before you, websocket can't works with standard version, because I m using "127.0.0.1" as domoticz ip (coded in hard, line 53 in plugin.py), the beta have been corrected but not in master branch. To resume, you can send command, but you can't receive them if domoticz isn't on same machine than deconz.

I can't say if the problem is from deCONZ or domoticz, but on deconz, some users had this kind of bug because of upnp. They have disabled it.
To make try, you can disable deconz ssdp service by editing systemd file and append --upnp=0 or use it in command line. But it's just for test because with this command your gateway will be invisible for other machine on your network.

[Minglarn]

Im glad it does... And it works well..
Even restarted Domoticz several times to be sure..
My netstat shows:

Code: Select all

pi@domo:~ $ sudo netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      512/sshd
tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN      776/sshd: pi@pts/0
tcp6       0      0 :::22                   :::*                    LISTEN      512/sshd
tcp6       0      0 ::1:6010                :::*                    LISTEN      776/sshd: pi@pts/0
tcp6       0      0 :::8443                 :::*                    LISTEN      513/domoticz
tcp6       0      0 :::6144                 :::*                    LISTEN      513/domoticz
tcp6       0      0 :::8080                 :::*                    LISTEN      513/domoticz
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           350/avahi-daemon: r
udp        0      0 0.0.0.0:56735           0.0.0.0:*                           350/avahi-daemon: r
udp        0      0 0.0.0.0:68              0.0.0.0:*                           490/dhcpcd
udp6       0      0 :::5353                 :::*                                350/avahi-daemon: r
udp6       0      0 :::60040                :::*                                350/avahi-daemon: r

And what I can see on my Domoticz (or not) is that deCONZ is not running..

From the log in Domoticz everything looks good.
Yes, i see that the IP is hardcoded in line 53..

Including the log from a restart here if it helps.

Code: Select all

2019-02-26 07:41:41.134 Status: (ConBee USB) Started.
2019-02-26 07:41:42.033 Status: (ConBee USB) Entering work loop.
2019-02-26 07:41:42.034 Status: (ConBee USB) Initialized version 1.0.4, author 'Smanar'
2019-02-26 07:41:43.761 (ConBee USB) onStart called
2019-02-26 07:41:43.816 (ConBee USB) onConnect called
2019-02-26 07:41:43.867 (ConBee USB) Websocket Http data : HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: V0htEbn5FhIA1xfQRyG3yU1aG9c=
Server: deconz
Access-Control-Allow-Credentials: false
Access-Control-Allow-Methods: GET
Access-Control-Allow-Headers: content-type
Access-Control-Allow-Origin: http://127.0.0.1
Date: Tue, 26 Feb 2019 06:41:50 GMT

2019-02-26 07:41:43.816 Status: (ConBee USB) Laucnhing websocket
2019-02-26 07:41:53.282 (ConBee USB) ### Request lights
2019-02-26 07:41:53.283 (ConBee USB) Send Command /api/0CF2D60566/lights/ with None
2019-02-26 07:41:53.333 (ConBee USB) onConnect called
2019-02-26 07:41:53.384 (ConBee USB) Classic Data : {}
2019-02-26 07:41:53.384 (ConBee USB) ### Request sensors
2019-02-26 07:41:53.384 (ConBee USB) Send Command /api/0CF2D60566/sensors/ with None
2019-02-26 07:41:53.485 (ConBee USB) onConnect called
2019-02-26 07:41:53.536 (ConBee USB) Incomplete trame, miss 751 bytes
2019-02-26 07:41:53.542 (ConBee USB) Classic Data : {'1': {'uniqueid': '00:21:2e:ff:ff:03:25:d2-01', 'etag': '276a14260deb4da44b844262e084fda0', 'config': {'configured': True, 'sunriseoffset': 30, 'sunsetoffset': -30, 'on': True}, 'manufacturername': 'Philips', 'type': 'Daylight', 'state': {'status': 150, 'daylight': True, 'dark': False, 'lastupdated': '2019-02-26T06:26:27'}, 'swversion': '1.0', 'modelid': 'PHDL00', 'name': 'Daylight'}, '4': {'uniqueid': '00:15:8d:00:03:11:67:91-01-0006', 'etag': 'eef0b49d3256ed61c9b807d00506d067', 'config': {'temperature': 0, 'battery': 100, 'reachable': True, 'on': True}, 'manufacturername': 'LUMI', 'type': 'ZHAOpenClose', 'state': {'open': False, 'lastupdated': '2019-02-25T19:33:57'}, 'name': 'Window / Door Sensor', 'ep': 1, 'modelid': 'lumi.sensor_magnet'}, '5': {'uniqueid': '00:15:8d:00:03:11:68:04-01-0006', 'etag': 'b41a35f8b80b239cac5644637f598a39', 'config': {'temperature': 0, 'battery': 100, 'reachable': True, 'on': True}, 'manufacturername': 'LUMI', 'type': 'ZHAOpenClose', 'state': {'open': False, 'lastupdated': '2019-02-25T12:18:12'}, 'name': 'OpenClose 5', 'ep': 1, 'modelid': 'lumi.sensor_magnet'}, '3': {'uniqueid': '00:15:8d:00:03:05:71:27-01-0406', 'etag': '3ab67e2df9a24e0b526b387b95fbdd8c', 'config': {'duration': 90, 'battery': 100, 'reachable': True, 'on': True, 'temperature': 0}, 'manufacturername': 'LUMI', 'type': 'ZHAPresence', 'state': {'presence': False, 'lastupdated': '2019-02-25T20:04:54'}, 'name': 'Motion Sensor (2)', 'ep': 1, 'modelid': 'lumi.sensor_motion'}, '6': {'uniqueid': '00:15:8d:00:02:f8:96:39-01-0006', 'etag': '8dcf439802820f04583c0fcc6c7c8bdb', 'config': {'battery': 100, 'reachable': True, 'on': True}, 'manufacturername': 'LUMI', 'type': 'ZHASwitch', 'state': {'buttonevent': 1004, 'lastupdated': '2019-02-25T12:27:43'}, 'name': 'Smart Switch', 'ep': 1, 'mode': 1, 'modelid': 'lumi.sensor_switch'}, '2': {'uniqueid': '00:15:8d:00:03:05:71:cc-01-0406', 'etag': '02095a1f9423b77f4ce4e75d3c83defb', 'config': {'duration': 90, 'battery': 100, 'reachable': True, 'on': True, 'temperature': 0}, 'manufacturername': 'LUMI', 'type': 'ZHAPresence', 'state': {'presence': False, 'lastupdated': '2019-02-26T06:35:50'}, 'name': 'Motion Sensor', 'ep': 1, 'modelid': 'lumi.sensor_motion'}}
2019-02-26 07:41:53.542 (ConBee USB) ### Device > 1 Name:Daylight Type:Daylight Details:{'status': 150, 'daylight': True, 'dark': False, 'lastupdated': '2019-02-26T06:26:27'}
2019-02-26 07:41:53.661 (ConBee USB) ### Update device (ConBee USB - Daylight) : {'sValue': 'On', 'nValue': 1}, IGNORED , no changes !
2019-02-26 07:41:53.661 (ConBee USB) ### Device > 4 Name:Window / Door Sensor Type:ZHAOpenClose Details:{'open': False, 'lastupdated': '2019-02-25T19:33:57'}
2019-02-26 07:41:53.662 (ConBee USB) ### Update device (ConBee USB - Window / Door Sensor) : {'BatteryLevel': 100, 'sValue': 'Closed', 'nValue': 0}, IGNORED , no changes !
2019-02-26 07:41:53.663 (ConBee USB) ### Device > 5 Name:OpenClose 5 Type:ZHAOpenClose Details:{'open': False, 'lastupdated': '2019-02-25T12:18:12'}
2019-02-26 07:41:53.663 (ConBee USB) ### Update device (ConBee USB - OpenClose 5) : {'BatteryLevel': 100, 'sValue': 'Closed', 'nValue': 0}, IGNORED , no changes !
2019-02-26 07:41:53.663 (ConBee USB) ### Device > 3 Name:Motion Sensor (2) Type:ZHAPresence Details:{'presence': False, 'lastupdated': '2019-02-25T20:04:54'}
2019-02-26 07:41:53.664 (ConBee USB) ### Update device (ConBee USB - Motion Sensor (2)) : {'BatteryLevel': 100, 'sValue': 'Off', 'nValue': 0}, IGNORED , no changes !
2019-02-26 07:41:53.664 (ConBee USB) ### Device > 6 Name:Smart Switch Type:ZHASwitch Details:{'buttonevent': 1004, 'lastupdated': '2019-02-25T12:27:43'}
2019-02-26 07:41:53.665 (ConBee USB) ### Update device (ConBee USB - Smart Switch) : {'BatteryLevel': 100, 'sValue': 'Off', 'nValue': 0}, IGNORED , no changes !
2019-02-26 07:41:53.665 (ConBee USB) ### Device > 2 Name:Motion Sensor Type:ZHAPresence Details:{'presence': False, 'lastupdated': '2019-02-26T06:35:50'}
2019-02-26 07:41:53.666 (ConBee USB) ### Update device (ConBee USB - Motion Sensor) : {'BatteryLevel': 100, 'sValue': 'Off', 'nValue': 0}, IGNORED , no changes !
2019-02-26 07:41:53.666 (ConBee USB) ### Request Groups
2019-02-26 07:41:53.666 (ConBee USB) Send Command /api/0CF2D60566/groups/ with None
2019-02-26 07:41:53.767 (ConBee USB) onConnect called
2019-02-26 07:41:53.818 (ConBee USB) Classic Data : {'1': {'etag': '276a14260deb4da44b844262e084fda0', 'state': {'any_on': False, 'all_on': False}, 'lights': [], 'devicemembership': [], 'type': 'LightGroup', 'action': {'effect': 'none', 'scene': None, 'on': False, 'ct': 0, 'sat': 127, 'colormode': 'hs', 'xy': [0, 0], 'bri': 127, 'hue': 0}, 'name': 'Test', 'id': '1', 'scenes': []}}
2019-02-26 07:41:53.818 (ConBee USB) ### Groupe > 1 Name:Test
2019-02-26 07:41:53.818 Status: (ConBee USB) ### deCONZ ready
2019-02-26 07:41:53.818 Status: (ConBee USB) ### Found 0 Operators, 6 Sensors, 1 Groups with 0 Ignored

[Thorgal789]

So if deCONZ is on win 10 it don't work, but works fine on Pi1 (with domoticz on other PI) ?
And on same port, perhaps raspbian is more permissive, but it's still strange for me.
I have take a look, on my side the 443 port is already used by domoticz. So it's perhaps for that deCONZ have choose 8088.

Code: Select all

pi@raspberrypi:~ $ sudo netstat -tulpn
Connexions Internet actives (seulement serveurs)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat        PID/Program name
tcp        0      0 0.0.0.0:5900            0.0.0.0:*               LISTEN      504/vncserver-x11-c
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      10422/deCONZ
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      516/sshd
tcp        0      0 0.0.0.0:8088            0.0.0.0:*               LISTEN      10422/deCONZ
tcp6       0      0 :::5900                 :::*                    LISTEN      504/vncserver-x11-c
tcp6       0      0 :::5008                 :::*                    LISTEN      10422/deCONZ
tcp6       0      0 :::8080                 :::*                    LISTEN      524/domoticz
tcp6       0      0 :::22                   :::*                    LISTEN      516/sshd
tcp6       0      0 :::443                  :::*                    LISTEN      524/domoticz
tcp6       0      0 :::6144                 :::*                    LISTEN      524/domoticz
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           10422/deCONZ
udp        0      0 0.0.0.0:68              0.0.0.0:*                           338/dhcpcd
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           279/avahi-daemon: r
udp        0      0 0.0.0.0:49464           0.0.0.0:*                           279/avahi-daemon: r
udp6       0      0 :::40518                :::*                                279/avahi-daemon: r
udp6       0      0 :::5353                 :::*                                279/avahi-daemon: r

[Thorgal789]

New version, now groups are working perfectly.

All groups are now show as a color bulb with all settings possibles (color level, temperature level, dimmer) regardless of the mode they have in deconz. Its now your job to send the correct command to the group.

For exemple, if in the same group you have 5 color bulbs and a bulb with simple dimmer, it's useless to send a color command to this group.

To enable it, just delete your deconz group from domoticz, and restart the plugin (hardware / select deconz / update), it will re create your group with this kind of device.

[Minglarn]

Nice!
Will try this out soon...

[akhome]

I got one original Hue Bulb and tested DeConz with some Android Apps, 50% of them are working with DeConz the other half doesn't connect. The Kodi Plugin I tried couldn't find the DeConz Gateway. Some started to move animated scenes to entertainment api, this might cause more incompatibly in future.

Logitech Harmony was the same, it didn't had a touchlink issue. It just didn't found the gateway or found the gateway, but even after ten attempts to connect it didn't work. Not sure why, but it's was suddenly working after software updates on both sides.

The DeConz/Domoticz connected by your plugin are running nonstop for the last couple of weeks. Within 3 weeks I had two mayor issues, one time the pi was unreachable (web app and ssh), had to pull the plug to reboot. One time the connection between DeConz and Domoticz got strange problems: Switch buttons and Blockly events in Domoticz could still control plugs via DeConz, but didn't got sensor updates, that caused my waterpump to run while it shouldn't. Might be the same issue Minglarn described, since I have the raspbee connected to the same Pi 3 that is running Domoticz. Will try to update everything when I have time and monitor how it works afterwards.

[Thorgal789]

For Hue bulb, to connect, are you using the touchlink function or the remote ?
I have never see a post with kodi + deconz, IDK if it can work, (I have only found this 1 years old post https://community.home-assistant.io/t/e ... conz/44909) but some things I know
- In the Phoscon App you need enable app authentication for 60 seconds (like for alexa).
- deCONZ need to use the port 80 (for alexa, IDK for the kodi plugin).

For Minglarn issue, easy to see if it's the same problem, just look at the proccessor use.
You are using headless mode ?
You don't have something interesting in your logs in your second isues ? When the websocket have stoped working ?
Wich one deconz are you using ? the last one is not necessarily the better (the 2.05.58 have the cpu problem). On my side I m still on 2.05.55 with domoticz and deconz on same Pi3.

[Minglarn]

Since I moved deCONZ to its own RPI i've hade no issues whatsoever...
May bee one minor... but that was easy resolved.
The isssue was that I did loose connection to some of my sensors and switches.

Easy fixed by changing the ZigBee channel to 25. Think there was some interference with Philips HUE. That was 7 days ago.

Code: Select all

top - 11:26:47 up 8 days, 23:45,  1 user,  load average: 0.60, 0.50, 0.41

[akhome]

The Hue Bulb was new and didn't needed touchlink, Deconz found it and conneced without issues. Control via Domoticz is possible.

I used authentication for 60 sec. for any android apps, Harmony and Kodi Hue plugin. My DeConz is on Port 80, Domoticz is moved to another port. Android apps Hue Essentials and all4hue are working fine, same for current version of Harmony app. Some other Hue apps and Kodi plugin don't connect even I opened authentication several times to retry.

After the second issue I immediately rebooted the Pi vis SSH. Have it running headless and needed to stop the wrong behavior of my waterpump asap. Will check if I can still find anything interesting in the log.

[Thorgal789]

"I got one original Hue Bulb and tested DeConz with some Android Apps, 50% of them are working with DeConz the other half doesn't connect"
So you finnaly have them working ?

For kodi plugin, I m sorry, but I think it's a missing feature, if it works for other application, I don't think it's a configuration problem. You can ask on their github but as it's not an official feature, not sure they can do something.

Are you using the official SD image for raspberry or you have make a complete install yourself ? I m asking because I have more bad returns from users that using headless mode than users using GUI, freeze usually.

[akhome]

Android apps Hue Essentials and all4hue are working fine, Harmony is now working too. HueManic, hueReact and Hue Matcher are not working. That's 50% of the hue apps I tried working with DeConz for me.

I didn't found any usefull information if Kodi Plugins for ambilight effects might work too. For theater mode no plugin is needed, Domoticz can do this any way I want. Tried the most common one and couldn't connect. I found information that it should work with do it yourself hue (that is supporting DeConz). As a Linux noop I don't like to install another software that seems to be pretty hard to setup only to increase the compatiblity of yhe API simulation for now.

I used the latest headless raspbian image and installed DeConz and Domoticz on my own to get the most lightweight setup possible. Since I read on dresden elektronik githup there are some further settings for Xiaomi sensors possible in the gui and you also say it might be more stable with your plugin I will make a new intallation with GUI. Would you recommend to start with Phoscon or Raspbian image?

[Thorgal789]

Haaa ok, was 50% of applications, in fact you are testing the HUE emulation ^^.
On my side, I have instaled the last Raspbian image, and I have installed domoticz then deconz. I prefer that than an image I don"t know how the system is configured (but I think less optimised than the deconz image).
I can't say if the GUI is more stable, but this version is less "nested" in the system, and I have less bad return with it.
And yes there is more setting with the GUI, I m using it for exemple for device that are not supported natively by deconz, but all xioami setting (sensitivity of the vibration sensor for exemple) can be edited using the REST api, but the GUI is realy more "friendly use".

But to make a try, you can just disable the headless version and enable the GUI version (4 command lines from my memory), and never instal VNC client, use the builtin one in Raspbian (in raspi-config) if you need VNC connexion.
If you have installed deconz yourself, I think It will be same, for me, to make a try, you don't need to re instal the whole system, just switch the version.

Edit:
Oups, I have forget you have the headless Raspbian version.