I have a couple of Third Reality Zigbee contact sensors I've been using for a long time with C-7. Yesterday I migrated to C-8 and some of them suddenly dropped their battery reading from 90%+ to 30~40%. The batteries were recently changed and reading at 1.55V+ so definitely still has a lot of juice. Just to be sure I grabbed a completely fresh set of batteries and popped those in, only to find the reading at 50%. The only thing I'm getting from the generic driver is state variable lastBattery : 1691350838.
Removing and re-including does not fix this. Again these sensors were reading just fine with C-7.
Whenever I mess with my Zooz battery sensors, the battery always plummets down in the 20s (even with a brand-new battery), but then it recovers on its own within a day. Perhaps something similar with your 3R sensor here.
I also found 1/3 of my zigbee shades don't work right after migrating to C8. Like when I use RF remote to control them they'd send their status to the hub but when I try to control the position from the hub nothing happens.
Basically lots of problem with zigbee. End up having to remove then re-pair those shades.
There can be a number of factors that can contribute to differences in the experience in moving devices like you have, and by that I'm not meaning you have done anything wrong, just by it's very nature, there can be differences in the performance.
Given that Zigbee is a mesh network, communication with a device can at times rely not only on the hub and the device, but can be influenced by the route the communications take and therefore the quality of any devices in between. If you move a device from one mesh to another it can (I believe) take some time for the optimal path to be identified, to @hydro311 's point about waiting. Also, with different devices involved in the two networks, the quality of the communications within the two mesh networks may vary, so it may not be the fault of the hub or the device being moved.
Equally, Zigbee can also be susceptible to interference from other Zigbee networks and Wi-Fi networks, so the channel and other settings on each network and surrounding networks can also impact communications. One network may be operating on a channel or with things like a power setting which means it is not impacted in this way, whereas another network has settings that mean it experiences interference.
None of that makes it less frustrating, but hopefully it may give you some areas to look at and I'd encourage you to come onto the Community and work through the issues you are having, there's going to be others here who have had either a similar or the same issue before and are happy to help.
On the subject of battery reporting: is the battery percentage number reported by the device itself or computed in some way by Hubitat driver? Since the contact sensor is reporting 50% on C8 and 100% on C7 for a fresh set of AAA, I thought the value may be different due to driver difference. If it's the definitive value reported by the device then I'd have to take a closer look at the sensors, perhaps replacing them.
this depends on the device for the most part.
with Zigbee devices some only report voltage, some only percentage, some both.
For a given device and driver combination there wouldn't be any difference in reporting between a C7 and a C8
