Yeah maybe I should do this one next. Makes it such a PITA for the way my code is when they do stuff like that!
No worries!!! I manually changed what I needed with the parameter command. Just thought I would mention it.
@jtp10181 Hi Jeff.
Quick question if/when you have a minute. I used the link above and bought 4 800LR Zen15 that arrived today. The driver now allows a default 2 second delay (or longer) before overload protection kicks in. Do you know how that compares to the Zen15 V2 generation which just has an enable / disable option? Thanks!
Those settings are on the device itself, so the driver just lets you adjust it. They did make a change on the v2 to the overload settings. I think this was due to complains from some people where certain appliances would trip the overload on the v1 at start up even though the normal draw was well within range. The v1 would shut off for overload as soon as it detected anything over the limit. Now with the v2 it has to be overloaded for at least 2 seconds before it will shut off, and you can adjust it up to 5 seconds. There is no way to totally disable the overload protection on the v2.
All the settings have detailed info from Zooz here as well: ZEN15 Power Switch Advanced Settings - Zooz Support Center
1 Like
My experience with the ZEN04 is that it recloses after a short time after opening due to overload.
Thanks! I should have found that link myself but knowing the reason for the modification is helpful. I tried the latest version on an airfryer: Reported about 15.25A and 1760W so I was wondering if it would trip.
Cheers
Hi folks, everything seems to be working fine with my ZEN14s (FW v2.00), but I want to confirm whether or not "Generic Component Switch" is the correct Type for the child devices when using this driver (v1.2.6)?
Somebody asked the same question quite a ways back in the thread, but I didn't see an answer.
Thanks!
Yes that is correct for the ZEN14, it does not have power metering. The devices with endpoint metering get a different child driver (Using the MCP driver).
ZEN14 should use the standard driver ( Zooz ZEN Plugs Advanced).
1 Like
Upon pairing, the Advanced/Community driver was automatically selected. Are you saying I should switch back to the system driver? Or, does that mean the standard version of the community driver as opposed to MCP which isn't applicable to this hardware?
Edit: I think I see now ... There is a Zooz ZEN Plugs Advanced and a Zooz ZEN Plugs MCP Advanced. I don't think I have the MCP version installed so that contributed to my confusion. I will stick with the standard version of your driver for my ZEN14s. It's been working great for my ZEN04s and ZEN15s. Thanks!
Correct I was recommending my standard driver, Zooz ZEN Plugs Advanced
I clarified above as well for anyone else.
Thank you.
I just added a ZEN20 before fully realizing there was an MCP-specific driver. It initially loaded with the system driver and then I switched to Zooz ZEN Plugs Advanced. I ended up with two sets of child devices - similar to what somebody reported towards the end of last year.
I could not get the MCP driver to appear in HPM so I added it manually from Github. Is that expected?
I switched to the MCP driver, but still have two sets of child devices (CH1-CH5) and (Outlet1-Outlet7) - I haven't removed any yet. Only the 1-5 have per-port power metering and they are using the "Zooz PowerStrip Outlet Component" and it is greyed-out under Device Info.
Rather than delete one set of child devices now, I think I will exclude the device and start over now that the MCP driver is installed. Any thoughts on this or why I had to manually install the MCP driver are appreciated.
It is an optional item in my package, so you have to do a "Modify" in HPM and add it. I personally do not like having a bunch of extra code forced on me I am not using so I make everything optional in the packages so people can pick and chose which ones to install. Maybe a bad approach for the masses.
Since you installed it manually you could now do a match up and it should add so you get future updates.
The "Outlet" childs are probably from the incorrect driver that was set, it just picked up 7 endpoints and created 7 childs. The MCP driver will detect the "CH" child devices created from the system driver and use those but not from incorrect drivers. Or if none found it will create its own.
The easiest fix would be to change the driver to "Device" and use the command to remove all childs. Then switch back to the MCP and run configure. No need to exclude.
1 Like
Thank you, again!
Everything seems to be set now. Just to be sure, the parent device is "Zooz ZEN Plugs MCP Advanced", CH1-CH4 are "Generic Component Metering Switch" and the USBs are "Generic Component Switch".
And, I learned a couple of things... I'd actually never encountered the "Device" driver or the "Modify" option in HPM before today.
Correct but you should have CH1-5 I think.
Yes, a typo on my part. Apologies to all for the noise.
In case this driver won't work, I'm using the "Generic Z-Wave Plus Outlet" driver with my three MP21Z (that's the 800LR non-pwr reporting version of yours there - it looks exactly the same), and it works fine -- been totally reliable for me.
There are only a few parameter options for these non-PR versions, so I just used Basic ZW Tool to set the couple non-default params I needed.
For some reason, I don't think it ever occurred to me to try this driver 
1 Like
Thanks. I'm using the EvaLogik driver now (same OEM) and that's worked fine, but for some reason I thought I should look at other options. Why? Because when things work you look for ways to break them!! 
I tried the built-in Minoston driver and things went wacky...plug and lights it's in an automation with started turning back on again after I turned them off. It was late at night so I flipped back to the EvaLogik driver rather than troubleshooting. I had noticed this driver before but figured it would be interesting to see how things behaved with it if it is compatible.
1 Like
Ha, yes, I forgot to add that I did try the Minoston driver - that was no bueno indeed 
1 Like
Ah, so not just me. Thanks.
1 Like
