C-7 Driver Issues

🛎️ Get Help
21

Me too. I've had a response from the guy who wrote the driver saying there may have been a fix in the latest update as it appears to be working now.
Dragged one of my out of my goodies drawer and it paired as a Fibaro Switch.
Changed it to the 223 driver.
The only thing for me was that it took a while for the 2 child devices to be defined.
I'm not sure what did it but they did appear eventually. Maybe 15 minutes later.
Could control the 2 switches OK and state change was also updated correctly.
I wonder what has changed but I suppose all that matters is they work now.

Unfortunately I bought 4 Qubino devices to replace these as the Fibaros were controlling the exhaust fans in my bathroom and EN Suite and my curtains. Couldn't wait for a fix.
Hey ho. I now have some devices to use to automate more things.
Where to start????? :thinking:

22

Time to investigate implants for the kids!? :slight_smile:

You: "Alexa, tell Michael to go to his room and do his homework."
Alexa: "Michael, go do your homework or I'll give you a shock you will not forget."
[Michael runs to bedroom]
You: "Honey, let's enjoy some wine and cheese..."

3 Likes
23

aha ok... but I also just included a qubino 2 relay and it worked!!!! but in dashboard meny the childs got double and the parent that I gave a name dont have child in dashboard but in device meny it has ... strange but now it works..... things are going the right direction ping @bcopeland

Skärmavbild 2020-08-27 kl. 20.28.21
Skärmavbild 2020-08-27 kl. 20.28.21640×642 39.4 KB
Skärmavbild 2020-08-27 kl. 20.28.12
Skärmavbild 2020-08-27 kl. 20.28.12534×602 27.3 KB
Skärmavbild 2020-08-27 kl. 20.27.19
Skärmavbild 2020-08-27 kl. 20.27.192194×556 87.2 KB

24

"EVA Logik Smart Plug" driver does not work when device is paired S2 Unauthenticated. Pairs as "device", manually switching the driver does not create the child devices as expected, so device dcoes not work.

Driver works fine when paired non-secure though.

25

Zooz ZEN20 Power strip. I can't get any of the reporting preferences to show securely or non-securely. Plus the other items listed above for the device.

26

@bcopeland

the Aeotec Siren 6 does not get recognized correctly in the C7, event if a chnage the driver there is no way to add the Aeotec Siren 6 Component Chime like in my good old C4. This child devices was created automatically

Inclusion logs:
dev:2312020-08-28 12:49:21.145 pm debugparse:zw device: 24, command: 7006, payload: 05 04 02 00 00 01 , isMulticast: false
dev:2312020-08-28 12:49:20.721 pm debugparse:zw device: 24, command: 7006, payload: 02 04 01 00 00 01 , isMulticast: false
dev:2312020-08-28 12:49:19.842 pm debugDevice Specific Report - DeviceIdType: 1, DeviceIdFormat: 1, Data: [12, 0, 1, 0, 1, 1, 9, 2, 5, 0, 0, 3, 0, 5, 9, 0, 0, 0, 0]
dev:2312020-08-28 12:49:19.820 pm debugparse:zw device: 24, command: 7207, payload: 01 33 0C 00 01 00 01 01 09 02 05 00 00 03 00 05 09 00 00 00 00 , isMulticast: false

image
image1134×801 37.2 KB

27

Just another data point - My Aeotec Siren 6 (paired S2 Authenticated) is working fine on my C-7.

image
image935×188 19.7 KB

:man_shrugging:

28

Thanks for the info, this is really strange I have done the process 3 times (using the pin code under the siren) with the same result.

29

Agreed, that is odd. I did pair that device back on 2.2.2.118 firmware I think, in case it is relevant. I have not tried to pair it again since.

30

It could be that, I am running on 2.2.3.135

31

Nanoleaf stuck on “sending” ... have another thread open I’m slowly working around the problems.

32

Schlage Z-Wave Locks.

Using the built-in BE468/BE469 driver. It seems that it is not reporting the battery level. Has been 2 days since installation and shows all the current states as on a C-4 except for battery.

33

