Hello, yesterday I try to use my switch from xiaomi in domoticz and I noticed following error:

2019-11-12 16:23:02.274 Error: (Conbee) 'onHeartbeat' failed 'UnboundLocalError'.
2019-11-12 16:23:02.274 Error: (Conbee) ----> Line 841 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py'
2019-11-12 ...

I have also conbee near wifi router, mayby there are some inrerferences, is that possibile ?

Via domoticz app/web bulb is turning immediately and script is writing in dzvents , I have also cube and with this is the same problem, tomorrow i wilk check how IT looks in phoscon app

What kind of lib?

Hello, is that normal that I have about 1,5 sec delay between pushing Xiaomi switch and turning on light ? I have conbee 2, working with domoticz. The same delay is when Im near conbee and when im in other room. What should I check to offsetting this delay? Thanks for help

Hmmm , I have also 'shake' for one script, the first one below and its working . My permission looks like here:

drwxrwxrwx 2 pi pi 4096 Oct 7 23:24 .
drwxr-xr-x 13 pi pi 4096 Oct 7 18:21 ..
-rwxrwxrwx 1 pi pi 74 Oct 7 18:21 radiozet.sh
-rwxrwxrwx 1 root root 21 Oct 7 18:30 stop.sh
-rwxrwxrwx 1 root ...

Hello could you tell me what Im doing wrong? When I rotate cube in right there should be executed specific scripts, the same for left. Scripts is recognising left and right (printing proper value, but scripts are not executed). Could you help ?



return {
on ={devices ={'Cube_kat'}},

execute ...

Its works, thanks guys for help !

I put * instead device name and it seems like script is looking for nValue for all devices in utility tab, but I dont see any Cube device in Utility.. I have only cube im switch tab

I put this script and it doesnt return anything in domoticz log

So if my device in domoticz is cube_device
This should be :

return {
on = { devices = { 'cube_device' } },

execute = function(domoticz, cube_device )
domoticz.log(cube_device.name .. " state: " .. cube_device.state,domoticz.LOG_FORCE)
domoticz.log(cube_device.name .. " nValue: ".. cube_device ...

Hello I have some logs from Xiaomi Cube like this:

2019-10-04 19:20:12.562 (Conbee) onMessage called
2019-10-04 19:20:12.562 (Conbee) ### WebSocket Data : {'state': {'buttonevent': 7000, 'gesture': 0, 'lastupdated': '2019-10-04T17:20:12'}, 'r': 'sensors', 'uniqueid': '00:15:8d:00:02:9b:f6:2a-02 ...

Thorgal problem rosolved. You have right I add it again iwth shaking etc and its added, thank for help !

I tego to rotate clock wise (like potentiometr) but i'm log theres no info, only when rotate 90, 180, shake etc, as above, where is mesuremets im domoticz? I cannot see it, plugin add to domoticz only one switch

Guys thank for help , my Cube are visible now , dont ask why , I dont know :D, I have another question.

Is there any option to add clock wise rotate to domoticz, I have only those options:

Level Level name Order
0 Off
10 Shak
20 Wake
30 Drop
40 90°
50 180°
60 Push
70 Tap

Here's result:

{"1":{"config":{"configured":true,"on":true,"sunriseoffset":30,"sunsetoffset":-30},"etag":"f5fd20be21c15aa5b25df5fe1e69ea04","manufacturername":"Philips","modelid":"PHDL00","name":"Daylight","state":{"dark":false,"daylight":true,"lastupdated":"2019-10-01T15:49:14","status":180 ...

Logs from conbee said that theres 2 sensors but still I dont have it in any tab in domo, sensors of course are visible in phoscon app:

2019-10-01 10:48:50.689 Status: (Conbee) Firmware version : 0x264a0700
2019-10-01 10:48:50.689 Status: (Conbee) Websocketnotifyall : True
2019-10-01 10:48:50.733 ...

Hello I have problem with xiaomi Cube im domoticz. After adding this to phoscon app (conbee II) I cannot see new devices in domoticz. I have also added xiaomi switch and this is working fine. Any idea how to deal with this problem ? I dont havent any logs regarding Cube in domoticz. Did any one had ...

Hello, today I bought conbee II and add xiaomi switch to it. After configuring deconz and adding hardware to domoticz , devices are no creating.
I have an error :

2019-09-26 20:51:35.685 Error: (Conbee) Wrong startup, retrying !!

Do you have aby idea where os the problem ?

Full logs:

2019-09 ...