I was informed by Zooz Support, because I had a ticket in, that there is a firmware update for the ZEN04: ver 1.30, vs the current 1.20.
After installing it and using it awhile, these are my observations, such as they are, using the current driver:
-Reporting can almost be totally suppressed, with the exception of energy, (kwh and duration), which still is 1kwh max reporting threshold.
-This suppression can be achieved by making value of the new parameters, 10 and 11, equal to 1.
-Since they are new parameters, this can easily be done from within the current driver, and they won't be affected by save preferences, config, etc.
-On a (side) driver note, I noticed that when voltage reporting frequency was set to, say 1 minute, no reports were generated by the driver despite the fact that the device was kicking them out (as observed in the basic z-wave driver). Only when current reporting was enabled did the voltage reporting start.
-Reporting zero watts, or "off", went from 35 seconds to 5 seconds.
@jtp10181, as mentioned by velvetfoot, firmware 1.30 has been released for the Zen04. Would it be possible to have the new parameters added to the driver?
I have started working on this, but I also need to work out an issue with converting this to use my library code and also a separate issue with the ZEN14.
@neerav.modi and @velvetfoot This update adds the new parameters for FW 1.30 on ZEN04 @bill.d I was not able to replicate your issue with the repeated accessory events but I added a check for that attribute so it only sends the event if the status is changing.
This driver now should also in theory work on any multi-channel plug that does NOT have multi-channel metering. For the ZEN25 it needs multi-channel metering, but I will likely create a separate driver to handle that, based on this driver.
Run CONFIGURE for ZEN14 after updating for endpoint detection!
[1.2.0] - 2023-05-21
Refactor code to work with shared library
Added proper multi-channel detection
Added new settings for ZEN04 FW 1.30
Added notes where 0=Disabled everywhere applicable (suggestion from @velvetfoot)
I don't know if this has been noticed, or even if I might have done something else, but here goes:
I did an app switch device for a zigbee plug with a ZEN04. Then I did it again, app device switching the ZEN04 back to the zigbee plug. When I went to the ZEN04 device page, I got an abbreviated page, with an Unknown Device warning. Configure, refresh, refresh page, did nothing. Excluding and Including brought the familiar device page back.
I'm thinking you want to be somewhat careful with that apps device switch, as handy as it might be. Check that things are working, don't assume.
Again, I could be wrong.
edit: I bet if I would've set device to "device", and cleared everything out it would've worked.
This is what I've done and had no problems. And IMO a clearing/cleaning function ought to be an optional part of the switching app as the devices being swapped are frequently very different.
I was looking at the logs and I noticed one of my ZEN04's was going crazy with reporting. I think it was because some of the reporting parameters got changed to default with the revised driver. The revision that incorporated firmware update 1.30. I noticed that with all my ZEN04's, so I went into each device and changed them back to what I wanted: disable watts, amps, volts, accessory, and set logging to info.
Should not have changed or defaulted any of the existing settings from 1.20 or earlier, but the new settings for 1.30 would possibly get set to the defaults after using the new driver, if you had manually changed them already.
What do you mean the order? They are in whatever order I have them setup to in the code. I usually go in a similar order as the Zooz docs, which is sort of numerical but also they group similar settings even when not numerical order.
For the setParameter function? It tells you on the device page. The order shown on the command button top to bottom is the same order to use in RM. I put the size last so it could be optional, if you use a parameter the driver already knows about you don't have to specify the size.
Hi. I'm adding a device, that had been excluded, and I can't get the full device page, with the Reporting Disabled, etc. I've tried doing the Device Driver, Config, Refresh, Refresh page, etc...several times.
