Domoticz

Posted: **Tuesday 02 April 2019 20:09**

Doesnt work at all. Also i see there is no device-state change. So if i for e.g. shut of the osram switch in phoscon, the device state in domoticz is still "ON"

Code: Select all

 2019-04-02 20:03:37.392 (deconz) Pushing 'onHeartbeatCallback' on to queue
2019-04-02 20:03:37.396 (deconz) Processing 'onHeartbeatCallback' message
2019-04-02 20:03:37.396 (deconz) Calling message handler 'onHeartbeat'.
2019-04-02 20:03:37.396 (deconz) onHeartbeat called

This is the only message i get in Log with enabled debug. Even if the temperatur changes or i shot on/off a switch.

Now i got tis message after some time. Seems to be the virtual device in phoscon:

Code: Select all

 2019-04-02 20:10:37.466 (deconz) onHeartbeat called
2019-04-02 20:10:46.990 (deconz) Pushing 'ReadEvent' on to queue
2019-04-02 20:10:47.032 (deconz) Processing 'ReadEvent' message
2019-04-02 20:10:47.032 (deconz) Received 182 bytes of data
2019-04-02 20:10:47.032 (deconz) 81 7e 00 b2 7b 22 65 22 3a 22 63 68 61 6e 67 65 64 22 2c 22 �~.�{"e":"changed","
2019-04-02 20:10:47.032 (deconz) 69 64 22 3a 22 31 22 2c 22 72 22 3a 22 73 65 6e 73 6f 72 73 id":"1","r":"sensors
2019-04-02 20:10:47.032 (deconz) 22 2c 22 73 74 61 74 65 22 3a 7b 22 64 61 72 6b 22 3a 74 72 ","state":{"dark":tr
2019-04-02 20:10:47.033 (deconz) 75 65 2c 22 64 61 79 6c 69 67 68 74 22 3a 66 61 6c 73 65 2c ue,"daylight":false,
2019-04-02 20:10:47.033 (deconz) 22 6c 61 73 74 75 70 64 61 74 65 64 22 3a 22 32 30 31 39 2d "lastupdated":"2019-
2019-04-02 20:10:47.033 (deconz) 30 34 2d 30 32 54 31 38 3a 31 30 3a 34 37 22 2c 22 73 74 61 04-02T18:10:47","sta
2019-04-02 20:10:47.033 (deconz) 74 75 73 22 3a 32 30 30 7d 2c 22 74 22 3a 22 65 76 65 6e 74 tus":200},"t":"event
2019-04-02 20:10:47.033 (deconz) 22 2c 22 75 6e 69 71 75 65 69 64 22 3a 22 30 30 3a 32 31 3a ","uniqueid":"00:21:
2019-04-02 20:10:47.033 (deconz) 32 65 3a 66 66 3a 66 66 3a 30 33 3a 63 64 3a 35 65 2d 30 31 2e:ff:ff:03:cd:5e-01
2019-04-02 20:10:47.033 (deconz) 22 7d .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. "}
2019-04-02 20:10:47.033 (deconz) Pushing 'onMessageCallback' on to queue
2019-04-02 20:10:47.033 (deconz) Processing 'onMessageCallback' message
2019-04-02 20:10:47.033 (deconz) Calling message handler 'onMessage'.
2019-04-02 20:10:47.033 (deconz) onMessage called
2019-04-02 20:10:47.034 (deconz) ###### WebSocket Data : {'id': '1', 'state': {'dark': True, 'status': 200, 'lastupdated': '2019-04-02T18:10:47', 'daylight': False}, 't': 'event', 'e': 'changed', 'r': 'sensors', 'uniqueid': '00:21:2e:ff:ff:03:cd:5e-01'}
2019-04-02 20:10:47.035 (deconz) ### Update device (deconzx) : {'nValue': 0, 'sValue': 'Off'}, IGNORED , no changes !
2019-04-02 20:10:47.463 (deconz) Pushing 'onHeartbeatCallback' on to queue
2019-04-02 20:10:47.486 (deconz) Processing 'onHeartbeatCallback' message
2019-04-02 20:10:47.486 (deconz) Calling message handler 'onHeartbeat'.

Posted: **Tuesday 02 April 2019 20:23**

So effectively you have a problem.
Can you send me the log when you restart the plugin (with the "update button"), for log you can just select "debug info only", it's the first one, perhaps it's called "python only".
You can use something like pastebin for log.

And yep, this one is the virtual device.

Posted: **Tuesday 02 April 2019 21:08**

If you are with GUI mode, pls take a look in deconz if your devices are still connected, because for me all is working, you have websocket notification and deconz have detected 2 devices and 3 sensors, so normal connexion is working too.
Wich one deCONZ version are you using ?

Posted: **Tuesday 02 April 2019 21:32**

Here i the Log after acivating debug and restart the plugin:

Code: Select all

 2019-04-02 21:27:37.216 (deconz) onStop called
2019-04-02 21:27:37.417 (deconz) onStart called
2019-04-02 21:27:37.469 (deconz) Your haven't use 127.0.0.1 as IP, so I suppose deCONZ and Domoticz aren't on same machine
2019-04-02 21:27:37.469 (deconz) Taking 192.168.178.32 as Domoticz IP
2019-04-02 21:27:37.469 (deconz) Debug logging mask set to: PYTHON
2019-04-02 21:27:37.520 (deconz) onConnect called
2019-04-02 21:27:37.670 (deconz) onMessage called
2019-04-02 21:27:37.671 (deconz) 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://192.168.178.32 Date: Tue, 02 Apr 2019 19:27:37 GMT
2019-04-02 21:27:37.184 Status: (deconz) Stop directive received.
2019-04-02 21:27:37.184 Status: (deconz) Exiting work loop.
2019-04-02 21:27:37.216 Status: (deconz) onDisconnect called for Name: 'deCONZ_WebSocket', Transport: 'TCP/IP', Protocol: 'None', Address: '192.168.178.20', Port: '8088', Baud: -1, Connected: False
2019-04-02 21:27:37.284 Status: (deconz) Stopping threads.
2019-04-02 21:27:37.285 Status: (deconz) Stopped.
2019-04-02 21:27:37.285 Status: (deconz) Started.
2019-04-02 21:27:37.413 Status: (deconz) Entering work loop.
2019-04-02 21:27:37.414 Status: (deconz) Initialized version 1.0.5, author 'Smanar'
2019-04-02 21:27:37.520 Status: (deconz) Launching websocket on port 8088
2019-04-02 21:27:37.217 Error: CConnection_disconnect, disconnection request from 'deconz' ignored. Transport does not exist.
2019-04-02 21:27:44.301 (ccc) General/kWh (kWh MeterEntertain)
2019-04-02 21:27:47.437 (deconz) onHeartbeat called
2019-04-02 21:27:47.437 (deconz) ### Request lights
2019-04-02 21:27:47.437 (deconz) Send Command /api/102E72763A/lights/ with None
2019-04-02 21:27:47.488 (deconz) onConnect called
2019-04-02 21:27:47.539 (deconz) onMessage called
2019-04-02 21:27:47.541 (deconz) Classic Data : {'1': {'etag': '9d82495c3619247f69464aa204b74a30', 'name': 'Light 1', 'type': 'Color light', 'state': {'xy': [0.146654, 0.253498], 'effect': 'none', 'on': False, 'hue': 0, 'bri': 244, 'sat': 0, 'colormode': 'xy', 'alert': 'none', 'reachable': False}, 'manufacturername': 'IKEA of Sweden', 'uniqueid': 'd0:cf:5e:ff:fe:22:73:69-01', 'swversion': '1.3.002', 'modelid': 'TRADFRI bulb E27 CWS opal 600lm', 'hascolor': True, 'ctmax': 454, 'ctmin': 250}, '2': {'etag': '5fe4b10b3b25b7562b5c3d7ba76e4322', 'name': 'Leselampe', 'type': 'On/Off plug-in unit', 'state': {'on': True, 'alert': 'none', 'reachable': True}, 'manufacturername': 'OSRAM', 'modelid': 'Plug 01', 'hascolor': False, 'swversion': 'V1.04.12', 'uniqueid': '7c:b0:3e:aa:0a:03:08:2a-03'}}
2019-04-02 21:27:47.541 (deconz) ### Device > 1 Name:Light 1 Type:Color light Details:{'xy': [0.146654, 0.253498], 'effect': 'none', 'on': False, 'hue': 0, 'bri': 244, 'sat': 0, 'colormode': 'xy', 'alert': 'none', 'reachable': False}
2019-04-02 21:27:47.542 (deconz) ### Update device (Standoben) : {'nValue': 0, 'sValue': 'Off', 'Color': '{"b":255,"cw":0,"g":201,"m":3,"r":0,"t":0,"ww":0}'}
2019-04-02 21:27:47.551 (deconz) ### Device > 2 Name:Leselampe Type:On/Off plug-in unit Details:{'on': True, 'alert': 'none', 'reachable': True}
2019-04-02 21:27:47.608 (deconz) ### Update device (Leselampe) : {'nValue': 0, 'sValue': 'Off'}, IGNORED , no changes !
2019-04-02 21:27:47.609 (deconz) ### Request sensors
2019-04-02 21:27:47.609 (deconz) Send Command /api/102E72763A/sensors/ with None
2019-04-02 21:27:47.660 (deconz) onConnect called
2019-04-02 21:27:47.711 (deconz) onMessage called
2019-04-02 21:27:47.714 (deconz) Classic Data : {'1': {'etag': '4342cc22a1e713242ddac6143e7fb992', 'name': 'Daylight', 'type': 'Daylight', 'state': {'dark': True, 'status': 220, 'lastupdated': '2019-04-02T19:21:43', 'daylight': False}, 'manufacturername': 'Philips', 'uniqueid': '00:21:2e:ff:ff:03:cd:5e-01', 'modelid': 'PHDL00', 'swversion': '1.0', 'config': {'on': True, 'sunriseoffset': 30, 'configured': True, 'sunsetoffset': -30}}, '3': {'etag': 'ec0ed252f66ded2fea74ee4b251b13a8', 'name': 'Multisensor', 'type': 'ZHAHumidity', 'state': {'humidity': 4992, 'lastupdated': '2019-04-02T19:03:59'}, 'ep': 1, 'uniqueid': '00:15:8d:00:02:e6:a8:dc-01-0405', 'modelid': 'lumi.sensor_ht', 'manufacturername': 'LUMI', 'swversion': '20160516', 'config': {'on': True, 'offset': 0, 'battery': 100, 'reachable': True}}, '2': {'etag': 'ec0ed252f66ded2fea74ee4b251b13a8', 'name': 'Multisensor', 'type': 'ZHATemperature', 'state': {'temperature': 2138, 'lastupdated': '2019-04-02T19:03:59'}, 'ep': 1, 'uniqueid': '00:15:8d:00:02:e6:a8:dc-01-0402', 'modelid': 'lumi.sensor_ht', 'manufacturername': 'LUMI', 'swversion': '20160516', 'config': {'on': True, 'offset': 0, 'battery': 100, 'reachable': True}}}
2019-04-02 21:27:47.714 (deconz) ### Device > 1 Name:Daylight Type:Daylight Details:{'dark': True, 'status': 220, 'lastupdated': '2019-04-02T19:21:43', 'daylight': False}
2019-04-02 21:27:47.715 (deconz) ### Update device (deconzx) : {'nValue': 0, 'sValue': 'Off'}, IGNORED , no changes !
2019-04-02 21:27:47.715 (deconz) ### Device > 3 Name:Multisensor Type:ZHAHumidity Details:{'humidity': 4992, 'lastupdated': '2019-04-02T19:03:59'}
2019-04-02 21:27:47.715 (deconz) ### Update device (Feuchtigkeit Arbeitszimmer) : {'nValue': 49, 'BatteryLevel': 100, 'sValue': '0'}
2019-04-02 21:27:47.721 (deconz) ### Device > 2 Name:Multisensor Type:ZHATemperature Details:{'temperature': 2138, 'lastupdated': '2019-04-02T19:03:59'}
2019-04-02 21:27:47.722 (deconz) ### Update device (Temperatur Arbeitszimmer) : {'nValue': 0, 'BatteryLevel': 100, 'sValue': '21.38'}
2019-04-02 21:27:47.727 (deconz) ### Request Groups
2019-04-02 21:27:47.727 (deconz) Send Command /api/102E72763A/groups/ with None
2019-04-02 21:27:47.779 (deconz) onConnect called
2019-04-02 21:27:47.829 (deconz) onMessage called
2019-04-02 21:27:47.832 (deconz) Classic Data : {'1': {'etag': '5fe4b10b3b25b7562b5c3d7ba76e4322', 'name': 'Wohnzimmer', 'id': '1', 'scenes': [], 'state': {'any_on': True, 'all_on': True}, 'action': {'xy': [0, 0], 'effect': 'none', 'on': True, 'scene': None, 'hue': 0, 'bri': 127, 'sat': 127, 'colormode': 'hs', 'ct': 0}, 'type': 'LightGroup', 'devicemembership': [], 'lights': ['1', '2']}, '2': {'etag': '5945e529a2dedecd42005a3f175d9c33', 'name': 'Arbeitszimmer', 'id': '2', 'scenes': [], 'state': {'any_on': False, 'all_on': False}, 'action': {'xy': [0, 0], 'effect': 'none', 'on': False, 'scene': None, 'hue': 0, 'bri': 128, 'sat': 128, 'colormode': 'hs', 'ct': 0}, 'type': 'LightGroup', 'devicemembership': [], 'lights': []}}
2019-04-02 21:27:47.832 (deconz) ### Groupe > 1 Name:Wohnzimmer
2019-04-02 21:27:47.832 (deconz) ### Groupe > 2 Name:Arbeitszimmer
2019-04-02 21:27:47.832 Status: (deconz) ### deCONZ ready
2019-04-02 21:27:47.833 Status: (deconz) ### Found 2 Operators, 3 Sensors, 2 Groups with 0 Ignored
2019-04-02 21:27:57.449 (deconz) onHeartbeat called
2019-04-02 21:28:07.466 (deconz) onHeartbeat called
2019-04-02 21:28:17.433 (deconz) onHeartbeat called

Raspbee Version:
Version 2.05.59 / 14.2.2019
Firmware 262F0500

For my understanding its a problem with the websocket connection. Is there a way to check the connection?

Posted: **Tuesday 02 April 2019 21:58**

Ok found the Problem. Dont know why, but the port of the websocket has changed in deconz. Got the config with: GET api/<apikey> and saw that the port has changed to 443 instead of the 8088 which is set in Domoticz plugin.

Sorry for that. I appologize for stealig your time, but maybe it help anybody else if there is a similar Problem in future.

Posted: **Tuesday 02 April 2019 22:02**

Nope all is fine, if websocket have failed you will have it in this log, and mainly it will not work with the build in sensor "daylight".

Don't take care at
"2019-04-02 21:27:37.217 Error: CConnection_disconnect, disconnection request from 'deconz' ignored. Transport does not exist."
or
"2019-04-02 21:44:28.543 Error: CConnection_disconnect, disconnection request from 'deCONZ' ignored. Transport does not exist."
you will have it everytime you will reset the plugin.

All are good in your log , except you have the "Light 1" "Standoben" in not reachable state.
Timestamp look good too
"2019-04-02 21:27:47.721 (deconz) ### Device > 2 Name:Multisensor Type:ZHATemperature Details:{'temperature': 2138, 'lastupdated': '2019-04-02T19:03:59'}"
21h27 and last seen 19:03 so for me it's good too.

You don't have deconz and domoticz on same machine ?

I have the second thermo sensor generation perhaps they don't work same, but you need to have at least 1 websocket notification for 2h working duration (for battery) even the temperature is the same.

But easier to debug : the plug.
When you click it on domoticz you need to have in log.

2019-04-02 21:57:16.015 Status: User: Admin initiated a switch command (60/deCONZ - Lum Couloir 1/On)

On Status mode, not in time order.

2019-04-02 21:57:16.019 (deCONZ) onCommand called for Unit 22: Parameter 'On', Level: 50, Hue:
2019-04-02 21:57:16.020 (deCONZ) Send Command /api/36E138295E/lights/3/state with {"on":true,"bri":127}

The first one is make by domoticz itself
The second one by the plugin.
If you miss the first one, the prb is from domoticz
If you miss the 2 other the problem is from the plugin

2019-04-02 21:57:16.123 (deCONZ) Classic Data : [{'success': {'/lights/3/state/on': True}}, {'success': {'/lights/3/state/bri': 127}}]
2019-04-02 21:57:16.123 (deCONZ) ###### WebSocket Data : {'state': {'on': True}, 'r': 'lights', 'uniqueid': '00:0d:6f:ff:fe:07cb-01', 'id': '3', 'e': 'changed', 't': 'event'}
2019-04-02 21:57:16.124 (deCONZ) ### Update device (deCONZ - Lum Couloir 1) : {'sValue': 'on', 'nValue': 1}

If you have the 4th but not the 5th, your plug don't answer to the gateway
If you have the 5 th and the plug is still at off > domoticz problem.

Posted: **Tuesday 02 April 2019 22:02**

Lol, not fast enought ^^.

But the buildin sensor have worked ? even with bad port ? You can't have websket notification with the bad port !

Code: Select all

2019-04-02 20:10:47.034 (deconz) ###### WebSocket Data : {'id': '1', 'state': {'dark': True, 'status': 200, 'lastupdated': '2019-04-02T18:10:47', 'daylight': False}, 't': 'event', 'e': 'changed', 'r': 'sensors', 'uniqueid': '00:21:2e:ff:ff:03:cd:5e-01'}
2019-04-02 20:10:47.035 (deconz) ### Update device (deconzx) : {'nValue': 0, 'sValue': 'Off'}, IGNORED , no changes !

So it mean the websocket is working.

Posted: **Wednesday 03 April 2019 14:42**

Hey i cant even explain myself what was going on there. For different reasons this little error makes me suspicious

Code: Select all

2019-04-02 21:27:37.217 Error: CConnection_disconnect, disconnection request from 'deconz' ignored. Transport does not exist.

So i have a look at the port in deconz and it says 443 and in the domoticz plugin 8088 was configured. After changing it in domoticz to 443 everything works fine.

Posted: **Wednesday 03 April 2019 18:00**

The important thing is now it works ^^.
I think in a future version, I will ad a fonction to check deCONZ config if debug is enabled, you are not the first one with a websocket port problem.

Posted: **Tuesday 09 April 2019 17:37**

New version online V 1.0.6.

The support for last devices (Door lock, curtain, thermostats, ... ) is not finished yet but I have too much bugs find by users.
I have had too a LUA exemple to change setting "on the fly" using the API, in this example you can change the sensitivy of the vibration sensor depending on the time : https://github.com/Smanar/Domoticz-deCO ... n-the-fly.

Posted: **Sunday 14 April 2019 10:15**

Just for information, the conbee is not available anymore, there is a new conbee called "conbee 2".
No changement, same application, future firmware will works for both, and both have same performances even the new one have better processor, same range, same maximum devices, ect ...

Posted: **Friday 26 April 2019 22:35**

Hi again.

Running the latest plug in and it works flawlessly.
Good job with this.

However, today I bought 2 aquara door sensors and in deConz is see that they have temperature sensors as well.

How do I add them to my temperature devices?

See this:

: brev.JPG (24.87 KiB) Viewed 3012 times

Posted: **Saturday 27 April 2019 15:19**

Hello, I haven't add them in the plugin because they are not reliables.

You have them on all Xioami device, but if you check the temperature you will see all possibles temperatures. Some of them they take the temperature of the door, or it never moves, or you can have hallucinating values.
On my side I have 28°C on the vibration sensor, 23°C on the motion and door sensor, while I have 21°C on the MultiSensor sensor, and they are at 3m each other.

Posted: **Saturday 27 April 2019 18:02**

Yeah... I see that... One of the sensors show 21 and the other shows 28 ... and they are like 30cm apart.

Posted: **Tuesday 30 April 2019 10:13**

Hi. Can you please add scene Button.
I have make scene with 3 bulbs and domoticz cant read this.

Thx

2019-04-29 21:03:26.015 Error: (deconz) Unknow device type On/Off light
2019-04-29 21:03:26.016 Error: (deconz) Can't Update Unit > 6 (lights)

Posted: **Tuesday 30 April 2019 18:54**

Sure, can you try the beta branch ? I have just updated it.
It add a "push to on" button for all scenes you have in deconz.

I use domoticz to set scene, so I haven't try this feature a lot, but your error message is strange, I can't see how scenes can provoke this error message.

Tell me if it's better pls.

Posted: **Tuesday 30 April 2019 19:06**

Hey, thank you! The buttons are here!

But I still have this strange message?

2019-04-30 19:01:52.526 Status: (deconz) ### Create Device SCENE_30 > 30 (Scenes) as Unit 49
2019-04-30 19:01:52.529 Status: (deconz) ### Create Device SCENE_TV > TV (Scenes) as Unit 50
2019-04-30 19:01:52.531 Status: (deconz) ### Create Device GROUP_Lampe_12-fach > Lampe 12-fach (LightGroup) as Unit 51
2019-04-30 19:01:52.533 Status: (deconz) ### Create Device GROUP_Treppe_OG > Treppe OG (LightGroup) as Unit 52
2019-04-30 19:01:52.533 Status: (deconz) ### deCONZ ready
2019-04-30 19:01:52.533 Status: (deconz) ### Found 38 Operators, 8 Sensors, 5 Groups and 2 others, with 0 Ignored
2019-04-30 19:01:52.084 Error: (deconz) Unknow device type On/Off light
2019-04-30 19:01:52.084 Error: (deconz) Can't Update Unit > 6 (lights)
2019-04-30 19:02:01.701 (deconz) onHeartbeat called
2019-04-30 19:02:11.719 (deconz) onHeartbeat called

Posted: **Tuesday 30 April 2019 20:11**

Lol, it seem I have forget the simple bulb, without color , without dimmer ( or a special device like a simple on/off module)
I have uploaded a new beta again. If this version don't work I will need more information about your device n°6 (with something like http://192.168.1.1:80/api/36E138295E/lights/6 )

I suppose it's a bulb with " On/Off light" as type, but it's strange, you should have this error during light scan.

Posted: **Tuesday 30 April 2019 20:39**

Thanks, everything is green now!

https://pastebin.com/sTfYAZWj

this is my switch 6

{"etag":"6347f5e237ad7970ab897c80d98b91f0","hascolor":false,"manufacturername":"SZ","modelid":"Lamp_01","name":"Hasenlicht","state":{"alert":"none","on":false,"reachable":true},"swversion":"20181107","type":"On/Off light","uniqueid":"01:12:4b:00:1b:ae:7b:25-0b"}

Posted: **Tuesday 30 April 2019 20:53**

One more question, I have found one among devices, but this is not known to me?
Do you know what that is?

"12":{"config":{"battery":100,"duration":90,"on":true,"reachable":true,"temperature":0},"ep":1,"etag":"a97e9a2f6451ea3b30b295f57ce49dca","manufacturername":"LUMI","modelid":"lumi.sensor_motion","name":"BWM Treppe-OG","state":{"lastupdated":"2019-04-30T18:50:03","presence":false},"type":"ZHAPresence","uniqueid":"00:15:8d:00:01:d9:1f:3a-01-0406"},"13":{"config":{"duration":60,"on":true,"reachable":true},"etag":"f4c35f6e2c88971e4f783aec07bc3571","manufacturername":"Phoscon","modelid":"PHOSCON_VPIR","name":"VPIR Bewegung Treppe","state":{"lastupdated":"2019-04-30T18:50:19","presence":false},"swversion":"1.0","type":"CLIPPresence","uniqueid":"vpir-1556631923079"},"14":{"config":{"on":true,"reachable":true},"etag":"64319e3edd2c933b1fd8e58674e8e775","manufacturername":"Phoscon","modelid":"PHOSCON_FSM_STATE","name":"FSM_STATE Bewegung Treppe","state":{"lastupdated":"2019-04-30T18:50:29","status":0},"swversion":"1.0","type":"CLIPGenericStatus","uniqueid":"fsm-state-1556631923079"},"7":{"config":{"on":true,"reachable":true},"etag":"117f3182bfbb089c82a3659355ca18d3","manufacturername":"Phoscon","modelid":"PHOSCON_FSM_FLAG","name":"CLIP-Sensor TOOGLE-ON-OFF","state":{"flag":false,"lastupdated":"2019-04-30T16:55:08"},"swversion":"1.0","type":"CLIPGenericFlag","uniqueid":"00:15:8d:00:01:f9:ef:de-01-0006-toogle-on-off"}}}

Domoticz

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

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)