I installed several ZSE18LR motion sensors yesterday.
The Tamper/Vibration feature doesn't seem to work.
I'm not even sure if it's available on the LR models-I think the old ones used to rattle when shaken.
However, for these most recent sensors, I didn't hit the button 5 seconds to wake up and do the initial configuration and preferences. I figured, let it wake up on its own.
I discovered that the driver/device was spamming 'tamper' in the logs.
After waking up the device and syncing, no more spamming.
For laughs, I tried to enable tamper/vibration in the driver, and it didn't work.
Again, though, no more spamming.
Yeah mine is flakey too. It does work though, but you really have to give it a good smacking. Not really useful as a tamper alert unless someone chucks it at the floor.
And yes I have also seem the spam storm of tamper alerts before, I reported it to Zooz I think.
Hi.
I'm trying to disable Humidity reporting on the ZSE44LR.
Disabling reporting interval by setting to 0 still leaves threshold enabled.
Your driver doesn't let me set threshold to 0, but the Zooz advanced settings says that for the 800 model, it can be set to 0 to disable.
Thanks.
Yeah I see in the docs they have changed some of the settings for the new model. I will have to go through and update the driver to dynamically accomodate that.
In the meantime you can edit the range in the code, should be line 185, just change the start point from 1 to 0.
I've just installed the ZSE44 Temp/RH 800 series sensor. In the preferences section it says the Temperature Change Report Trigger Range is 10-100 but for the 800 series it is 1-100. If I try to use a value of 1 the driver complains, see screenshot below. I did try changing the range in the driver on line 180 but it did not help. Presume this needs an update somewhere else?
I added my ZSE44 to the built-in Google home integration but noticed it doesn't report humidity in the Google Home app. Is this an issue with the driver code or the platform code?
I would assume it is an issue with the GH integration. I am using the standard humidity capability and states. Could be tested with a virtual sensor that you share to GH, see how that works.
Hi. I'm having some problems with a ZSE43 800LR.
Probably reception problems but I came across the following:
There is a system driver and your driver.
I've been using the system driver.
Which driver is best, or are they the same at this point?
Thanks.
edit: Same prob with generic contact driver. Thinking the LR device isn't making it through to the hub reliably. Although the Ecolink is linked direct to hub. Weak radio/antenna in the ZSE43, I believe. Driver not a factor, apparently.
If you want to confirm the driver itself is processing messages correctly you can turn on debug logging (or trace logging on my driver as well) to see every message the driver gets from the device. The advantage of my driver for that is you can choose how long the logging stays on vs the default 30 mins only on system drivers (without having to go find and remove the turn off scheduled task). IMO my driver also has more friendly debug logging, a lot of system drivers only log the raw hex string.
I was trying to disable humidity reporting on my 800LR ZSE44.
According to Zooz, Parameter 4 can be set to zero on the 800 model to disable reporting over a threshold. Reporting by time can be disabled with another parameter.
This was not possible with the 700 series.
I'm sorry if this has already been discussed, and sorrier if it was I who brought it up.
Might be a while before I post an actual fix for that, but if you look at the code just find all the parameter specifications, find #4 and manually edit the range to start with 0. Should be a pretty easy fix even if you know nothing about code.
As a relatively recent refugee from SmartThings, there is one thing that I miss, a Groovy driver for multi-sensors that set the reporting threshold to a percent of reading for illumination readings. A fixed value reporting threshold either causes under-reporting at low vales or over reporting at high values.
Percent of reading improves the reporting, but it means the reporting threshold is updated allmost every time there is a new reading.
With a small threshold, my hub has a heavyload every day,
I have an idea for limiting the threshold limit updates, while still having a set of threshold limits that are close to the percent of scale.
This will reduce both the reporting at high lumens and the threshold updating, @jtp10181 please PM me if you are interested.
@jtp10181 I am trying to set parameter 185, the lux threshold, from RM. Using the Custom Command to configure Illumination on the device with parameters 185 and the threshold both as a number.
Have run configure on the device and pressed the zWave button for 3 seconds. No change.
Configure can’t take any parameters. Since you can’t change settings without walking the device manually I never put the set parameter commands on these divers. I suppose I could add it to the ones that have a usb power option if that’s what you are trying to do.
