I have 2 of the A5's in my table. The device that has it seems to change every now and then, usually the battery powered ones.
I tried to add all my powered devices of which I have I have 16 it went to complete s**t on the last device 
going to add them back to ST and use for HubConnect for the time being
Gotcha, well I’m happy to not be the only one. I can pair my devices at the hub, and no A5 shows up ( after repair, reboot ) and the device works as intended. ( open closed reg immediately ) I move the device 18 feet diagonally away. Do a repair, A5 joins the mix and the device is no longer working. Open / close do nothing. A5 only shows up with Dome Leak, Aeotec recessed DW series 7. I have a bunch of other battery devices and they never.
Weird.
It is slowing improving I will give it another hour before I remove them
I see nothing in zwave log is that normal?
You have to open the logs in another window to see live. Mine doesn’t show any logs on that page either.
All mine are back on ST and back on Hubitat using HubConnect I might move ZigBee over instead
Add me to the list of phantom A5 routing.
I had a couple of TKB TZ88E which were working last night and could be controlled on and off.
This morning they are routed through the phantom A5 and can't be controlled.
I'm actually running 2.2.3.119 with the latest z-wave firmware.
Yeah, I have my 2 Linear/GoControl WADWAZ-1 Contact Switches battery operated and they are not working reliably and losing events... They used to work flawlessly in smartthings and ST hub was way worse located... Now Im also observing the A5 routing. Since I'm in Hubitat for 2 days now, I'm not sure if's a range thing, bug... Because I've put new batteries and that shouldn't be an issue...
interesting i though it was only me. when my hub was hosed before going back to 2.2.2 i had the A5 node and everything routing through it for the mosst part.. Maybe this is the issue some ghostly A5 node cooked in the firmware somwhere
Just to point out the obvious, not only is A5 greater than any Z-Wave ID that you probably have, it’s also an alternating one/zero pattern (10100101), perhaps something in the new Z-Wave radio is oscillating? Or something loses and regains sync? Just a thought, I’m sure Mike Maxwell has already pursued that Avenue. After all, Hubitat is the first controller, I believe, to use the 700 chip, and the new protocol stack might have some issues. It’s so fun to be on the bleeding edge - lots of blood here.
1 Like
I have the same issue. New Hubitat user, added my devices according to distance from the hub, but 8 devices show routing through the A5 node. I was a smartthings user before as well.
Hopefully this can be rectified soon.
I also posted under this other thread that should be combined into this one.
Unknown Z-wave devices
Also seeing this and unable to remove failed devices.
What firmware version are you running? There was an update released today to fix many of these issues:
I installed the .2.132 and my network is worse than before. Now everything routes through A5, a repair says “busy” or “failed do communicate” it can’t delete routes. I had some issues so I did a shut down, no power for 10 min and restarted and when it restarted, every single Zwave device shows routing through A5 and now nothing works.
I await the hot hot fix, hot fix fix.
1 Like
Pretty much same, latest firmware, and many devices showing A5, and I'm unable to exclude as well, having to factory reset most devices
@dcd722 If you haven't already before doing drastic things like resetting devices first try to shutdown the hub (not reboot), and pull the power for 30s to fully reset the radio and all things that don't power down on a reboot.
It might not help (obviously didn't for @ourmessages), but if things are 'gummed up' it very well might help.
I will say this firmware (2.2.3.132) update doesn't fix everything for everyone. But it did make it better for many, Hopefully your specific issues will get nailed next!
1 Like
Could I make a simple request that posters stop using the phrase "latest firmware" and instead provide the firmware version that they have installed? Days and months after their post is made, when I (or others) search through these threads for problems that have been solved, or problems that were caused, by certain versions of firmware, it's very difficult to figure out exactly the configuration that caused or fixed the issue if the firmware is described only as "latest". Thanks so much.
3 Likes
Thanks, I did try that, and things are definitely better for my Inovelli Fan+Light switches, looks like the Red Series Dimmers are screwed up joining S2, but now I can't remove all the SmartStart entries that seem to have duplicated. Might try a rollback
Here is my first device page, the subsequent pages all have everything going through A5 as I said above. Once it routes through A5 the device is no longer accessible. The prior firmware seemed to lose a few A5 device routes overnight, I’ll see where the overnight cleanup leads.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
