I’ve just received a ZooZ ZSE40 and tried to set the Trigger interval to 200. If I click save a second time while it’s set to 200 or just exit and re-enter the thing, it then reads -56 and seems like it will read -56 for all time. Seems like it stops working correctly when I try using values past 144 even though the instructions say it supports values up to 255.
I guess the real question is can you tell from the event file what the trigger interval is actually. I’m not an expert on this, but Zwave uses signed bytes, so a one byte goes from -128 (x80) to +127 (x7F). 200 (xC8) is -56. Anyway the device should know this and trigger after 200 seconds.
Bob
I did not check to see what the interval is, but odd that 144 works if that’s the case. But no matter what, Openhab indicates values of 0-255 are acceptable and after it changes to a negative number you can’t press save any more which would seem to make at least that an Openhab error.
What version of OH are you on? There have been changes regarding validation since 3.2
144 should return a negative too, but need to know if 200 is working. Could just be a UI glitch, if it is not impacting what you want to do.
Bob
Version 3.2 and it turns out 144 doesn’t work either. I’m not quite certain how to test trigger interval.
One more question. I see 4 versions of this device in the Zwave DB. On the UI page for the device under thing properties, what is the dbReference? One version has this parameter in minutes, not seconds, another seems to have a 60 second limit, that other two have the 255.
As to testing I would think you would see in the events log. Trigger the device and wait for the all-clear. Another way is to link the channel to an item, create a rule for a change in the item to turn on or off a light and time how long the light is on. A debug log of the zwave will also work, but they can get long and you are only looking for a couple of messages.
Lastly as a battery device after any change you make in the config, you need to wake the device to get it accepted.
Bob
edit: also I’m assuming this device is fully initialized (Five line on the UI page and an XML in userdata/zwave). if not the parameter setting could be impacted.
It’s currently set to 15 and these are a few times the sensor triggered today. The shortest ones are 15 seconds so I assume the setting is seconds: I’ll change it to 150 no and post those results in a few minutes:
2022-06-13 11:54:22.095 - Item ‘Garage6MotionAlarm’ changed from OFF to ON
2022-06-13 11:54:52.891 Item ‘Garage6MotionAlarm’ changed from ON to OFF
2022-06-13 12:02:14.510 Item ‘Garage6MotionAlarm’ changed from OFF to ON
2022-06-13 12:02:46.214 Item ‘Garage6MotionAlarm’ changed from ON to OFF
2022-06-13 12:03:51.345 Item ‘Garage6MotionAlarm’ changed from OFF to ON
2022-06-13 12:05:41.721 Item ‘Garage6MotionAlarm’ changed from ON to OFF
2022-06-13 12:08:21.738 Item ‘Garage6MotionAlarm’ changed from OFF to ON
2022-06-13 12:08:53.228 Item ‘Garage6MotionAlarm’ changed from ON to OFF
2022-06-13 13:00:26.725 [Item ‘Garage6MotionAlarm’ changed from OFF to ON
2022-06-13 13:00:56.730 Item ‘Garage6MotionAlarm’ changed from ON to OFF
2022-06-13 13:50:36.505 Item ‘Garage6MotionAlarm’ changed from OFF to ON
2022-06-13 13:51:42.436 Item ‘Garage6MotionAlarm’ changed from ON to OFF
And here’s what happened after changing to 150. And all this makes me wonder what that setting means.
2022-06-13 14:40:21.423 Item ‘Garage5MotionDetect’ changed from OFF to ON
2022-06-13 14:40:51.087 Item ‘Garage5MotionDetect’ changed from ON to OFF
2022-06-13 14:42:04.892 Item ‘Garage5MotionDetect’ changed from OFF to ON
2022-06-13 14:42:34.530 Item ‘Garage5MotionDetect’ changed from ON to OFF
2022-06-13 14:55:53.793 Item ‘Garage5MotionDetect’ changed from OFF to ON
2022-06-13 14:56:23.407 Item ‘Garage5MotionDetect’ changed from ON to OFF
Are you waking the device after changing the setting? Anyway to my eye the setting is 30 seconds. Also to follow-up what is the version number? there are 4 devices in the DB of ZSE40.
Bob
Is this useful?:
- modelId ZSE40 v2
- zwave_version 2.32
- versionMin 32.2
- manufacturerId 027A
- manufacturerRef 2021:2101
- dbReference 1278
- zwave_deviceid 8449
At least to know what to look at (and it is the newest version). The default for the device is 15 seconds. As a battery device it will need to be awakened for any UI change to take effect.
Bob
Bob
I know about the wakeup for battery devices. I like the new feature where the interface shows pending so you know it’s not been updated yet.
