I've run into an issue with the Hubitat Driver for the Zen15, aka, Power Switch.
Parameter 24, which is not exposed as a choice on the device page, defaults to "2" with a parameter save or config.
"2" will not show a change an on/off state change if done programmatically, only if the button is pushed. I, and I'm assuming everyone, lol, would want "1" which does show on/off.
No big deal, just change it with the Basic Z-Wave tool. Thing is, it'll go back to "2" if parameter save or config button is pushed, as I said. This could easily be done inadvertently.
I'd say, if you're not going to expose it in the device page, don't change it with those button pushes.
It seems that auto/on and off, also not exposed on the driver page, aren't affected by this reverting back to some default upon config or param save.
edit: I'm not sure how to go about this bug reporting thing, so @bobbyD , please forgive me if I'm doing it wrong.
@jtp10181 has written many drivers for Zooz switches/dimmers/plugs. Not sure if he has written one for the ZEN15, but if he has, I would recommend using it.
Alright I will put together a beta version to try out. I think I can just setup the params on my existing driver and it should work the same as the zen04.
@velvetfoot does it possibly set that param to 2 because when you send an ON/OFF command via the driver it automatically requests the status to be sent back? So it may work fine there but then the auto on/off which was added in the 1.06 firmware is probably not sending reports due to that parameter?
Would this mean param adjustment could also happen?
Also, still diggin' the Hi/Lo.
There are differences in the two, though.
-You can disable the overcurrent protection in the Zen15
-You can disable the timed reports totally in the Zen15.
-On/Off Status change notifications in the Zen15 (as mentioned earlier)
-Manual control can be disabled in the Zen15.
Timed reports you can just about eliminate them with a long duration, like the max of 45 days.
I personally can see with just doing the other things by way of the Basic Z-wave editor, but that's just me. As long as they don't get changed by a config or pref save, lol.
I am reviewing the docs for the ZEN15 now, it will support all the parameters. The way I have my code built I can setup specific parameter lists for each device and it will adjust once it figures out the device you have it on.
I don't think so. One, because I was trying to limit the on/offs on my refrigerator, lol. I actually tested it. I changed the param in z-wave basic tool, went back to power switch driver, and one time did a pref save, and another iteration the config. It got changed both times, no on/offs, far as I can remember. The actual parameter gets changed. I'm not observing behavior after an auto on, or something like that.
I think this will work and give you all the settings. Should also force parameter 24 to a value of 1.
You may need to run Configure twice for it to detect and present all the power options. WARNING - this will possibly reset your energy duration, parameters, and possibly other stuff.
You will need to "Save Preferences" on anything else already using this driver also, to set a new state variable used to determine if the device is power reporting or not.
Just updated driver above. How is it working on ZEN15 since I have no way to test it?
I also added a feature that will ignore anything over preset limits, log a warning and also what normally is in debug logs (as warn level). Also increments a warnings attribute that could be used to trigger RM. You would have to check the logs to see the actual warning though.
I may need to increase the limit for the ZEN15 though, it was set at 18Amps from whatever code I borrowed in past (and was not being used). Will have to look into the specs and possibly set better limits for final version.
So, you're thinking it's a communications thing? My mesh should be pretty strong with all the switches, etc, I have.
On the driver, it's cool that different options come up depending on whether it's a zen04 or zen15-like 0 as an option to disable timed reports you don't want, which is an option that the 15 has but 04 doesn't.
Yes, thinking somehow the messages are getting mangled but still passing the CRC check at random. Seems like it should not be possible as often as you and others are reporting it on the ZSE44 though. If I can see the full zwave message it might give a hint as to whats going on.
Just had another idea, the zwave message actually lists the previous value and the time elapsed since the previous report. If the mangled messages have bad info there as well, I might be able to verify it is a good message from that info. If the false readings have accurate info in the previousValue then I would be tipping more towards the device is actually sending out bad info.
Are you getting any bad info from the ZEN15 or only the ZEN04's?
I put the option in there to disable it with the warning from the Zooz settings docs.
That would be this complicated settings map I invented where I can make adjustments per model number in a universial driver:
Unless you have multiple copies of the driver installed, when you update the code it will apply to all devices using it. This version wont be in HPM (yet) anyway, I just posted it on Gist for testing.
@jtp10181 : On the Zen15, the switch state doesn't change unless refreshed. The switch does physically change. I checked to make sure parameter 24 was 1, and it was. I tried this on two of my Zen15's, and they both did this.
This is the debug log:
There doesn't seem to be a problem with the Zen04. I get a debug message like this when I turn it off and on:
