Internal. No luck yet on the shut down and remove power trick, but it only just powered back up.
C5 has the internal radio (US version).
I was following your thread, seems just a little different than my issue, but maybe something similar underlying our problems. I don't see anything from Z-Wave devices in logs (at least not yet). Oh well, I can always bring the C5 back up.
You, sir, are like a superhero. Well said... 
1 Like
I can actually see the paddle up/down and energy monitoring on switches coming in.
1 Like
Left it alone for a couple hours. Nothing in logs over that time for me.
For a lark I tried to disable Z-Wave. Then after Enable, nothing came back. Not really sure what that means, but I don't think that is expected behavior.
Yeah. That may be a bit different. It’s strange, I can control my Inovelli Light Bulbs just fine, but my Inovelli light switches report energy readings and physical switch changes, but via Hubitat, I cannot control them or repair them. Z-Wave updater cannot see them. So, like I said, seems like they can talk to the hub, but the hub cannot talk to them.
In device edit, under Device Details in the Data field i see an entry for zwNodeInfo on the C8 Pro, but not on the C5. All the other entries in Data are the same. I checked a few other devices on the C5 and none have zwNodeInfo. They all work fine on the C5. Anyone know the importance of that data field, and if there is another way to find it on the C5? Or is the C8 Pro just creating something which it needs but didn't exist on the C5?
Image from the C8 Pro-
A reboot, or a shut down, pull power, restore power, restart will bring your devices back after a Disable \ Enable. Happened to me as well.
zwNodeInfo is something that gets automatically saved by the hub, not sure what it is for but its not important so don't worry about it. It can be deleted and the devices still work so its not critical for device communication.
If all the usual tricks are not working I am suspecting something with the migration has failed internally for whatever reason and no amount of prodding will make it work. Something the devs will have to figure out.
Also FYI 2.3.8.118 is public now, not beta. It sounds like you had BOTH hubs on that platform doing the migration? If so, and its not working, you will probably have to wait for devs to figure something out.
Thanks, I'll take a look for that
That was my guess, just thought I'd ask rather than assume I knew everything about this thing.
I have just attempted to migrate with 2.3.8.119. Same result as 2.3.8.118 as outlined in my previous post. In short, devices appear in Z-Wave details, but none of the devices work and I can't simply Repair, Refresh, or Replace the device to get it working (all fail).
I'd suggest you send your hub's UID (Settings>Hub Details) to @bcopeland along w/a short summary of the issues you're seeing for him to investigate any details in your engineering logs.
Was there ever a resolution to this ? I ordered a new C8 Pro and intend to put it in a mesh with my existing C8. But my thought was to migrate the almost 200 devices and many apps to the C8 Pro so it becomes my primary. Then reset the C8 and start new, putting some new devices and migrating some as appropriate. But I don't want to do this if I'll be wresting with migration. I could just add the C8 Pro and start adding new devices to it. Not having real performance challenges on the C8, but occasionally get elevated alters.
Afraid it isn't fully resolved for me. Good news, I seem to be a strange case. From what I've seen looking for a solution, I'd bet you have a good chance to migrate. I'm still waiting to do things manually, hoping the development team finds something in my logs which might lead to a solution.
Did you submit a warranty case in the Support portal?
I would say that from what I see on these forums, that is correct. There seems to be a few people with issues, but it isn't widespread or on every single hub.
Yep. Migrated this morning, and so far it appears (knock wood) it was as smooth as butter. I'll wait a bit before restarting and resetting the original hub to begin configuring it for a send hub. Any gotchas to watch for in doing that ? I noted the Zigbee channel change requirement.
Yes for sure wait a week at least just in case you need to emergency go back to the old hub. Then you can use the diagnostics tool to do a full reset. I forget if the Full reset warns you about breaking subscriptions. If thats an issue then you can do both radios and a soft reset instead.
Yes make sure if using Zigbee to put it on a separate channel from the other hub.
