C-7 Driver Issues

[bcopeland]

I wanted to get a list going of any built-in driver issues that my still exist on the platform after 2.2.3.135. Please reply to this with drivers that are not operating properly. Please include the model of the device, what driver it is using, and what are the issues.

[mailtomatte]

Fibaro UBS FGBS-001: Childs dont report status.
Fibaro Dimmer 2 FGD-212: Sometimes don't report status right
Qubino flush relay 2ZMNHBD1 .:childs dont work
Qubino Flush Dimmer 2: Sometimes don't report status right'
Qubino Flush shutter * ZMNHCD1 : Sometimes reports wrong status
Fibaro RGBW FGRGBW-442:Missing separate childs for each color

Community drivers not working (should be included in HE)
Fibaro Double Switch FGS 223 childs not working (fibaro double switch 2 fgs223 driver)
Fibaro Shutter 2 Dont report % of level right (generic driver)

Thanx /Mattias

[danabw]

Zooz ZEN25 Double Plug has issues pairing and operating properly w/C7 hub. @mike.maxwell said on one of the threads that he was going to order one to look into it.

Illustrative threads below:

Zooz ZEN25 log errors - C7

Getting the following message in the logs over and over. And I’ve even turned off all logging. I selected the Zooz double plug as the driver. Any clue what to make of this error? [image]

Zooz Double Plug (Zen25) child devices - Consistently not working from Dashboard (or at all)

I've added a Zooz Double plug using the built-in Zooz double-plug driver. I can control both plugs from the main device page, and each outlet separately from the child devices pages. FWIW, the Child device pages don't seem to update very well, when I got to them they often don't have the correct current state of the left/right outlet. However, when I add them to a dashboard, as a switch or outlet, only the parent device tile works. Both child devices freeze as soon as I click on them, w/a "Sen…

C7 - problem with ZEN25

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, comma…

Zooz double plug doubled up in the wrong way - can't remove (new C7 FW/Radio)

Thanks! Just to provide some feedback, I started the repair, the Zwave repair in progress (or something like that) messaging appeared briefly and then the screen jumped/refreshed and it went back to normal w/no message. Obviously way too fast, so hit the Zwave repair button again and got a message dialog that the repair is in progress. Not sure this is how you guys meant it to be - I'm pretty sure I remember on 2.2.2 that when a Zwave repair was running there was a persistent message on the Zw…

Off-topic rant about security

My Zooz Zen25 double plug is not being fully recognized during the inclusion process, even after updating the hub and radio firmware to the latest version. The inclusion process completes, but it is being added as a generic "device" in the device list, preventing me from each individual plug in the device list. I initially tried including the device with default authentication that is checked (security 2 class 0). Other things I've tried: Used other authentication methods, including no authen…

[ourmessages]

Aeotec recessed door sensor 7 using both generic ZWave contact driver
and the Aeotec DW sensor 7 driver. Neither work.

Although with 30 min of run time everything else seems to be working better.

[672southmain]

All of these have been tested as repeatable on my C-5 hub. I have not yet put devices on my C-7.

Support Ticket 17749: multiple issues with Aeotec Door Sensor 7 Series driver when used on Aeotec Door/Window Sensor 7 (ZWA008-A). Workaround: use Aeotec Door/Window Sensor 7 driver from firmware 2.2.1.116. Regression testing of this bug is difficult because of issues discussed in that ticket.

I’ve just discovered additional issues with the Aeotec Door Sensor 7 Series driver when used with Aeotec Recessed Door Sensor 7 (I’ve got 3). Have not turned in a ticket yet, I’m doing testing to create minimal test cases, but, briefly, on the same driver, some of the devices report position of the tamper switch and others don’t report any tamper Switch line; some report one formatting of firmware version, others report another formatting; one drains the battery in 7 days, others have gone months on original battery, all report same device, mfr, etc.

edit: If it matters, all 3 Aeotec Recessed Door Sensor 7 devices (bought & installed at same time) originally used the built-in Aeotec Recessed Door Sensor 7 driver, and were switched to the consolidated Aeotec Door Sensor 7 Series driver, upon advice by @bobbyD, when the older driver became Deprecated a few months ago.

Support Ticket 17402: cosmetic issue with Zooz Zen16 driver, still present with 2.2.3.135.

[datavortex]

In my opinion the numbering for buttons 1 and 2 in Inovelli Fan/Light Switch is unexpected and seems reversed. Lights (2) are on top and fan (1) is on the bottom.

[rob9]

I'm not having good luck with the Schlage BE468/BE469 driver and the corresponding locks.

I have 4 of these door locks and the messages passing through aren't making a lot of sense.