Mine has been reporting at 100, so hard to tell if that's correct, or bogus. I did replace the batteries very recently before I move it over from ST, so it could actually be correct...

34

@bcopeland
Just updated to the 2.2.3.142 and my Aeotec Siren 6 is still not getting discovered correctly :frowning:

image
image726×453 20.3 KB

image
image958×284 22.5 KB

dev:4862020-08-31 08:52:47.962 pm debugparse:zw device: 38, command: 7006, payload: 05 04 02 00 00 01 , isMulticast: false
dev:4862020-08-31 08:52:47.749 pm debugparse:zw device: 38, command: 7006, payload: 02 04 01 00 00 01 , isMulticast: false
dev:4862020-08-31 08:52:47.402 pm debugAssociation Report - Group: 1, Nodes: [01]
dev:4862020-08-31 08:52:47.385 pm debugparse:zw device: 38, command: 8503, payload: 01 05 00 01 , isMulticast: false
dev:4862020-08-31 08:52:46.792 pm debugDevice Specific Report - DeviceIdType: 1, DeviceIdFormat: 1, Data: [12, 0, 1, 0, 1, 1, 9, 2, 5, 0, 0, 3, 0, 5, 9, 0, 0, 0, 0]
dev:4862020-08-31 08:52:46.772 pm debugparse:zw device: 38, command: 7207, payload: 01 33 0C 00 01 00 01 01 09 02 05 00 00 03 00 05 09 00 00 00 00 , isMulticast: false
dev:4862020-08-31 08:52:46.440 pm debugVersion2 Report - FirmwareVersion: 1.4, ProtocolVersion: 5.3, HardwareVersion: 164
dev:4862020-08-31 08:52:46.433 pm debugparse:zw device: 38, command: 8612, payload: 03 05 03 01 04 A4 00 , isMulticast: false
sys:12020-08-31 08:52:42.249 pm warnZ-Wave Inclusion timed out, status:7
35

I reported this on another thread but thought it might be good here as well..

On .142 - only my GE Enbrighten Switch shows a route, the others - Zooz Zen 23/24s v3 (I think) all with the Zooz Central Scene Switch & Dimmer drivers. I get this:

nr154
nr1543331×1775 306 KB

Repairing/Refreshing an individual node does not seem to do anything. However I changed the "Main Floor Back Hall" Dimmer (006) to "Generic Z-Wave Smart Dimmer" and now get this:

nr157
nr1573395×1753 365 KB

Dunno if a UI bug or a driver issue so thought I'd report it here. On .135 the reporting worked but included the mystery A5 device..

clarification: The other non Enbrighten switches/dimmers drivers are all still set to "Zooz Central Scene" except 006.

1 Like
36

For giggles I tried to change another device "Main Floor Foyer Light" to generic.. saved then hit config and I got a pending changes message in the logs. Tried hitting the "save" button for that device again but no additional messages showed up. I then changed the "Main Back Hall Switch" back to "Zooz Central.." saved and hit configure.. in the logs got another message about pending changes appeared and to hit the "save" again which I did for that device. Nothing else appeared in the logs (not even configure messages I did for each driver change) other than the pending changes so not sure if anything happened. Also no new routing information on details page.

Here are the logs of the above actions:

nr158
nr1581275×763 103 KB

37

Apologize on posting 3 times in a row but have to mention.. the "Main Floor Back Foyer Light" is now showing a route after the change. Everything seems to be routing through the Enbrighten switch (0C)... kinda weird as it was the only one showing a route originally. All devices are less than 20 ft away.

nr159
nr1593367×1423 323 KB

The act of changing drivers + configure seems to have had an effect. Even the original device which I restored back to "Zooz Central Scene Dimmer" is still showing a route. Wonder if I should do that with all my non-Enbrighten devices.

edit: for giggles tried to mess with the back pantry switch (OA) - in this case left the driver alone and just hit "save" then "configure". Got a "There are 4 pending changes pending. please click Save again" in logs.. hit save device and am waiting for something to happen.

Note: I just realized after routing through C0 all devices also route through 0A.. 0A itself doesnt show up in the routing column. Again not sure if this is a UI bug or not. Also not sure why the devices less than 20 ft away have to go through 2 hops to get to the hub..happy with the reported speed though! :smile:

