Blockly - Xiaomi motion sensors behave opposite to config

Topics (not sure which fora)
when not sure where to post, post here and mods will move it to right forum.
Post Reply
Posts: 2
Joined: Sunday 18 February 2018 21:03
Target OS: Raspberry Pi
Domoticz version:

Blockly - Xiaomi motion sensors behave opposite to config

Post by raeymeister » Sunday 18 February 2018 21:21

Hi, I run raspberry pi 3 with domoticz 3.8923 (beta). Behaviour is same on stable release (2017/09/20).

Domoticz is linked to the Xiaomi gateway. Xiaomi Human body motion sensors are recognised as well.
Alerts are seen in domoticz log when motion detected:

2018-02-18 20:10:23.957 {"cmd":"report","model":"motion","sid":"158d0881bb5169","short_id":38887,"data":"{\"status\":\"motion\"}"}

for an event in blockly to work, I have to indicate if "xiaomisensor" doesnotequal "Motion"
Then the event works (see attached screenshot). I don't understand why i can't use the = , this is completely opposite behaviour as what I expected.

It is not blocking for me, but maybe you have a similar experience.

Thanks for your advice.
xiaomi_motion_event_blockly.png (11.39 KiB) Viewed 113 times

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 5 guests