For the devs to fix if they have time:
One On action and one Off action results in multiple device log entries.
For the devs to fix if they have time:
One On action and one Off action results in multiple device log entries.
What do debug logs show during this time, and what specific device are you using?
This happens for all my "Generic Z-Wave Plus Outlet" devices too -- I don't know if this has always been the case, or something recent.
I've only noticed lately because I'm playing with some rules for a couple of those devices.
My devices are a few Minoston MP21Z plugs, a couple GE outlets, and several Leviton ZW15R outlets -- this double-log behavior is consistent for all of them.
If I command a Refresh, it just gives one log entry, but it's "XYZ was turned on (off)" instead of "XYZ is on (off)", but that's perhaps a topic for another day
What do debug logs show when this happens?
Apologies - I forgot that part... Here are logs starting with an Off-On sequence with no debug logs (both double entry).
Then I turned on debug logs and did another Off- On sequence (and then turned off debug).
That one above is for one of my Minoston plugs. Here's one for one of my Leviton ZW15R outlets (on/off w/ no debug, then debug on for another on/off, then debug off). For this one, I added a "Refresh" command at the very end too.
I noticed in my Minoston logs, it didn't double-entry the last "On" command. So I wanted to test a different device -- this time, my Leviton does double the last command (Off) too
The text shown is description text logging, even though the device is reporting twice only one actual event on the hub will be generated, you can verify this by looking at the events in the driver itself
Fair enough -- thanks.
Yeah, I definitely didn't mean to imply that I suspected double events were actually occurring or anything like that -- they aren't -- there's very obviously just one relay click per event.
Just seemed odd that this one driver in particular reports double logs like that, but it's no skin off my back since everything is actually working perfectly fine.
Thanks again!
Its the device reporting twice, not the driver, annoying, but harmless...