Ugh omg sorry. I'll try physically testing that way again, cant remember if I did post beta upgrade.. sounds like I probably didnt. Thank you for everything!
Every day that I check my hub that is running the Beta version of this driver it says there is an update in HPM. I assume you're not updating it every day? Anyone else see this?
[edit] As I posted this I realized I had never tried to run another update after running a update, to see if it still said there was an update. It turns out it does so something is going on with HPM. Is this normal for using a Beta?
It has happened to other people. You could try running a repair on it. Or maybe unmatch the package and then match again (will have to enable beta again after matching).
1 Like
I don't think this has anything to do with your beta drivers. I have not switched over to them yet and I am getting the HOM update notifications as well.
One thing i did notice is the package manifest has a version for the package as a whole and then each driver has a version and betaVersion tag. Have you tried removing the version tag from the package section at the top?
1 Like
Jeff,
Could you consider adding parameter 20 to the driver on your next touch?
Scene Control Multi-Tap
Parameter 20: Disable multi-tap scene control so that only single taps report via central scene. Once this functionality is disabled, double taps, held, released, 3-tap, 4-tap, and 5-tap events will be ignored and won't be reported to the hub.
Values: 0 – multi-tap for scene control enabled; 1 – multi-tap for scene control disabled. Default: 0.
Size: 1 byte dec
I'm presently using button mode to work around the physical detect issue. While this is working, it results in a noticeable switch lag (because the switch waiting for double, triple taps etc before it fires). I'm only using the single tap, so disabling this should make it faster.
What switch is that for? The switch/dimmer pack supports 7 different models.
Sorry, this is the ZEN71 .
https://www.support.getzooz.com/kb/article/535-zen71-on-off-switch-advanced-settings/
Ok, and in the meantime you can change the setting using the "Set Parameter" command, you just need to know the "size" which is in the zooz settings docs (most are 1).
Thanks Jeff... again.
I should have thought of that. Yes, the zooz faq shows the parameter as one byte.
Applying it manually it did the trick, no (perceptible) delay on the switch now. Having the eventual driver support will ensure the setting persists.
Reminds me I still need to capture trace logs to send to hubitat for what may be the ZWJS bug (no 'physical on' reported) for ZEN71 . They may want me to switch to native driver and test that too.
It may work fine on the native driver, if they use the generic "guessing" method I eluded to wherever that conversation happened. The method I used is device specific and in theory should be more reliable because it uses the different types of responses from the device to make the determination.
It works great when you do not have Zwave JS in the middle trying to be "helpful" by transforming and changing the messages from the device. ZIP just passes the raw hex to the driver, and Hubitat's parse method converts it to useable data that in nearly all cases exactly matches the intention of the raw hex.