Hassio Automation won't auto-trigger

Thanks Tom,

I can’t get the binary sensor to change from basic set. OpenZ-Wave log reports
‘Invalid Index Set on ValueList
… Warning, ValueList returned a NULL value for GetValueListSelection: Current power mode’.
I tried it on an off binary sensor & one on.

Aeotec Multisensor 6 has 9 ‘entities’:

Binary on/off. Basic set or binary sensor report
Alarm level. 0 (zero)
Alarm type 0
Burglar. 0,3,8
Luminance. 000000.0
Humidity. 00.0
Source node Id 0
Temperature. 00.0
Ultraviolet. 0.0

From other posts, Alarm Type, Alarm Level and Source node id do nothing - they are always zero value.

Merry Christmas!

So you saw the state of the binary sensor change from off to on & back when you trigger/untrigger the device?

A Xmas miracle! The binary sensor report stuck overnight. It works now.

There is a disconnect sometimes however as the burglar sensor correctly reports movement but the binary sensor doesn’t go to ‘on’ from ‘off’.

Thanks Tom & Finity.

Detailed Change to Binary Sensor Report on Raspberry Pi 3+ on Hassio .84.5:

Valid automation script before beginning.
Restart
Wait 10 minutes.

  1. From Overview/Frontend
  2. Click Configuration
  3. ClickZ-Wave
  4. Click Z-Wave Node Management
  5. Click Nodes dropdown
  6. Click required (Z-Wave) sensor
  7. Click ‘Entities of this node’ (sensor) eg ‘binary_sensor.aeotec_zwave_multisensor_6_sensor’
  8. Under Node Config Options
  9. Click Config parameter dropdown
  10. Select ‘5. Command Options’
  11. Select ‘Binary Sensor Report’
  12. Click 'Set Config Parameter’s
  13. Check OZW Log, Load.

You may have to try several times. Wait more than 10 minutes between attempts.

Thank you, WayneNelson!
Spent quite a long time looking for this.