Not a new install, fully updated, just thought I would play with some z-wave devices. Added z-wave plugs with success, but the PIR is being problematic detecting movement lol.
did you add it using “secure inclusion”? if not you may be missing the binary sensor for motion
Do you have frontend for zwavejs? if so you may check the node there and you should be able to see what sensor are available under “Values”. In my case, i have a multisensor and it does not have binary sensor it provide but provides motion as a Notification. Only temp and luminance are seperate sensor
Try to re-pair with secure inclusion if you did not do this already.
Or you may try reinterview. If sensor has bad connection or battery operated device that sleep during connection sometimes the sensor are missed.
Hi,
As geidorei said ,
This is not a zwave+ device so does not support secure connection.
The binary sensor “Any” is the motion sensor ( on → off → on … )
If your looking for state change in HA it may be useful to watch zwavejs log also as verification change or no change occurring. If set logging to file ON you may also check historical logs to verify this
Log for the device as below, I see a change state for ‘any’ but how can I make use of that, for example say to turn a light on? I am so used to using ZigBee devices, so the question to be asked: ‘is z-wave always this complicated?’ lol.
2021-09-03 15:53:13.640 INFO ZWAVE: Node 11 is asleep
2021-09-03 15:53:13.653 INFO ZWAVE: Node 11: value added 11-32-0-currentValue => 99
2021-09-03 15:53:13.654 INFO ZWAVE: Node 11: value added 11-32-0-targetValue => undefined 2021-09-03 15:53:13.657 INFO ZWAVE: Node 11: value added 11-48-0-Any => true
2021-09-03 15:53:13.658 INFO ZWAVE: Node 11: value added 11-49-0-Air temperature => 24.1
2021-09-03 15:53:13.659 INFO ZWAVE: Node 11: value added 11-49-0-Illuminance => 1000
2021-09-03 15:53:13.660 INFO ZWAVE: Node 11: value added 11-49-0-Humidity => 58
2021-09-03 15:53:13.661 INFO ZWAVE: Node 11: value added 11-112-0-2 => 1
2021-09-03 15:53:13.663 INFO ZWAVE: Node 11: value added 11-112-0-3 => 720
2021-09-03 15:53:13.664 INFO ZWAVE: Node 11: value added 11-112-0-4 => 1
2021-09-03 15:53:13.665 INFO ZWAVE: Node 11: value added 11-112-0-5 => 2
2021-09-03 15:53:13.666 INFO ZWAVE: Node 11: value added 11-112-0-111 => 720
2021-09-03 15:53:13.667 INFO ZWAVE: Node 11: value added 11-112-0-112 => 720
2021-09-03 15:53:13.668 INFO ZWAVE: Node 11: value added 11-112-0-113 => 720
2021-09-03 15:53:13.668 INFO ZWAVE: Node 11: value added 11-112-0-101-1 => 0
2021-09-03 15:53:13.671 INFO ZWAVE: Node 11: value added 11-112-0-101-32 => 0
2021-09-03 15:53:13.671 INFO ZWAVE: Node 11: value added 11-112-0-101-64 => 0
2021-09-03 15:53:13.672 INFO ZWAVE: Node 11: value added 11-112-0-101-128 => 0
2021-09-03 15:53:13.673 INFO ZWAVE: Node 11: value added 11-112-0-102-1 => 0
2021-09-03 15:53:13.674 INFO ZWAVE: Node 11: value added 11-112-0-102-32 => 0
2021-09-03 15:53:13.675 INFO ZWAVE: Node 11: value added 11-112-0-102-64 => 0
2021-09-03 15:53:13.677 INFO ZWAVE: Node 11: value added 11-112-0-102-128 => 0
2021-09-03 15:53:13.677 INFO ZWAVE: Node 11: value added 11-112-0-103-1 => 0
2021-09-03 15:53:13.678 INFO ZWAVE: Node 11: value added 11-112-0-103-32 => 0
2021-09-03 15:53:13.679 INFO ZWAVE: Node 11: value added 11-112-0-103-64 => 0
2021-09-03 15:53:13.681 INFO ZWAVE: Node 11: value added 11-112-0-103-128 => 0
2021-09-03 15:53:13.681 INFO ZWAVE: Node 11: value added 11-112-0-255 => undefined
2021-09-03 15:53:13.682 INFO ZWAVE: Node 11: value added 11-114-0-manufacturerId => 134
2021-09-03 15:53:13.684 INFO ZWAVE: Node 11: value added 11-114-0-productType => 2
2021-09-03 15:53:13.684 INFO ZWAVE: Node 11: value added 11-114-0-productId => 5
2021-09-03 15:53:13.686 INFO ZWAVE: Node 11: value added 11-128-0-level => 99
2021-09-03 15:53:13.687 INFO ZWAVE: Node 11: value added 11-128-0-isLow => false
2021-09-03 15:53:13.688 INFO ZWAVE: Node 11: value added 11-132-0-wakeUpInterval => 240
2021-09-03 15:53:13.689 INFO ZWAVE: Node 11: value added 11-132-0-controllerNodeId => 1
2021-09-03 15:53:13.690 INFO ZWAVE: Node 11: value added 11-134-0-libraryType => 6
2021-09-03 15:53:13.691 INFO ZWAVE: Node 11: value added 11-134-0-protocolVersion => 3.28
2021-09-03 15:53:13.692 INFO ZWAVE: Node 11: value added 11-134-0-firmwareVersions => 1.18
2021-09-03 15:53:13.696 INFO ZWAVE: Node 11 ready: AEON Labs - DSB05 (4 in 1 MultiSensor)
I don’t see any 11-48-0 in log so look like no Binary Sensor change during that logging time
Just for your understanding
You can see each sensor has some number…like all multisensor is 11-49-0 the specified as humidty, illuminance, etc
You can look in log and find everything that occur
For this node 11
Yes, Zwave is hard but honestly there is nothing better than clearly labeled log to go through when things are not as expected. That said, no clue why binary sensor not change or reporting state. Zwave js has made it much better than when I was using openzwave
Look like log you provide is less than 2minute correct? Maybe looking at longer logging period, like 1 hr while a lot of movement around sensor then 1hr with very little movement, may provide clearer picture of how and if it functioning
Honestly I never like multisensor for motion. I think they have long period between state changes for motion, like minutes not seconds. I use Zwave motions and even then put them in “test” mode to allow the 5second between trigger vs 5minute
FYI: After recent update to Z-Wave integration everything is now working. I did lose all the other sensors as the device kept falling into a deep sleep and would not wake, but all seems to be ok now and I can also see a change in the PIR motion.
How exactly did you fix this? I was using the sensor via a Veralite, but a recent lightning strike appears to have toasted my Vera, so I excluded / included the sensor via a Z-stick instead (via Z-Wave JS to MQTT, the most recent version). I’ve got the ‘any’ motion sensor now but it’s always on. Temperature, humidity and lux are separate sensors and all seem to be working.