Motion Sensor Issues

Configuration
1

Hey guys and gals!

I just got HASS up and running yesterday, and I am running into an issue with my first automation.

A quick run down of my very simple setup:

Hass running on Debian 8 VM in a virtualenv
Couple of Philips Hue bulbs with the 2nd Gen Hue Bridge
EcoLink Z-Wave PIR motion sensor with 5th Gen Aotec Z Stick

On to the issue. I can see everything in the web interface. I can control my lights, and I see my sensor in the ‘off’ state. The problem is that the sensor never leaves the ‘off’ state. If I wave my hand in front of it the LED blinks so I know it detected motion, but it never switches state from ‘off’ to ‘on’. When viewing the same device in OpenZWave Control Panel, I can clearly see the state changing from ‘off’ to ‘on’, so this is some kind of miscommunication between the Z Wave network and HASS.

I have tried re pairing it with the Z Stick a couple of times, and even went so far as to completely rebuild HASS on a fresh Linux install thinking maybe I did something wrong.

Any ideas? Thanks in advance!

2

Okay, so I got the motion sensor to read on and off in HASS, but my automation is not working.

automation:
  alias: Turn on basement light
  trigger:
    platform: state
    entity_id: binary_sensor._sensor_2_0
    state: 'on'
  action:
    service: turn.light_on
    entity_id: light.basement
3

I guess you should try to find out which part is not working. The trigger or the action. If you go the the “dev” section in your ui you could manually trigger the action part by calling service “turn.light_on”, entity_id light.basement.

4

Sanders,

Thank you!! Playing around with the dev tools led me to the answer.

action:
  service: turn.light_on
  data:
    entity_id: light.basement
5

turn.light_on is not a service. If you go to the services tab in the GUI you can see all the services that are available. What you want is either

homeassistant.turn_on
or
light.turn_on

6

Sorry, that was a mixup on my end. In my config it is light.turn_on.

7

So I am having the exact same issue with these exact sensors… How did you get it to recognize them?