ZEN71 and ZEN72 Pending changes, even after upgrade to firmware 10 about hubitat HOT 8 CLOSED

Can you edit the driver code and uncomment the log.trace at the very bottom. Also enable the debugging on the device. Then try again to confirm my suspicion. Post a screenshot of the log entry if you can, that is easier to read than a text paste. There should be some trace stuff that comes back after it tries to change the parameter. I suspect Zooz did not include that parameter in those two devices for some reason. Those are the only two I do not have myself to test on.

from hubitat.

Here is the log after that change and hitting Save Preference and then a Configure. What's confusing is that I don't see the prior messages in this log?

I like these because the style matches the ZEN32 scene controllers I have.

from hubitat.

You must have forgotten to turn on debug logging again, but no worries I can see that the value being returned is paramNum 1, which means that the one it is trying to set, is not valid for that device.

It is not actually hurting anything besides being annoying. If you want to fix it for now you can edit the code to remove that parameter from the 71 and 72. On the dimmer driver this is around line 424, or 357 for the switch. I will just add the 'changes' section as shown below to my next update to fix it.

	associationReports: [ num: 7,
		title: "Send Status Report to Associations on", 
		size: 1, defaultVal: 15, 
		options: [ 0:"None", 1:"Physical Tap On ZEN Only", 2:"Physical Tap On Connected 3-Way Switch Only", 3:"Physical Tap On ZEN / 3-Way Switch",
			4:"Z-Wave Command From Hub", 5:"Physical Tap On ZEN / Z-Wave Command", 6:"Physical Tap On 3-Way Switch / Z-Wave Command",
			7:"Physical Tap On ZEN / 3-Way Switch / Z-Wave Command", 8:"Timer Only", 9:"Physical Tap On ZEN / Timer",
			10:"Physical Tap On 3-Way Switch / Timer", 11:"Physical Tap On ZEN / 3-Way Switch / Timer", 12:"Z-Wave Command From Hub / Timer",
			13:"Physical Tap On ZEN / Z-Wave Command / Timer", 14:"Physical Tap On ZEN / 3-Way Switch / Z-Wave Command / Timer",
			15:"All Of The Above" 
		],
		changes: [71:[num:null], 72:[num:null]]
	],

from hubitat.

You are right, I didn't have debug logging on. I glanced and had Descriptive Text logging on and mis-read it.

Making those changes gets past that parameter. Now we are back to the core issue I was having, setting the 3-way switch type on the ZEN71. It works on the ZEN72, but on the ZEN71 it does not get set and I have 1 change pending.

Looking at the docs, this switch only allows values of #12 of 0 (on/off) or 1 (momentary).

Using the menu item for Toggle On/Off with 2x/3x which sets it to 1, results in a proper sync. However the ZAC99 now does nothing. I'll have to reach out to to Zooz about that.

The ZEN72 docs indicate that it supports the full set of values for parameter 19.

Would it be useful to have a ZEN71 and ZEN72, I could send you a pair.

Thanks.

Jeff

from hubitat.

Setting it to 1 should do the trick and allow the momentary to work, so if that's not working it could be a firmware issue. As far as the parameter options... this one is a pain because half have 2 options and half have 4, so the make the code less confusing I am going to split it into two sections. On your switch driver if you want to test, around line 339, the threeWaySwitchType is changed and threeWaySwitchType2 is added.

	threeWaySwitchType: [num: null, // (12)
		title: "3-Way Switch Type",
		size: 1, defaultVal: 0, 
		options: [0:"Toggle On/Off Switch", 1:"Momentary Switch"],
		changes: [21:[num: 12],23:[num: 12],71:[num: 12]]
	],
	threeWaySwitchType2: [num: null, // (19)
		title: "3-Way Switch Type",
		size: 1, defaultVal: 0, 
		options: [0:"Toggle On/Off Switch", 1:"Toggle On/Off with 2x/3x Shortcuts", 2:"Momentary Switch", 3:"Momentary with 2x/Hold Shortcuts"],
		changes: [22:[num: 19],24:[num: 19],72:[num: 19]]
	],

from hubitat.

That seems to do the right thing as far as setting the parameter goes. The switch is not responding to the traveller input at all, I'm discussing that with Zooz support.

Thanks.

Jeff

from hubitat.

Great, I will get an update out with those fixes soon.

from hubitat.

This was fixed with commit e0d2c6c

from hubitat.