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:
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:
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.
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.
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!
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.
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..
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.
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.
[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
In my C-7 setup (see previous post with screencap of details page) The Zooz switches do not seem to be repeating very well. GE Enbrighten switches are taking precedent. I wonder if it has anything with me pairing everything unsecured?
I had an inclusion issue yesterday where I added GE Enbrighten switch and it came up as a Zooz switch! After changing back to Enbrighten it was fine but the code the assigns the driver seemed to get confused with the other stuff I added (or maybe it cached some failed inclusion info dunno).... strange.
I had something similar happen to me the other day. On the new non-S2 device you might want to look at the device details -> Data section and see what it says.
In my case it had the info for the previously paired S2 device, and indicated it was paired securely (in reality it was not, the device in question doesn't support any security levels). It also had the inClusters for the previous device, too.
That's weird too - everything I'm pairing is S2 capable but I am including as unsecured right now. Trying not to make it more complicated than I have to.
The pairing process seems to retain info from previous inclusions (if they failed I wonder?)
Zooz has been iffy on repeating end of things but the Enbrighten stuff just seems to work.
I think that is the case - and not only when it outright fails. I saw it too when the pairing process didn't fully complete and the device was partially paired (in zwave details, but with no clusters - waiting to be discovered and finish the pairing).
It was really easy for me to see on my dev hub (as it said a non-secure device was S2 and the inClusters were all wrong).
I'll see if I can figure out how to reproduce it. Seems tricky though as when I saw it happen it was after an S2 pairing didn't 100% complete, so I need to get that to happen again.
Yeah mine (enbrighten) just id'd as Zooz.. didnt think to check the cluster info but since both were unsecured and was able to switch out. wasnt paying all that much attention to it.
I am having trouble getting an Aeotec Window Sensor 6 to pair and show a status (open/Close) It shows the battery level. I have others that work correctly but not this one.
I joined it several times, did factory resets no open/closed. I rejoined it to my ST and it showed open closed. I am running a C7 V 142. Any ideas, other than the trash....
It seems like I've seen a number of posts about Aeotec "6" devices having trouble. Wondering if there is a general class issue w/the Aeotec devices that results from something in their drivers, or how HE inclusion sees them.
I think Aeon's product line is "7" for the 700 series chip and "gen5" for the 500 series chip. The only "6" I know of in their product catalogue is the MultiSensor 6.. where 6 means the number of sensors in the one product. It's a "gen 5" device though.
For ME, Aeon has Joined the C-7 easily, especially since Aeon has many products that use single vs double click to determine unsecured vs secured joining.
It's not supposed to.. Will have to investigate this .
