I noticed that as well, it seems to be a delay in the plug itself reporting the reduction to 0W power. Its almost like it has to go to 0 and stay there for 30 seconds before the plug reports it. Possibly to avoid flooding reports if something is bouncing around a lot?
Wasn't there an issue with 0W in the last firmware version? That was before my time, so to speak, but I think I read something about it. Maybe this behavior is part of the fix.
They had an issue with a bunch of 0 voltage reports coming in, but yes maybe they did a delay on anything 0 reports to be sure it is correct before sending it.
I think what they should have done is had it report the zero but not report again unless it went back above say 10. That should stop the multi reporting when it's really off. Or maybe make the 10 selectable? Dunno just crazy how it works. My Sengled plugs don't do that.
Yes, agreed, it is not normal for there to be a delay. I sent an email to Zooz to let them know about it. I have some Sengled ones as well and they report very quick when the attached devices turns off. I am using one of them to monitor my Sump Pump which only runs for about 10 seconds then turns off.
On the other hand, speed wise, it seems to me the high/low setting might capture inrush (power, in this case). My oil boiler just started and the high reading said 400 while steady state is around 200 Watts. That could seem about right, or is inrush even more?
Edit: This was on a Zen15, not Zen04, sorry.
I timed it several times. Pretty consistent 30 seconds.
I just got this response from Zooz. They're working on a firmware update:
Thank you for reaching out!
We have identified this as an issue with the current firmware. We are working on a firmware update for the device, and we will reach out as soon as it is available.
Please don't hesitate to reach out with any questions in the meantime.
I know I may be stretching it, but I just plugged in a Zen04 on a garage door opener. So far, so good. I have to say, the high/low value capability is nice.
UPDATE
Big news is that I have set this driver up such that it should work universally with any Z-Wave power metering plug that follows the standards! Please let me know if it works on your device and I can update the main post with a list.
Thanks to @velvetfoot for helping to test the ZEN15 support on this driver.
[1.1.0] - 2023-01-08
Added
- Support for ZEN15
- energyDuration as an attribute so it can display on dashboard
- Over limit checking with Warn log and warnings count attribute
Changed
- Probing device for power metering support instead of hard coded by model
- Reworked the meter lists to implement the limits
- Reworked switch event handling to catch BasicReport and SwitchBinaryReport
6 Likes
Is there a way to check for warnings? I'd like to get a notification when there's a out of bounds reading even if it's filtered out.
Is it somehow connected with EnergyDuration? I noticed that it seems to be a text field, rather than number. What the heck is EnergyDuration, anyway, lol.
Thanks for you efforts.
Edit: Never mind. I scrolled down further and found warnings!
edit2: Is that a number? So to test if there's been a warning, do you test for "changed"? "increased"?
Interestingly, as I was putting a rule together, on my third trigger event, it showed two warnings. The log had, like, a gazillion volts. So, I'd guess every time the warnings count changed would be good, no?
Yes if you want an alert set it to alert when warnings increases or changes. It just counts up how many there has been since the last reset.
energyDuration is how many days the energy meter has been running since the last reset. I originally had it as a string including the word "days" but I decided to change the attribute to be just the number and forgot to change the type. I will change it for the next version.
EDIT: Decided to just push a minor fix, no version change. If you already updated run a repair to grab the fix.
1 Like
Is this the auto driver update thing? I'm not doing that yet. I'm not really using EnergyDuration, yet anyway.
Check out the new tile, lol:
Pushed the update to Github, so yes if using HPM a repair would grab the new code. Otherwise old fashioned importing works as well. Seriously though, go get HPM.
This for sure looks like a corrupted message. There should be 8 values, the first two for voltage should always be 161, 66 which gives a precision of 2 and a size of 2 among other things. The next two values are usually the voltage, then two for the delta time, and two for the previous meter. There is not a good way to know if the message came from the device like this or if it got corrupted along the way somehow. I might have to try putting some more load on mine and see if I can reproduce these issues.
Or less. This one is less than 30 watts, as well as the other, I believe.
Right now mine has one of those little air freshers plugged into it. Barely registers anything 
. I am just using it as a repeater at the moment.
If the Zen04 on the water softener, which I replaced, again, along with the little transformer powering the Zen16, locks up one more due to bogus overcurrent, I'll replace it with a Zen15 power switch, which doesn't seem to be acting up so far, and this 'feature' can be disabled.
Oh, what do you have for the ZEN16? Is it just a 1A phone charger or did you wire it direct with the 5V DC?