Edit2: Nothing happened on the Details page this time - no routing info. Then I hit "refresh" button on device "0A" and now got a "Z-Wave Network responded with Busy message".... still on generic zwave smart switch driver.

nr160
nr1601387×883 144 KB

edit3: and now 0A is showing a route.... and it looks like 06 has figured out it is in fact close enough to the hub.. so things are adapting. This only happened after I started changing the Zooz drivers to generic (and 06 I changed back!). - I'm insane please ignore that last bit.. :crazy_face:

nr161
nr1613347×1429 326 KB

edit4: I just realized that the "Back Porch Heater" is also an Enbrighten switch and it was not showing a route but now is... this is very strange. Everybody likes to route through the GE stuff apparently.

38

So I have no trouble going from Zooz Central Scene drivers to Generic Smart Drivers for both switches and dimmers. I save the devices as generic then press configure. All is well. When I switch back to the Zooz driver and do the same (save then configure) I get a that "pending... " message and then I click the "save device" button again.

Why is it doing this?

39

I think @bcopeland will find this very interesting...

40

Hope we can get the driver fixed by the next version, below you can see the logs and details of the discovery of the same device but on a C4 Hub.

image
image997×264 17.3 KB

Log from C4 disvovery 
[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:45.937 am [debug](http://192.168.1.5/device/edit/1313)MultiChannelAssociationReport(groupingIdentifier:3, maxNodesSupported:5, reportsToFollow:0, nodeId:[1], multiChannelNodeIds:[[nodeId:1, bitAddress:0, endPointId:2]])

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:45.458 am [debug](http://192.168.1.5/device/edit/1313)MultiChannelAssociationReport(groupingIdentifier:9, maxNodesSupported:5, reportsToFollow:0, nodeId:[1], multiChannelNodeIds:[[nodeId:1, bitAddress:0, endPointId:8]])

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:45.101 am [debug](http://192.168.1.5/device/edit/1313)Strobe(#22) = 257

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:45.032 am [debug](http://192.168.1.5/device/edit/1313)Flash Fast(#21) = 1285

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:44.975 am [debug](http://192.168.1.5/device/edit/1313)Flash Slow(#20) = 2570

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:44.831 am [debug](http://192.168.1.5/device/edit/1313)Pulse Fast(#19) = 842138885

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:44.759 am [debug](http://192.168.1.5/device/edit/1313)Pulse Slow(#18) = 2139030026

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:44.676 am [debug](http://192.168.1.5/device/edit/1313)On(#17) = 65280

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:44.574 am [debug](http://192.168.1.5/device/edit/1313)Off(#16) = 255

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:44.510 am [debug](http://192.168.1.5/device/edit/1313)Silence Alarm with Action Button(#96) = 0

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:40.306 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Strobe(#22) from '257' to '257'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:40.297 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Flash Fast(#21) from '1285' to '1285'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:40.292 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Flash Slow(#20) from '2570' to '2570'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:40.284 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Pulse Fast(#19) from '842138885' to '842138885'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:40.277 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Pulse Slow(#18) from '2139030026' to '2139030026'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:40.272 am [debug](http://192.168.1.5/device/edit/1313)CHANGING On(#17) from '65280' to '65280'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:40.264 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Off(#16) from '255' to '255'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:40.256 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Silence Alarm with Action Button(#96) from '0' to '0'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:40.161 am [debug](http://192.168.1.5/device/edit/1313)configure()...

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:36.755 am [debug](http://192.168.1.5/device/edit/1313)MultiChannelAssociationReport(groupingIdentifier:3, maxNodesSupported:5, reportsToFollow:0, nodeId:[1], multiChannelNodeIds:[[nodeId:1, bitAddress:0, endPointId:2]])

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:36.293 am [debug](http://192.168.1.5/device/edit/1313)MultiChannelAssociationReport(groupingIdentifier:9, maxNodesSupported:5, reportsToFollow:0, nodeId:[1], multiChannelNodeIds:[[nodeId:1, bitAddress:0, endPointId:8]])

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:35.792 am [debug](http://192.168.1.5/device/edit/1313)Strobe(#22) = 257

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:35.295 am [debug](http://192.168.1.5/device/edit/1313)Flash Fast(#21) = 1285

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:34.712 am [debug](http://192.168.1.5/device/edit/1313)Flash Slow(#20) = 2570

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:34.244 am [debug](http://192.168.1.5/device/edit/1313)Pulse Fast(#19) = 842138885

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:33.704 am [debug](http://192.168.1.5/device/edit/1313)Pulse Slow(#18) = 2139030026

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:33.177 am [debug](http://192.168.1.5/device/edit/1313)On(#17) = 65280

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:32.668 am [debug](http://192.168.1.5/device/edit/1313)Off(#16) = 255

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:32.185 am [debug](http://192.168.1.5/device/edit/1313)Silence Alarm with Action Button(#96) = 0

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:31.743 am [debug](http://192.168.1.5/device/edit/1313)Firmware: 1.4

[sys:1](http://192.168.1.5/logs#sys1)2020-09-02 11:47:31.056 am infoZ-Wave Discovery Stopped

[sys:1](http://192.168.1.5/logs#sys1)2020-09-02 11:47:31.053 am infoZ-Wave Device Discovered: Aeotec Siren 6

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.982 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Strobe(#22) from 'null' to '257'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.966 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Flash Fast(#21) from 'null' to '1285'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.962 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Flash Slow(#20) from 'null' to '2570'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.941 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Pulse Fast(#19) from 'null' to '842138885'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.938 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Pulse Slow(#18) from 'null' to '2139030026'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.936 am [debug](http://192.168.1.5/device/edit/1313)CHANGING On(#17) from 'null' to '65280'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.928 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Off(#16) from 'null' to '255'

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.817 am [debug](http://192.168.1.5/device/edit/1313)CHANGING Silence Alarm with Action Button(#96) from 'null' to '0'

[dev:1314](http://192.168.1.5/logs#dev1314)2020-09-02 11:47:30.669 am [info](http://192.168.1.5/device/edit/1314)Aeotec Siren 6 - Chime mute is unmuted

[dev:1314](http://192.168.1.5/logs#dev1314)2020-09-02 11:47:30.661 am [debug](http://192.168.1.5/device/edit/1314)unmute()...

[dev:1314](http://192.168.1.5/logs#dev1314)2020-09-02 11:47:30.646 am [info](http://192.168.1.5/device/edit/1314)Aeotec Siren 6 - Chime volume is 10%

[dev:1314](http://192.168.1.5/logs#dev1314)2020-09-02 11:47:30.626 am [debug](http://192.168.1.5/device/edit/1314)setVolume(10)...

[dev:1314](http://192.168.1.5/logs#dev1314)2020-09-02 11:47:30.520 am [warn](http://192.168.1.5/device/edit/1314)installed...

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.258 am [warn](http://192.168.1.5/device/edit/1313)Creating Chime Component Device

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.221 am [info](http://192.168.1.5/device/edit/1313)Aeotec Siren 6 volume is 50%

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.201 am [debug](http://192.168.1.5/device/edit/1313)setVolume(50)...

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.198 am [info](http://192.168.1.5/device/edit/1313)Aeotec Siren 6 mute is unmuted

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.195 am [debug](http://192.168.1.5/device/edit/1313)unmute()...

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.177 am [debug](http://192.168.1.5/device/edit/1313)configure()...

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.120 am [info](http://192.168.1.5/device/edit/1313)Aeotec Siren 6 volume is 50%

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.117 am [debug](http://192.168.1.5/device/edit/1313)setVolume(50)...

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.103 am [info](http://192.168.1.5/device/edit/1313)Aeotec Siren 6 mute is unmuted

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.100 am [debug](http://192.168.1.5/device/edit/1313)unmute()...

[dev:1313](http://192.168.1.5/logs#dev1313)2020-09-02 11:47:30.066 am [warn](http://192.168.1.5/device/edit/1313)installed...

[sys:1](http://192.168.1.5/logs#sys1)2020-09-02 11:46:53.884 am infoInitializing Z-Wave Device : 48