It seems to often confuse "physical" and "digital" actions (e.g., turning the thumb knob vs. sending a lock/unlock request over z-wave).

Plus, I'll see several events (often with conflicting information) for the same action I take with the lock.

The S2 Zwave Plus one (brand new) seems to be the worst. Distance seems to also be an issue--they seem to route directly too the hub, but I'm not sure all the messages are getting there properly (I don't seem to get very timely event triggering).

[bobbles]

To be honest you need to look at most of the Fibaro devices.
All mine worked on 2.2.2 using custom drivers.
Now...........
Some do not work. Period.
Others work with mitigation put in. Refresh commands etc.
I have opened a thread already about this at the request of Mike.

[mag]

Leviton VRPA1 - PlugIn Appliance switch - connects fine; however, it's being incorrectly detected as "Generic Z-Wave CentralScene Dimmer".

If changed to "Generic Z-Wave CentralScene Switch", works for switching the load. But:
'Turn on indicator' option in Preferences does not do anything.
Current States/numberOfButtons = 2, for some reason.

[simon]

Yale Conexis L1 Lock

Lock and Unlock commands work. Status always remains at "unknown". No normal Locked or Unlocked messages. Here's what is logged after I locked/unlocked a number of times.....

dev:43272020-08-26 11:11:29.978 debugskip cmd: NotificationReport(v1AlarmType:22, v1AlarmLevel:1, reserved:0, notificationStatus:0, notificationType:0, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:43272020-08-26 11:11:29.897 debugparse: zw device: 61, command: 7105, payload: 16 01 , isMulticast: false
dev:43272020-08-26 11:11:28.949 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:2, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:1)
dev:43272020-08-26 11:11:28.912 debugparse: zw device: 61, command: 6203, payload: 00 10 02 FE FE , isMulticast: false
dev:43272020-08-26 11:05:51.251 debugskip cmd: NotificationReport(v1AlarmType:21, v1AlarmLevel:1, reserved:0, notificationStatus:0, notificationType:0, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:43272020-08-26 11:05:51.247 debugparse: zw device: 61, command: 7105, payload: 15 01 , isMulticast: false
dev:43272020-08-26 11:05:50.172 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:1, doorLockMode:255, insideDoorHandlesMode:0, lockTimeoutMinutes:0, lockTimeoutSeconds:0, outsideDoorHandlesMode:0)
dev:43272020-08-26 11:05:50.168 debugparse: zw device: 61, command: 6203, payload: FF 00 01 00 00 , isMulticast: false
dev:43272020-08-26 11:05:44.956 debugskip cmd: NotificationReport(v1AlarmType:9, v1AlarmLevel:0, reserved:0, notificationStatus:0, notificationType:0, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:43272020-08-26 11:05:44.953 debugparse: zw device: 61, command: 7105, payload: 09 00 , isMulticast: false
dev:43272020-08-26 11:05:37.342 debugskip cmd: NotificationReport(v1AlarmType:25, v1AlarmLevel:1, reserved:0, notificationStatus:0, notificationType:0, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:43272020-08-26 11:05:37.338 debugparse: zw device: 61, command: 7105, payload: 19 01 , isMulticast: false
dev:43272020-08-26 11:05:36.068 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:2, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:1)
dev:43272020-08-26 11:05:36.063 debugparse: zw device: 61, command: 6203, payload: 00 10 02 FE FE , isMulticast: false
dev:43272020-08-26 11:05:29.285 infoTB Porch Front Door Lock has a low battery
dev:43272020-08-26 11:05:29.282 debugBatteryReport: BatteryReport(batteryLevel:255)
dev:43272020-08-26 11:05:29.266 debugparse: zw device: 61, command: 8003, payload: FF , isMulticast: false
dev:43272020-08-26 11:05:01.572 debugskip cmd: NotificationReport(v1AlarmType:25, v1AlarmLevel:1, reserved:0, notificationStatus:0, notificationType:0, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:43272020-08-26 11:05:01.568 debugparse: zw device: 61, command: 7105, payload: 19 01 , isMulticast: false
dev:43272020-08-26 11:05:00.623 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:2, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:1)
dev:43272020-08-26 11:05:00.608 debugparse: zw device: 61, command: 6203, payload: 00 10 02 FE FE , isMulticast: false
dev:43272020-08-26 11:04:56.647 debugskip cmd: NotificationReport(v1AlarmType:21, v1AlarmLevel:1, reserved:0, notificationStatus:0, notificationType:0, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:43272020-08-26 11:04:56.643 debugparse: zw device: 61, command: 7105, payload: 15 01 , isMulticast: false
dev:43272020-08-26 11:04:55.656 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:1, doorLockMode:255, insideDoorHandlesMode:0, lockTimeoutMinutes:0, lockTimeoutSeconds:0, outsideDoorHandlesMode:0)
dev:43272020-08-26 11:04:55.652 debugparse: zw device: 61, command: 6203, payload: FF 00 01 00 00 , isMulticast: false
dev:43272020-08-26 11:04:51.676 debugskip cmd: NotificationReport(v1AlarmType:22, v1AlarmLevel:1, reserved:0, notificationStatus:0, notificationType:0, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:43272020-08-26 11:04:51.672 debugparse: zw device: 61, command: 7105, payload: 16 01 , isMulticast: false
dev:43272020-08-26 11:04:50.090 debugskip cmd: NotificationReport(v1AlarmType:9, v1AlarmLevel:0, reserved:0, notificationStatus:0, notificationType:0, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:43272020-08-26 11:04:50.086 debugparse: zw device: 61, command: 7105, payload: 09 00 , isMulticast: false
dev:43272020-08-26 11:02:52.302 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:2, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:1)
dev:43272020-08-26 11:02:52.237 debugparse: zw device: 61, command: 6203, payload: 00 10 02 FE FE , isMulticast: false
dev:43272020-08-26 11:01:56.026 debugskip cmd: NotificationReport(v1AlarmType:22, v1AlarmLevel:1, reserved:0, notificationStatus:0, notificationType:0, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:43272020-08-26 11:01:56.021 debugparse: zw device: 61, command: 7105, payload: 16 01 , isMulticast: false
dev:43272020-08-26 11:01:54.658 debugskip cmd: NotificationReport(v1AlarmType:9, v1AlarmLevel:0, reserved:0, notificationStatus:0, notificationType:0, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:43272020-08-26 11:01:54.569 debugparse: zw device: 61, command: 7105, payload: 09 00 , isMulticast: false

[tivomaniac]

@rob9 you might try putting a z-wave repeater between the hub and lock if there isn't one. I am using a BE469 and so far I'm not having any issues. Before the repeater it would sometimes show unlocked on my dashboard when I was in fact locked but I haven't seen that since.

[rob9]

It's like 20-40 feet away. I have 3 repeaters in my house--but none of the locks seem to want to use them. Short of sticking them to tripods with extension cords in the middle of the family room and the hall, I'm not sure how much more I can do!

I'm somewhat limited, also, by trying to keep the repeaters attached to a UPS so things work if the power goes out.

[672southmain]

The Ring Alarm Extender v2 has its own battery backup and sends power fail notification

[rob9]

I have one of those and I have 2 Aeotec Range Extender 7 devices. The Ring one is a few feet from one door. One of the Aeotecs is near another door. And the third extender is in the center of the house, in the rafters in the basement.

[tivomaniac]

My routing table shows the Schlage using my Aeotec 7.

[jerryamile]

I never could get:

Monoprice Motion/Temperature Z-Wave 15271

To work, the motion never updated, now that I updated to the latest firmware for C7, I don't even see the variable of motion or no motion any more, Now it's just a temperature sensor.
I might try to turn on my smart thing hub to see if I can add it successfully back to that, as it was working fine with it before.
Posted about the issue: Monoprice Motion/Temperature Z-Wave 15271 No motion updates
and someone else had the same problem here:
Monoprice PIR Motion Sensor with Temperature

[jerryamile]

Ok I just added it back to Smart things Hub V2, no problems, working good. Motion,temperature,tamper switch. And I don't have any device handlers installed.

[mag]

Zooz Power Strip ZEN20 v2.0:

Connected okay with S2 and all 120V channels seem to be working; however:

1. power reporting is all wrong - 25.5W regardless of the load changes.
2. No reporting for USB channels
3. Energy - in kWh for a newly connected strip.
4. In response to Reset button click, the log says: " 2020-08-26 21:21:15.810 warnIgnoring reset() command because this firmware version does not support power/energy reporting"

Update:

as it turns out, the statement "Connected okay with S2" was a little too optimistic.
I did select "Security 2 Class 2 - Access Control" option but when the device connects, the actual Security level is reported to be 'None'. And I get this:
"2020-08-26 21:44:47.966 warnZ-Wave device id: 8 failed S2 bootstrapping - KEX_FAIL_KEX_KEY: Key failure indicating that no match exists between requested/granted keys in the network. - the device needs to be excluded then included again to use securely."

[obolove2001]

I have same problem with monoprice motion sensor workes fine on wink but won't send motion to hub on hubitat

[mailtomatte]

I actually got a fibaro double 223 to work right now with community driver... yihaa... will test more..