Salut,
Pour ma part, j’utilise ce flow dans Node-red:
[{"id":"9d0a0834.cd0998","type":"group","z":"1988cfb9.49c74","name":"Réarmement Occupancy","style":{"stroke":"#ffC000","fill":"#ffffbf","label":true,"fill-opacity":"0.5"},"nodes":["3f4a6e85.e15e52","4abd3efb.dc3cb","a732b7ee.e4df98","de6eed80.ca8458","f1ba51b0.fe3938","ca109013.8553e8","afe1f9da.01e9b8"],"x":34,"y":659,"w":1132,"h":322},{"id":"3f4a6e85.e15e52","type":"function","z":"1988cfb9.49c74","g":"9d0a0834.cd0998","name":"Occupancy FALSE when Occupancy TRUE","func":"if( msg.payload.occupancy == true && msg.payload.occupancy_reset_by_flow != true ) {\n msg.payload.occupancy = false;\n msg.payload.occupancy_reset_by_flow = true;\n} else {\n msg = null;\n}\n\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":650,"y":760,"wires":[["a732b7ee.e4df98"]]},{"id":"4abd3efb.dc3cb","type":"debug","z":"1988cfb9.49c74","g":"9d0a0834.cd0998","name":"message de sortie","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","statusVal":"","statusType":"auto","x":1030,"y":940,"wires":[]},{"id":"a732b7ee.e4df98","type":"delay","z":"1988cfb9.49c74","g":"9d0a0834.cd0998","name":"","pauseType":"delay","timeout":"5","timeoutUnits":"seconds","rate":"1","nbRateUnits":"1","rateUnits":"second","randomFirst":"1","randomLast":"5","randomUnits":"seconds","drop":false,"x":820,"y":880,"wires":[["4abd3efb.dc3cb","f1ba51b0.fe3938"]]},{"id":"de6eed80.ca8458","type":"comment","z":"1988cfb9.49c74","g":"9d0a0834.cd0998","name":"Réarmement occupancy après 5s","info":"Voici mon flux Node Red pour « faux réarmer » les capteurs de mouvement modifiés au sein de HA. Je suis sûr qu'il existe de meilleures façons de le faire, mais cela fonctionne bien pour moi. Le flux peut gérer un nombre arbitraire de capteurs de mouvement, ci-dessous en a deux à titre d'exemple. Le flux peut gérer un délai de réarmement arbitraire, l'exemple utilise 10 s ; cependant, rien en dehors de la plage d'environ 6s et 90s n'a de sens. Vous devrez modifier pour pointer vers votre propre serveur MQTT. ","x":200,"y":940,"wires":[]},{"id":"f1ba51b0.fe3938","type":"mqtt out","z":"1988cfb9.49c74","g":"9d0a0834.cd0998","name":"","topic":"","qos":"0","retain":"","respTopic":"","contentType":"","userProps":"","correl":"","expiry":"","broker":"1eb4fa04.85f54e","x":990,"y":880,"wires":[]},{"id":"ca109013.8553e8","type":"debug","z":"1988cfb9.49c74","g":"9d0a0834.cd0998","name":"source aqara","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":550,"y":700,"wires":[]},{"id":"afe1f9da.01e9b8","type":"mqtt in","z":"1988cfb9.49c74","g":"9d0a0834.cd0998","name":"Eclairage sous sol: Détecteur de Mouvement","topic":"zigbee2mqtt/Détecteur de mouvement Aqara 1","qos":"0","datatype":"json","broker":"1eb4fa04.85f54e","nl":false,"rap":false,"x":230,"y":760,"wires":[["ca109013.8553e8","3f4a6e85.e15e52"]]},{"id":"1eb4fa04.85f54e","type":"mqtt-broker","name":"","broker":"localhost","port":"1883","clientid":"","usetls":false,"protocolVersion":"4","keepalive":"60","cleansession":true,"birthTopic":"","birthQos":"0","birthPayload":"","birthMsg":{},"closeTopic":"","closeQos":"0","closePayload":"","closeMsg":{},"willTopic":"","willQos":"0","willPayload":"","willMsg":{},"sessionExpiry":""}]
l’info est présente sur le site zigbee2mqtt:
https://www.zigbee2mqtt.io/devices/RTCGQ11LM.html#xiaomi-rtcgq11lm
et j’ai modifié le capteur en suivant les indications de ce site:
[Making Xiaomi Motion Sensor a Super Motion Sensor - Connected Things - SmartThings Community]
cela fonctionne très bien depuis plusieurs mois et le temps d’attente entres deux détections est de 5s, donc parfait.