Setting up my first motion sensor and everything looks ok but although it turns on it never turns back off when I stop moving in front of the sensor. It does work however if I trigger the automation from the dashboard.
My understanding was that if I can make it work by manually triggering the automation then it should be setup properly, is this not the case?
I’ve removed and re-added the sensor and it’s still showing the same. Both the OS and the HA versions are up to date and I’ve rebooted the entire system quite a few times.
Would anyone be able to point me in the right direction please?
You want to look at the motion state of the device. I don’t remember setting mine up, but i know it wasn’t straight forward. The reporting type might have needed to change.
This is my automation:
- alias: Hall Motion Detected During Night
trigger:
- platform: state
entity_id: binary_sensor.hallway_ms_sensor_32_0
to: 'on'
condition:
- condition: time
after: '23:00:00'
before: '07:00:00'
action:
- service: homeassistant.turn_on
entity_id: script.hall_motion_night
same device as yours. So if you have it setup properly, you should be looking at the state of the device, not the burgler attribute.
Interesting. I had read a few places which including some here on HA, this one included which mention that 0 is off, 8 is motion and 3 is tampering. If I look in the history for the sensor I can see 8’s for when there’s movement and 0’s for when there isn’t any.
I’ve got it working now somehow. These are the setting which work:
- alias: Motion Detection - Dining Light on
trigger:
platform: state
entity_id: sensor.aeotec_zw100_multisensor_6_burglar
to: '8'
action:
service: light.turn_on
entity_id: light.level_3
- alias: Motion Detection - Dining Light off
trigger:
platform: state
entity_id: sensor.aeotec_zw100_multisensor_6_burglar
to: '0'
for: '00:01:00'
action:
service: light.turn_off
entity_id: light.level_3
I think setting to to: 0 might have done the trick.
For anyone else reading, the bit that’s still confusing is that eventhough I put 1 minute of inactivity to turn the light off it actually takes about 4 minutes for some reason. Very odd.
I tried both binary_sensor.aeotec_zw100_multisensor_6_sensor_13 and binary_sensor.aeotec_zw100_multisensor_6_sensor and neither seemed to work after restating the Server Management inbetween changes.
Some poeple have used ‘0’ and others ‘on’ so I’ll have to dig around more tomorrow and see if binary should be getting 0/1 or on/off.
@Coolie1101, if you have one of these sensors would you mind telling me what you set for to: please?