Blockly - Xiaomi motion sensors behave opposite to config
Posted: Sunday 18 February 2018 20: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.
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.