I had a similar issue with this one but it eventually worked. No tricks, just repeated pair/unpair. If it continues I would say it is defective.
I did remove my z-stick to pair though… was unable to get it to pair through the Hassio interface.
Battery powered devices are asleep 99% of the time and a probe by HA won’t see a known device. There is usually a way to temporarily “wake” the device so check your manual. While the device is awake, try checking or changing some setting. The wake time is usually very short, perhaps 15 to 30 seconds so you will likely need to trigger the wake several times. Check the manual. Try using tail -f on the OZW_og.txt file in your configuration folder and then trigger one or more of the sensors on the device and see whether the device sends out the information. Check the manual.
Yes, I am having challenges with this also. It pairs fine with my Sigma UZB and I see the badges, but the motion sensor doesn’t appear to work. I understand if it is alseep to conserve battery, but shouldn’t the motion sensor wake it up?
Not all motion sensors present the trigger in the same way. You may need to determine what the trigger is and then use that information in your configuration. SSH into your HA device and run the following in your configuration directory.
tail -f OZW_Log.txt | grep Node0x
replace the Node0x with the Node number for your Zwave motion sensor. Then operate the motion sensor. You will need to place it face down into something and let the delay time (usually 4 or 5 minutes). It make take a few tries but you should start seeing some values change.
@2devnull here is the output from one of my motion sensors.
2018-02-24 17:09:24.396 Detail, Node031, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x1f, 0x03, 0x20, 0x01, 0x00, 0xcf
2018-02-24 17:09:24.397 Info, Node031, Received Basic set from node 31: level=0. Sending event notification.
2018-02-24 17:09:24.397 Detail, Node031, Notification: NodeEvent
2018-02-24 17:09:24.421 Detail, Node031, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1f, 0x0a, 0x71, 0x05, 0x07, 0x00, 0x00, 0xff, 0x07, 0x02, 0x00, 0x00, 0x77
2018-02-24 17:09:24.421 Info, Node031, Received Alarm report: type=7, level=0, sensorSrcID=0, type:Burglar event:2, status=255
2018-02-24 17:09:24.421 Detail, Node031, Refreshed Value: old value=7, new value=7, type=byte
2018-02-24 17:09:24.421 Detail, Node031, Changes to this value are not verified
2018-02-24 17:09:24.421 Detail, Node031, Refreshed Value: old value=255, new value=0, type=byte
2018-02-24 17:09:24.422 Detail, Node031, Changes to this value are not verified
2018-02-24 17:09:24.422 Detail, Node031, Refreshed Value: old value=0, new value=0, type=byte
2018-02-24 17:09:24.422 Detail, Node031, Changes to this value are not verified
2018-02-24 17:09:24.422 Detail, Node031, Refreshed Value: old value=2, new value=2, type=byte
2018-02-24 17:09:24.422 Detail, Node031, Changes to this value are not verified
2018-02-24 17:09:24.422 Detail, Node031, Notification: ValueChanged
2018-02-24 17:09:24.425 Detail, Node031, Notification: ValueChanged
2018-02-24 17:09:24.427 Detail, Node031, Notification: ValueChanged
2018-02-24 17:09:24.428 Detail, Node031, Notification: ValueChanged
So in my case, I see that the alarm level goes from 0 to 255 when motion is triggered. From the Developer tools < > section of the HA web interface I looked up the alarm level entry for the lr_motion and found sensor.lr_motion_alarm_level
I can use this in an automation with
alias: Turn on LR lamp when there is movement
trigger:
platform: state
entity_id: sensor.lr_motion_alarm_level
to: '255'
action:
- service: light.turn_on
entity_id: light.lr_lamp@zarthan - thanks…checking it now.
UPDATE: I did what you stated and put it in a close draw for 5 min, but when I took it out, I didn’t see anything in the log.
Most of these are the entities it has:
What is the Node ID for your device?
You can get some information from the Logbook (HA left side menu). See what that shows.
try running the tail command again. make sure you have the node id correct. make sure node case is as shown. Node
The log shows Node002
Try restarting home start. You can do that from the web interface. Then try just
tail -f OZW_Log.txt
I believe this is what I need to look for then (i.e. use level=255) ?
Node002, Received Alarm report: type=7, level=255, sensorSrcID=0, type:Burglar event:8, status=255
That looks correct. Give it a try.
How do you pair these? The manual says something about 5 flashes I don’t see and then pressing the programming button. The only button I see is the tamper switch. I’m using a ZOOZ Z-Wave stick and haven’t had issues with other devices, even a monprice Tilt switch.
The manual is terrible. I tried forever to use the “button”. It was the first time I ever struggled to add a node. The inside “button” appears to only be the tamper detection switch. Remove the batteries, then click Add Node in HA, then re-insert and it will pair. Insertion of the batteries is what produces the 5 flashes.
Well, I just figured out the “button” is a tiny hole on the bottom of the sensor. There are 4 slots, and next to that a tiny hole. Use a paper clip to activate it. So if the battery method doesn’t work, try that!
1 Like
Wow, who would find that? The battery method is giving me:
2020-03-04 20:22:49.202 Info, Add Device
2020-03-04 20:22:49.202 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x88, 0xf9
2020-03-04 20:22:49.202 Detail, Notification: ControllerCommand - Starting
2020-03-04 20:22:49.205 Detail,
2020-03-04 20:22:49.205 Info, contrlr, Sending (Command) message (Callback ID=0x88, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x88, 0xf9
2020-03-04 20:22:49.208 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x88, 0x01, 0x00, 0x00, 0x3b
2020-03-04 20:22:49.208 Detail,
2020-03-04 20:22:49.360 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-03-04 20:22:49.360 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2020-03-04 20:22:49.360 Detail, Node001, Expected callbackId was received
2020-03-04 20:22:49.360 Detail, Node001, Expected reply was received
2020-03-04 20:22:49.360 Detail, Node001, Message transaction complete
2020-03-04 20:22:49.360 Detail,
2020-03-04 20:22:49.360 Detail, contrlr, Removing current message
2020-03-04 20:22:49.361 Detail, Notification: ControllerCommand - Waiting
2020-03-04 20:22:49.361 Info, WriteNextMsg Controller nothing to do
I’ll try the button. 106.5 messed my Z-Wave up. I had two node 10s somehow. I went back to 106.2 and alls fine again.
The button got it pairing, but it won’t go past the probe stage. Any suggestions?
Press the button multiple times, if it went to sleep too soon it needs to continue sending its node info.
Thanks, I’ll give a go.
That got it paired. I see sensor entities. |[sensor.vision_security_zp3111_multisensor_4in1_battery_level]
|[sensor.vision_security_zp3111_multisensor_4in1_burglar]
|[sensor.vision_security_zp3111_multisensor_4in1_clock]
|[sensor.vision_security_zp3111_multisensor_4in1_emergency][sensor.vision_security_zp3111_multisensor_4in1_homehealth]
|[sensor.vision_security_zp3111_multisensor_4in1_luminance]
|[sensor.vision_security_zp3111_multisensor_4in1_power_management]
|[sensor.vision_security_zp3111_multisensor_4in1_relative_humidity]
|[sensor.vision_security_zp3111_multisensor_4in1_sourcenodeid]
|[sensor.vision_security_zp3111_multisensor_4in1_temperature]
no binary_sensor for PIR detection or sensor that could be used to make it. Am I missing something?
I found your post in another thread and will pursue that.
Changing Motion Sensor from "Basic Set (default)" to "Binary Sensor report" or "Alarm report".
Lots of patience needed with these. I didn’twait three minutes to see the burglar go to zero.