First time I've received this error.
Device still works.
Pics of error log and driver specs below:
edit: attn: @bertabcd1234
What does line 290 in the driver look like? Expecting something like:
updateDataValue("zwWakeupInterval", "${cmd.seconds}")
but the error message would seem to indicate it is more like:
updateDataValue("zwWakeupInterval", cmd.seconds)
You are absolutely correct!
Perhaps I'll see if there's an driver update.
Although, I have several other ZEN34's and this is the first error I've ever gotten.
1 Like
Change it to look like the first line and the error should go away, but I believe there may be a newer version out which would be the better direction.
2 Likes
yes - newer driver is in HPM... he updated recently for associations Zooz ZEN34 associations - 
Get Help / Devices - Hubitat (side note - if you were wanting to do direct assoc you may need to be on Z/ip ~ at least to make the initial association)
1 Like
Thanks. I don't do associations, now.
1 Like
Did not get an error today.
I'm going to go out on a limb and do nothing. 
1 Like
Got another error code.
No errors on any of the 3 other ZEN34's.
Downloaded @bertabcd1234 's latest driver.
Hopefully devices will still work, lol.
Looks like the same issue as earlier.
Yes. And only on the one device.
I just tested a ZEN34, and it still works with the new driver, so that's a plus!
Hmmm, might check that device and see if it is using the new driver (don't think that line 290 has the same code in the newer version).
I just installed the driver now. So, I'll have to wait a day or two.
1 Like
this might be obvious but may want to check firmware ver too - I do remember when I got mine (I'm on hardware v1) they were not the latest ZEN34 Remote Switch Change Log - Zooz Support Center
I checked. Per the device pages, all four are on the same firmware and software (whatever that means) versions.
edit: These are LR versions, so still fairly new.
1 Like
What other error? That's the same one as your original screenshot, a couple days old now, and what the update made a couple months ago specifically fixes.
I am not aware of any problems with the current driver version (or any hardware changes to the device that should matter).
3 Likes
Didn't know that. Thanks.
