I wonder if a parameter is not set correctly to report motion status.
I don't have this sensor, but you can use a tool to view the parameters and change if necessary, if the driver you're using doesn't support it.
You are getting hub load errors, so nothing is working right.
Shut down the hub and unplug for 30 seconds and then boot it back up.
Thanks for the reply everyone. I rebooted as suggested and that has fixed most things. I suspect something after more observations, it seems the way to push new configurations to the zse11 Q sensors is not working (or I'm doing it wrong). Because all of these issues have been resolved when I just waited overnight, when is when I believe the settings get pushed to the device when they wake up to check (every 12 hours by default, correct)?
could it be possible that the "refresh" and "configure" buttons are not working even though I push those and then hold the button on the device for 3 seconds and get a confirmation single blink?
A "refresh" or "configure" is not going to do anything immediately on a Z-Wave device that is sleeping, as most battery powered devices (including this one) will be by default. On mains power, that shouldn't be an issue.
As the log entries will say when you try, waking the device manually (see the device manual for how, or I normally put it in my log entries if I know--I think just pressing the Z-Wave button on this) is one way to make that happen. The other option is to wait for the wakeup time to occur, as you note, which is set to 12 hours by this driver (and many Hubitat drivers and is likely a default for many devices).
@bertabcd1234 yes thank you for that. I think that is what I was saying, that I'm familiar with the process of sending the new configuration to the device by waking it up (which I did multiple times) but it didn't seem to take the new settings or the behavior of it wouldn't change (the problems I was having).
Are you saying I can confirm in the logs when a successful refresh has happened and the new configuration has been pushed to the device? My observations were that when I followed those steps, it would not show the new settings but things would magically "be fixed" after that 12 hour has elapsed (meaning it woke up and polled for new configurations to be loaded).
I'd check for ghosts in your z-wave table.
1 Like
With any kind of logging turned on (debug has the most info, but descriptionText should be enough -- that's the default after 30 minutes), you'll see log entries for ConfiigurationReport commands received from the device, which would be new parameter values. This won't tell you anything if the device didn't change something (and send it to the hub) or if you want to check the raw value of existing Z-Wave parameters. In that case, you might be more interested in something like this:
This is also a great idea, and a good troubleshooting step for any Z-Wave problems.
1 Like
Thanks everyone. I did find one ghost (great tip!) and removed that. I have all my zse11 sensors setup now and plan to order a few more, so when I set those up I'll pay more attention to the logs when I am "configuring" or "refreshing". The problems I saw went away after waiting overnight so I'm thinking it is something like I outlined above (but haven't confirmed yet but observing logs, which I'll do next time).
Thanks everyone for the help!
