Motion sensor setup working with automation

Configuration
1

I have Dome motion sensor, which works great as a motion sensor and the automation I setup to turn on a zwave switch is working, but I have been trying to get lumination sensor working so if the lux is over a certain amount, it will not switch the light on. My configuration for the automation is:

- action:
  - data:
      entity_id: light.level
    service: light.turn_on
  alias: When movement in MB WC turn light on
  condition:
  - below: '2000'
    condition: numeric_state
    entity_id: sensor.dome_motion_detector_luminance
  id: '1521395553520'
  trigger:
  - entity_id: binary_sensor.sensor
    from: 'off'
    platform: state
    to: 'on'

Dorking around with the sensor settings, the lumination is not being detected at all, or at least it is not reported, even if the motion sensor is activated:

image

Motion sensor:

image

I got some help on the hass.io forum and thought it would be a matter of changing some of the settings in the zwave settings. I have:

7: Light Sensing Interval - This is set to 180
9: Ambient Light Sensitivity Level - This is set to 100

There has to be something I am missing to set this up, just not sure what it is. Since the motion part is working, that should be configured properly, right?

2

I forgot to add that before I set Light Sensing Interval and Ambient Light Sensitivity Level, I would at least get a graph under the lumination sensor that got updated every 12 hours. But now, I don’t even get that.

3

Any thoughts on how to debug this? I did verify that my changes are being sent to the Node when I wake up the sensor. Thinking it has to be something fundamental, just not sure where to look or what to try.

4

I had this problem with a cheap Monoprice sensor, unenrolling and reenrolling it did the trick.

5

Will give this a try. So, you mean to exclude the sensor, then include again, right?

6

I see this is an older post but not sure if you resolved it. I have 2 Dome Motion Sensors and have figured out a few things with them. I’m using Hassio on a Pi with a HUSBZB-1 stick.

First I found is you cannot change any setting until they are awake. I have set Light Sensing Interval to 90 Seconds and Ambient Light Sensitivity Level to 2 (because I have them in a low light area). So every 90 seconds it checks the light level and if it has changed 2 or more lux it reports it. If you are in a brighter light or an area it changes often you may want to increase the value so it isn’t constantly trying to update. I let mine settle a couple days in the position I wanted them after first adding them to get a handle on where I wanted to set the light level, too often will use more battery.

To make the parameter changes… I opened the sensor for access to the button to wake it. I then got everything ready in the hassio Z-Wave panel ready to change the setting, I then pressed the button quickly 1 time on the sensor to wake it and right after hit the update button in Hassio, the parameter changed immediately. I did this each time I set a parameter and everything update immediately.

Another thing I found was rebooting Hassio when these sensors are in “Initializing (cache)” state can cause you to lose the entities in Hassio, the Motion Sensor and the Binary Motion Sensor remain but everything else goes away. You can recover without removing and re-adding, I have done this by re-booting Hassio again and while it is coming back up pressing the motion detector button quickly once to wake it so it updates properly. You may need to do this a couple times to get all the device entities back.

The motion detector should report all changes no matter what state it is in, don’t be alarmed if they stay in an initializing state for a day. I have found them to be fast and I use 2 of them for both Light and Motion detection and will probably add more. Once you learn the little tricks with them and set them up they just work.

EDIT: You do not need to set a polling interval in Hassio… if you set the parameters correctly they do update quickly has been my experience.

4 Likes
7

Hi,

I came across this post, I have just added a Dome motion sensor and I was wondering if there was a way of speeding up the time from when motion is detected to when the action is triggered. I want to use the sensor to turn my basement lights on as I go down the basement stairs

8

I can’t find anything on the setting. You can tell if it’s the report time or maybe another issue by looking at the states on the developer tab and triggering it and see how fast the state changes.

9

Thanks for the reply,

Actually once it had settled down on the Zigbee network it triggers the lights pretty quickly

Really pleased with it, works well

10

Hey guy’s,
What setting do you guys have for parm 2 & 6?, mine is on the default setting 30 & 8, and I find my light automation’s are not re-triggering effectively with the turn_off service set to 5sec after sensor goes to off state even though motion is still present.

@MarVin Thanks for the info the Ambient Light setting.

11

You shouldn’t have to change them but your brief description of what you are trying to do has me confused. What are you trying to accomplish?

12

When the lights turn off while I’m still in the room without movement, and I move to activate motion, the lights don’t turn back on, same as if I leave the room and return as soon as the light turn off.

13

Are you trying to do it in one automation or with 2?

I use 2 it’s easier…

One for ON

,

  • id: ‘1549212412448’
    alias: Bsmnt Stair Motion On
    trigger:
    • entity_id: binary_sensor.bsmnt_stairs_motion
      from: ‘off’
      platform: state
      to: ‘on’
      condition: []
      action:
    • data:
      entity_id: light.bsmnt_stairs_light
      service: light.turn_on
      ,

One for OFF with a timer

,

  • id: ‘1549212495808’
    alias: Bsmnt Stair Motion Off
    trigger:
    • entity_id: binary_sensor.bsmnt_stairs_motion
      for: 00:05:00
      from: ‘on’
      platform: state
      to: ‘off’
      condition: []
      action:
    • data:
      entity_id: light.bsmnt_stairs_light
      service: light.turn_off
      ,

On should need no explanation… Off looks for the motion detector to go from ON to OFF waits 5 minutes then turns the lights off… if the motion detector get’s triggered again, On to Off, it resets the timer… and turns the lights on if they are off.

14

I know this is an old post but I am new and was wondering how to set stuff up. I have an Aeotec Gen5 z-wave. and an Aeotec motion z wave sensor I do not know how to setup or use I have the Home Assistant setup but do not know how to use Automations. Can someone help me setup because i need to setup a z-wave motion sensor for my christmas tree