FYI - I just received 2 Zen04s and they are firmware 2.10. I do not know if this is based on 1.10 or if it incorporates the changes made in 1.20 and 1.30 or not. I would assume so, but the changelog doesn't mention hardware V2 at all. I've submitted a ticket with Zooz to find out.
1 Like
Send me the changes if there is anything major.
I suspect you might have gotten 800 series chips with a v2 hardware and the settings will match the prior newest firmware version. Thats what they have been doing recently.
Yup, that is the case. This is the response from Zooz.
The 2.10 firmware on ZEN04 800LR is based on the 1.30 firmware ZEN04 700 series
There's something going on with the device in Hubitat... not sure if you need to update the driver for it or if there was something else going on. I got the plug for my wife to plug some plant grow lights into. I created a simple basic rule; turn it on at sunrise and off at sunset. It seems to have turned on at sunrise just fine and I texted my wife and she says the light is still on, but the current state of the plug in Hubitat seems to suggest it's not on.
The events tab shows it turning on and not turning off.
However the log never shows it turning on. It's weird to me it would not show up here. It should have an entry where I drew the red line.
When I first set it up yesterday, it seemed to be working right. Here is me turning it on and off from the device page to test it.
I went to the device page just now and manually clicked the refresh button and the current states updated to what it should be. This generated a "Switch has turned on" event in the logs.
I'll keep an eye on it and see if the problem happens again or if it was just a fluke.
That is actually just showing that the On command was called, the device never responded or there would be a subsequent "switch" event. That is why the switch state stayed as "off".
UPDATE
I posted a minor update to GitHub to fix issues with the fingerprint, so now the driver should properly match to supported devices when they are paired. Did not increase the version since it mostly benefits new installs but if you want to update anyway just run a repair in HPM.
I just made use of the Accessory state.
I've left a plug in electric heater on in the bathroom several times. Always caught myself, but I thought I'd add a little to the safety factor.
I recognize that nothing is perfect, and this is merely a help.
The heater idles at 1.8 watts. I set the configured the accessory 'switch' to be 5 watts. Wrote a rule that turns off the plug if the accessory 'switch' is on for more than 30 minutes.
So, the plug is always on unless the heater is turned on for more than 30 minutes at a time. The time could be adjustable.
Anyway, thanks @jtp10181 , Jeff, for making this possible.
1 Like
UPDATE:
Added new driver to this package to support devices with multi-channel power (MCP) metering. This includes the ZEN20 and ZEN25, and any other similar device should work as well.
This is designed to be compatible with child devices created from the system drivers, it should detect and use those before creating any new child device. This was only tested on the ZEN20 by a couple of users so PLEASE let me know if any issues are noticed!
Must PRESS CONFIGURE BUTTON and check all your settings after changing to this driver.
MCP Driver [0.1.0] - 2023-10-21
- Initial public release to HPM
2 Likes
Testing this with my Zen25 now. Seems to be working well so far. This should be the go to driver for it going forward as it properly reflects what was set previously.
Fantastic driver as always.
2 Likes
I just noticed Zooz has a 800LR-series version of the good ol' Zen15 available now, but it doesn't appear that they've caught up with it in other Z15 documentation and firmware yet.
Something to watch though -- I'll upgrade the two Z15s I have once the dust settles with this new version here.
1 Like
I'm including two Zen04's.
One worked.
The second, I can't get the latest driver to display-I get some older version.
I've configured, saved preferences, refreshed, refreshed browser, to no avail.
When I exclude and then reinclude, I get the right driver, but some field was off...so I hit configure, and I got back to the old version; this happens each time.
This kind of thing happened in the past for me, but I've always managed to get it running.
Any tips?
That doesn't really make any sense, what do you mean an old version of the driver?
Check your driver code, do you have two different copies of it installed?
Also, may want to do a repair in HPM if you use that, I did update some fingerprints in the regular driver so it would match better when pairing new devices.
I updated to the latest firmware I had, 1.30...it was 1.20. I'm having cloudy recollections of this being necessary. That did the trick.
But, check this out:
All of my ZEN04's I had updated to 1.30. HOWEVER, for the other plug I added today, it was 2.10...the only one! I had just reached into a bag of them still in boxes. The box said ZEN04 LR.
Different firmware, different protocol.
I thought that was interesting.
Ok so yeah you were not getting an old driver, you were just not seeing all the settings. That was because of the firmware version. All of my drivers are setup to adjust the settings visible based on the firmware version of the device. So that's all that was going on. When you run a configure it checks the FW version from the device and then rebuilds the settings list.
For the LR model, yes they are upgrading all the devices to the 800 chip it seems, I think it is just much easier to get that chip so they are slowly phasing out the 700 versions. Usually they are not adding or changing settings around and since the FW version goes up my driver will keep on working like nothing happened. If they add any new settings I have a way to handle that as well.
1 Like
Or if LR Z-Wave is enabled by Hubitat, lol.
Zen14 Google Home incompatibility. Voice control of the #2 outlet does not work from Google Home. It does work with Alexa. I tried this driver to try and solve that with no success. Swapping in an Echo Dot for a Google Nest Mini solved that.
Both outlets use the same driver so not sure what would possibly cause that.
And I just tried it again and now it works. Not sure what the issue might have been. I had a spare Dot so I'll leave it in place.
I got some intel on the Z15, they added one new setting to have a delayed power on after a power outage, which I think you could already do that with the auto-on delay but maybe this only turns it back on if it was already on, and not if you had manually turned it off prior.
They told me the Switch Binary reports (class?) was being removed on all 800 chip devices, which would totally or partially break ALL of my on/off type drivers. I think that statement was a misunderstanding, because the 800LR ZEN switches have been reported as working on my existing driver.
Waiting for further response back from Zooz.
Also @hydro311 if you upgrade anything and want to get rid of old stuff I am on the lookout for a Zen15. I would like to put one on my sump pump instead of the cheapo zigbee plug I have on there now. Or maybe the dishwasher, something anyway.
1 Like
That's weird, and I actually thought that was required for Hubitat to use in drivers when they were getting the C-7 certified. I'd maybe expect them to stop using Basic instead, being very generic, but I think that is required for association and maybe backwards compatibility, so aside from maybe a parameter to control what you get, I'm not sure I'd see that either...
Also, I'm not him, but I can't resist the urge to upgrade 500-series Z-Wave devices, so I'm sure I'll have one or two to get rid of at some point point if nothing else. 
2 Likes
Yeah I think that they are just removing some (apparently undocumented settings 3/4) options from the parameter 24 that lets you chose which type of reports are sent. I dont usually expose those anyway and just force them to how I coded my driver.
Someone is relaying that incorrectly and saying the Binary class is being removed. He also said the new firmware was designed to be compatible with prior drivers so developers did not need to make changes... 
So I have high hopes that it will keep on keeping on with the same driver.
EDIT: Zooz got back to me and said Switch Binary is not going away, he had not had enough coffee yet when he sent me the first email 
3 Likes
