Inovelli LZW60 - Hass.io - unable to configure PIR Timeout

Sensors General Discussion
, , ,
#1

Good morning!

I’ve been trying to play around with the LZW60 4-1 sensor as I was hoping to replace all of my motion sensors with these devices in the near future. However, while for the most part the device works quite well, I cannot configure the PIR Timeout at all… I can configure everything else with ease, but reviewing the log files the only configuration parameter my server sends it during the wake up period is the default 30, and I’m never sending this value. I went as far as trying to force the config I wanted by manually editing the config file and re-adding the sensor, this also did not work.

30 seconds is pretty useless for my current set up and I’d love to set it to 5 seconds, but I’m unable to.

Here’s a log entry where it was successful in editing the PIR Sensitivity (Parameter 12) from 9 to 6:

2020-05-01 09:03:00.006 Info, Node022, Response RTT 103 Average Response RTT 74
2020-05-01 09:03:00.006 Detail, Node022, Refreshed Value: old value=9, new value=6, type=byte
2020-05-01 09:03:00.006 Detail, Node022, Changes to this value are not verified
2020-05-01 09:03:00.006 Info, Node022, Received Configuration report: Parameter=12, Value=6
2020-05-01 09:03:00.006 Detail, Node022, Expected reply and command class was received
2020-05-01 09:03:00.006 Detail, Node022, Message transaction complete

I then queued up my config change to release once the device woke up 60 seconds later (set time really low while troubleshooting):

2020-05-01 09:03:00.036 Detail,
2020-05-01 09:03:00.036 Detail, Node022, Removing current message
2020-05-01 09:03:00.036 Detail, Node022, Notification: Notification - Node Asleep
2020-05-01 09:03:41.058 Info, Node022, Value::Set - COMMAND_CLASS_CONFIGURATION - PIR Trigger Time (seconds) - 13 - 1 - 5
2020-05-01 09:03:41.058 Info, Node022, Configuration::Set - Parameter=13, Value=5 Size=1
2020-05-01 09:03:41.059 Detail,
2020-05-01 09:03:41.059 Detail, Node022, Queuing (WakeUp) ConfigurationCmd_Set (Node=22): 0x01, 0x0c, 0x00, 0x13, 0x16, 0x05, 0x70, 0x04, 0x0d, 0x01, 0x05, 0x25, 0x9a, 0x31
2020-05-01 09:03:41.059 Detail,
2020-05-01 09:03:41.059 Detail, Node022, Queuing (WakeUp) ConfigurationCmd_Get (Node=22): 0x01, 0x0a, 0x00, 0x13, 0x16, 0x03, 0x70, 0x05, 0x0d, 0x25, 0x9b, 0x35
2020-05-01 09:03:59.877 Detail, Node022, Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x16, 0x02, 0x84, 0x07, 0x64
2020-05-01 09:03:59.877 Detail,
2020-05-01 09:03:59.877 Info, Node022, Received Wakeup Notification from node 22

And here’s where it’s supposed to be configuring Parameter 13 to 5 seconds from 30:

2020-05-01 09:03:59.940 Info, Node022, Response RTT 37 Average Response RTT 55
2020-05-01 09:03:59.940 Detail, Node022, Refreshed Value: old value=30, new value=30, type=byte
2020-05-01 09:03:59.940 Detail, Node022, Changes to this value are not verified
2020-05-01 09:03:59.940 Info, Node022, Received Configuration report: Parameter=13, Value=30
2020-05-01 09:03:59.940 Detail, Node022, Expected reply and command class was received
2020-05-01 09:03:59.940 Detail, Node022, Message transaction complete
2020-05-01 09:03:59.940 Detail,
2020-05-01 09:03:59.940 Detail, Node022, Removing current message
2020-05-01 09:03:59.940 Detail, Node022, Notification: ValueChanged

Installation and configuration done exactly as instructed here including modification of manufacturer_specific.xml and inclusion of lzw60 config .xml file. Removed the sensor and readded it a solid 10 times minimum post installation as well.

Does anyone have any ideas?

#2

Can you set it to 6 seconds? 5 seconds is supposed to be the minimum, but if 6 works and 5 does not, perhaps there is a firmware bug.

1 Like
#3

Thanks for the idea! However, same issue… I’ve tried with 6, 29 and even a higher value of 40, but the device only ever pushes the default 30… I was wondering the same thing, but at this point I can’t really imagine its not a firmware issue. Bummer :frowning:

#4

And just to be sure, you are pressing the button on the sensor 3x (not 1x) after making the change?

#5

Neither actually, I was letting it wake up on it’s own after 60 seconds. But when I was testing by hitting the button I did hit it 3 times to wake it up. I found it easier to adjust the wake up interval to 60 seconds for testing purposes so I was relying on that.

#6

If it makes you feel any better, I tried changing this value on my sensor, and I can recreate the issue. I tried setting it to 5 seconds, 20 seconds, and 60 seconds, but it reverts back to 30 seconds when I wake the device up. I am not sure if it is an issue with OpenZwave, or something else.

Ill try playing around with things a bit further later this evening, and see if I can come up with anything.

1 Like
#7

Thanks for testing on your end, it actually does help a lot to know it’s not just me haha. It’d also save everyone the hassle of returning this device for a replacement thinking it might be just this one that’s defective. I’ll see if there’s anything else I can play around with on my end, but otherwise I’d love to help trouble shoot this issue for a resolution at some point.

#8

I think I found the issue. The parameter size was incorrect in the config file lzw60.xml.

I posted an updated version here:

I replaced my config file with the one posted above, ran “Refresh Node Info” in HA on the device, and then pressed the button 3x, and it appears to be working correctly now.

2 Likes
#9

That did it! All works on my end and I can configure my PIR Timeout to 5 seconds! Many thanks!