jtp10181 / hubitat Goto Github PK

The setting is generating events even when the power state is not changed. The events are based on the time-based schedule for wattage reporting. Is it possible to suppress those non-state changing events? Thanks

https://community.hubitat.com/t/driver-zooz-smart-plugs-advanced-zen04-zen05-zen14-zen15/98333/166?u=jtp10181

https://community.hubitat.com/t/driver-zooz-smart-plugs-advanced-zen04-zen05-zen14-zen15/98333/168?u=jtp10181

Error downloading https://raw.githubusercontent.com/jtp10181/Hubitat/main/Drivers/zooz/packageManifest.json

Need to make sure multichannel devices get a MC lifeline association of 1:0

Impacted Devices:
ZEN52 - FIXED
ZEN14
ZEN30

https://community.hubitat.com/t/zooz-titan-water-valve-zac36-c-8-connectivity/117374/4?u=jtp10181

Would it be possible sometime to add Parameter 99 to your driver? Pretty please with cherry on top? In my case, 99's been a very helpful option, so easier access to tweak/refine that setting would be muy bueno. Thanks for consideration - all your Zooz drivers kick butt!

In the final firmware update for the Zen21, Zooz added these 2 parameters. I'm mainly interested in being able to disable programming from the switch.

I configured a ZEN71 and ZEN72 for momentary 3-way (for use with ZAC99) and notice both have pending changes.

I upgraded the ZEN71 from firmware 1.03 to 10 and still have the issue. A log when I press Save Preferences shows this:

