C7 - problem with ZEN25

[k5map]

I received a new Zooz ZEN25 today and successfully paired it to my C7 (S0 unauthenticated). After a few minutes, I started seeing these errors in my log and now I can't control it from HE:

Summary

dev:452020-08-14 08:20:25.455 pm errorgroovy.lang.MissingMethodException: No signature of method: zoozDoublePlug.parse() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:34, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 0, 0, 0]), ...]
Possible solutions: parse(java.lang.String), wait(), run(), reset(), run(), grep() (parse)
dev:452020-08-14 08:20:24.820 pm errorgroovy.lang.MissingMethodException: No signature of method: zoozDoublePlug.parse() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:33, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 30, 0, 0]), ...]
Possible solutions: parse(java.lang.String), wait(), run(), reset(), run(), grep() (parse)

Any idea what may be wrong?

My apologizes about the log info not being formatted correctly... not sure how to do that.

[dadarkgtprince]

a lot of people are having issues with the ZEN25. i want to assume it's only with the C-7 hub. I have one paired to a C-5 hub and it works no issues

[neonturbo]

@k5map

My apologizes about the log info not being formatted correctly... not sure how to do that.

Screenshots are almost always better. Also, you can hide long logs and large pictures by going to the cog wheel in the posting box (upper right corner - to the right of smileys) select the text you want to hide, and click "hide details"

Summary

That gives you this.

[k5map]

Much thanks... will edit my original post

[k5map]

@dadarkgtprince are you able to turn On/Off each of the two outlets individually via your C5 HE?

[danabw]

I had endless problems w/the Zen25 on my C7 with 2.2.2 and 2.2.3, never got it to pair/work properly. I don't have any solutions, and wish you luck...for some reason some folks have it up and running, some (like me) just could not get it to work.

Mike Maxwell (HE engineer) says he has one on order and will be looking into it. You might want to sit on it until he has had a chance to look at the device and see what he can see.

[dadarkgtprince]

@k5map

@dadarkgtprince are you able to turn On/Off each of the two outlets individually via your C5 HE?

yup, no issues on C-5

https://i.imgur.com/jYMOTNJ.mp4

[Rxich]

I'm on a C4 but just upgraded my zen25 firmware to 2.0 in anticipation of using my C7 after the bugs are fixed in C7.
Check your firmware

[dadarkgtprince]

firmwareVersion: 2.0

firmware has been on 2.0 the whole time

[dadarkgtprince]

@Rxich

just upgraded my zen25 firmware to 2.0

how did you upgrade your firmware? was it through HE? or is there another process?

[k5map]

I have the V2 but do not see the firmware version in HE. Where can I find this info?

[dadarkgtprince]

@k5map

Where can I find this info?

Select the parent device from your Devices menu. Scroll to the bottom. Under Device Details, there is one row labeled Data. You'll find the firmwareVersion in there

[k5map]

I did as you stated but do not see the firmware version (pic attached)

[dadarkgtprince]

Weird, it shows it on my C-5

C-5:

I'll need to take the device closer to my C-7 to pair it since I haven't built that network up yet. I'll try it this weekend and post an update

[neonturbo]

I think you can also get this with the Basic Zwave tool. It will report in the logs. Change to that tool as the driver, get a Version Report, and swap back to the correct driver.

Super basic Z-Wave parameter tool

I just published a very basic Z-Wave tool for setting device parameters for all the tweakers out there...

[Rxich]

Mine shows right under capabilities in device page. Although I'm using a non HE native driver ( ahem- not really 3rd party, but a developer that the manufacturers rely on for drivers)
Try the driver by krlaframboise

I used an aeon zstick 5 to upgrade

[danabw]

@Rxich

krlaframboise

krlaframboise himself has said in his Zooz double plug driver thread that there was no reason to use his after the built-in driver was added to Hubitat.

@krlaframboise

Hubitat ended up adding support for the USB reporting to their built-in handler and I think it also supports all the settings in the latest firmware so you're correct, there's no reason to use this handler. (I forgot I wrote a custom Hubitat handler and responded from my phone thinking this was the ST forum)

I used both his and the Hubitat driver and neither resolved my problems w/the plug, unfortunately. Mine had FW 2.0 and I had nothing but problems w/the plug, so having 2.0 is not a panacea...but you'd think should help.

[k5map]

I'm not seeing the firmware version in my device details... also, my HE does not show the 2 child devices to control each plug individually. Might have to give the other driver a trail run.

[krlaframboise]

@danabw

I used both his and the Hubitat driver and neither resolved my problems w/the plug

I'm not sure if the code changes required for S2 have been made public so I haven't added them to any of my custom handlers yet.

This device has tons of settings and Hubitat can rarely handle them all in a single attempt so you often have to click the configure button about a minute after joining the device and then refresh the page in order to see the children and everything that should be in the data section.

[k5map]

I just clicked the Configure and then Refresh buttons and did not see any change in my Device page but did see something interesting in the log. But still do not see the 2 child devices to control each outlet individually.

Summary

dev:462020-08-15 12:19:26.165 pm debugRight Outlet Auto Turn-On After(#15) = 60

dev:462020-08-15 12:19:25.957 pm debugRight Outlet Auto Turn-On Timer Enabled(#14) = 0

dev:462020-08-15 12:19:25.656 pm debugLeft Outlet Auto Turn-On After(#11) = 60

dev:462020-08-15 12:19:25.431 pm debugLeft Outlet Auto Turn-On Timer Enabled(#10) = 0

dev:462020-08-15 12:19:25.170 pm debugRight Outlet Auto Turn-Off After(#13) = 60

dev:462020-08-15 12:19:24.922 pm debugRight Outlet Auto Turn-Off Timer Enabled(#12) = 0

dev:462020-08-15 12:19:24.654 pm debugLeft Outlet Auto Turn-Off After(#9) = 60

dev:462020-08-15 12:19:24.407 pm debugLeft Outlet Auto Turn-Off Timer Enabled(#8) = 0

dev:462020-08-15 12:19:24.140 pm debugElectrical Current Reporting Frequency(#6) = 300

dev:462020-08-15 12:19:23.898 pm debugVoltage Reporting Frequency(#5) = 300

dev:462020-08-15 12:19:23.636 pm debugEnergy Reporting Frequency(#4) = 300

dev:462020-08-15 12:19:23.362 pm debugPower Reporting Frequency(#3) = 30

dev:462020-08-15 12:19:23.119 pm debugPower Reporting Threshold(#2) = 5

dev:462020-08-15 12:19:22.835 pm debugLED Indicator Mode(#17) = 1

dev:462020-08-15 12:19:22.606 pm debugManual Control(#16) = 1

dev:462020-08-15 12:19:22.340 pm debugOverload Protection(#7) = 10

dev:462020-08-15 12:19:22.112 pm debugOn/Off Status Recovery After Power Failure(#1) = 0

dev:462020-08-15 12:19:21.518 pm debugFirmware: 2.0