dev:3662021-12-30 12:10:04.385 debugEntryway: Stairs: Changing associationReports (#7) from null to 15
dev:3662021-12-30 12:10:03.864 debugEntryway: Stairs: executeConfigureCmds...
dev:3662021-12-30 12:10:02.899 warnDescription logging is: true
dev:3662021-12-30 12:10:02.896 warnDebug logging is: true
dev:3662021-12-30 12:10:02.881 infoupdated...

2.3.0.121
Hardware Version
Rev C-7

Package manager claims I'm up to date:

Child Central Scene Switch v1.0.0 (driver)
Zooz ZEN Dimmer Advanced v1.5.0 (driver)
Zooz ZEN Switch Advanced v1.5.0 (driver)
Zooz ZEN30 Double Switch v1.4.4 (driver)

A log from the ZEN72 which is running firmware 1.03

dev:1692021-12-30 12:17:45.534 debugKitchen: Table light: Changing associationReports (#7) from null to 15
dev:1692021-12-30 12:17:44.699 debugKitchen: Table light: executeConfigureCmds...
dev:1692021-12-30 12:17:43.641 warnDescription logging is: true
dev:1692021-12-30 12:17:43.638 warnDebug logging is: true
dev:1692021-12-30 12:17:43.635 infoupdated...

Any more debugging info I can provide?

Thanks.

Jeff

See this thread https://community.hubitat.com/t/possible-to-use-zooz-zen21-led-as-indicator-zwave-setting-by-rm/66076

https://community.hubitat.com/t/release-zooz-zen-switches-advanced-drivers/58649/51?u=jtp10181

This is due to some parameters not being supported, so the driver keeps thinking that it needs to update them still when it does not hear back from the device that it was updated.

"Report" is misspelled in some (maybe all?) of the drivers. For example, see line 869 in the ZEN27 driver:

return getParam(7, "Send Status Repot to Associations on", 1, 15, associationReportsOptions)

Thought I should mention it. 😄

The ZSE44 is missing deviceModel from the data section like you have for other devices.

geting an error when downloading either Zooz ZSE40 4-in-1 Multisensor or Zooz ZEN Plugs Universal via HPM

Failed download of file
An error occurred downloading https://jtp10181.gateway.scarf.sh/zooz-zen-plugs-v1.2.2.groovy

Failed download of file
An error occurred downloading https://jtp10181.gateway.scarf.sh/zooz-zse40-v1.2.0.groovy

I am trying up update via HPM and getting this error:

I thought that I installed it with HPM originally. It was showing current version N/A. I ran a match and it shows installed version 0.0 and when trying to update still getting the error below. Is it supported to update the driver using HPM when it is assigned to devices?

Error Occurred During Installation
An error occurred while installing the package: Failed to upgrade driver https://jtp10181.gateway.scarf.sh/zooz-zen-plugs-mcp-v1.2.2.groovy.

Be sure the package is not in use with devices.

My Leviton DZ6HD dimmers do not respond to the initial discovery query (see attached):

firmwareVersion: 1.22
hardwareVersion: 255
configVals: [:]

When the ZSE11-800LR is in direct sunlight it is reporting negative values instead of maxing out at 32767. FW: 2.00, HW: 2, Driver: 1.2.2

https://community.hubitat.com/t/hubitat-homekit-bridge-zooz-z72-dimmer-issues/111315/11?u=jtp10181

OK I see why that's not working, the commands are so close together the driver has the same issue as the device, the last level is from prior, not the most recent command. Should have known that would happen.

What if I set a "pending level" state var and then ignore the on command if the level is pending.

[waterboysh]
How big of a deal would it be to add an option for a backup sensor? I have a ZSE44 and a ZSE40 in each bathroom. I use the ZSE44 since the ZSE40 will prioritize sending motion events. But it'd be nice to select it as a backup device if the primary device has been inactive for a certain amount of time. Even more awesome if it could flip a switch or send a notification when it decides to do this.

https://community.hubitat.com/t/app-smarter-humidity-fan-fork-for-testing/95138/35?u=jtp10181

[waterboysh]
I also sometimes have the issue of the light or fan reporting the opposite of what it actually is on a particular Zen30. It's one of the newer V3 zwave 700 series ones also on firmware 3.10. I never saw this until I setup a room lighting automation to turn the fan and light on and off with motion. I think there is a potential issue with sending both the switch and relay commands at the exact same time.

Most often it seems to be that the fan doesn't turn off, but the light does. If I look at the device page, it'll say both are off.

I was wondering if the driver has a way of integrating a small delay (maybe as a configurable setting) if a command is sent to both within a very short time frame. I don't have any logs of when this has happened to share. It usually goes unnoticed or is noticed well after the fact when passing by the room. It also doesn't happen super often.

EDIT: Oh, and if it matters I am using your custom driver for the relay so that Google recognizes it as a fan and not a light.

https://community.hubitat.com/t/driver-zooz-zen-switches-advanced-and-dimmers/58649/379?u=jtp10181

Info logging for the ZEN30 child device should be sent to the child to log, so that the logs can be filtered by device if desired.

https://community.hubitat.com/t/release-zooz-zen-switches-advanced-drivers/58649/48?u=jtp10181

Need a check for newer firmware and possibly force the brightness correction off. Firmware implements this feature itself so the driver feature is not needed anymore.

https://community.hubitat.com/t/driver-zooz-zen-switches-advanced-and-dimmers/58649/366?u=jtp10181

Hey Jeff,
I ran into a minor issue with the Leviton driver. I was working on an alert rule and needed to flash a lamp connected to a DZ6HD as part of the rule. It wouldn't work. Problem was the Flash Rate was set too slow.

The Flash rate was not exposed, so I had to switch to the 'Generic Z-Wave Smart Dimmer' driver to set it, then switched back to the Leviton driver. No big deal, just thought you might want to know.
Thanks - Joe

All I know is that the "Generic Z-Wave Smart Dimmer" driver offers a few fixed choices like 750ms, 1Sec, 2Sec, etc. I've been playing with this with rule machine and don't see a way to set flash time within a rule. You can delay the start of the flash but can't see how to set the flash rate in RM 5.1.

Maybe I set it accidentally without knowing it, but my Leviton device was set for 2 seconds, which screwed up the HE and I got excessive traffic warnings. Once I set it for 750 ms (the fastest choice in the driver) everything worked in my rule.

I checked a few of my other devices and they all come up with the 750ms setting. I do remember reading a thread about some devices not supporting Flash, but that HE will simulate it if not available.

https://community.hubitat.com/t/l4viton-dimmer-flash-rate/115521

Use same logic as ZEN04 driver to filter out bogus events.

https://community.hubitat.com/t/driver-zooz-sensors-advanced-zse40-zse44/81074/126?u=jtp10181

I have a ZEN 54 with a Hubitat C-7 hub. It does not Dim. The 0-10V output is always at 8 volts regardless of the level I set. Any ideas?

Finaly got this up and running today. Found an oddity; Looks like either the name was incorrectly duplicated the second time GMS3 is listed, or there is a device mismatch going on .

Based on everything around it, looks like it's one line all the way across per device , then I found this on:

GMS3 is a Ring Gen 2 Motion sensor, no way it could be LR.

LRMS2 is a Zooz ZSE18LR, and should be paired LR. so how did these two end up on the same line?

For comparison, here is the rest of the table

I do see one possible issue, if a child is off (or on) and I send the same command to it again, the plug only reports back the parent state and not the endpoint/child state. I am also noticing the parent state is just mirroring whatever that last endpoint change was, if I turn one ON the parent reports On, if they are both on and I turn one off, the parent reports off. Makes no sense really. I think Zooz changed something with a firmware update because I don't remember it doing that when I made the driver.

https://community.hubitat.com/t/driver-zooz-smart-plugs-advanced-zen04-zen05-zen14-zen15/98333/158?u=jtp10181

Firmware 4.10 added some parameters that aren't defined in the driver currently.

Is there anyway to add those parameters?

VER. 800LR (released 11/2023)

Hardware:

800 Series Z-Wave chip

Firmware: 4.10

Long Range Ready
Separated ramp rate settings into 4 new parameters: ramp rate ON physical (13), ramp rate OFF physical (31), ramp rate ON Z-Wave (32), and ramp rate OFF Z-Wave (33). [See all settings here.](https://www.support.getzooz.com/kb/article/468-zen30-double-switch-advanced-settings/)
Adjust Double Tap (parameter 17) and Single Tap (parameter 18) behavior to match ZEN72 and ZEN77 dimmers.

This location is running Hubitat C5 version 2.3.8.140
Device is ZSE40 700 Series 4-in-1 Sensor
Previous custom driver version 1.0.5
Upgraded to version 1.2.0

This version on the C5 is making the device in Hubitat unresponsive. The device still blinks when motion is active but the driver in Hubitat continues to show inactive. Also all the pending changes never updates the device even if I wake-up the device multiple times. Temperature and humidity reading do not update as well.

At another location running Hubitat C7 (2.3.8.140) I am running version 1.2.0 with NO problems at all. Maybe there is an issue with Hubitat C5 and this version 1.2.0.

I spent many hours including and excluding the device to figure out what's happening but after switching to the driver provided by Hubitat the device started to work. The only problem I have in using the Hubitat driver is that it does not allow me to make changes to the Temperature and Humidity offsets.

Is it possible that you can provide me a link to download custom version 1.0.5? I have a few remote locations running Hubitat hubs and this is the only one still running the C5 and I need to control a few important devices with this ZSE40 and for now I had to make code changes to compensate the for the offsets I need to setup in the driver.

Thank you for your code and help in this matter.

Paul

[velvetfoot]
I'm in the process of adding a Zen15 and I'd like to suggest that the driver add something like "0 to disable" in the applicable boxes. They have the range, but not that 0 disables the reporting option. This might help those not familiar with the advanced settings.

https://community.hubitat.com/t/driver-zooz-smart-plugs-advanced-zen04-zen05-zen14-zen15/98333/137?u=jtp10181