I'm running a C7 (2.2.5.131) but it appears although I'm having issues with my zigbee devices.
I've tried swapping the channel and its not made any improvement, the issues are:
Devices stop reporting after a few hours (or even minutes)
SmartThings (Centralite 3200-SGB) plugs stop reporting and being able to be reported on (I have 10 of these, to improve my mesh)
If I rejoin (just do a quick reset on the plug) and it starts being able to be controlled again for a short while, but doesnt even report power usage - even if the options are enabled and set to 1w). just reports as 0 all the time
Toggling the on/off of a plug on the dashboard doesnt do anything to the 'dead' devices.
All the plugs are using the Generic Zigbee Outlet device type
All Z-Wave devices are rock solid
Anyone got any ideas on what I can try, its almost like the zigbee devices are going to sleep and then refuse to wake up. I would have thought the plugs would be 100%, since their mains powered and should be repeaters themselves.
One example plug:
Reset this about an hour ago, its sat about 10 ft away from the hub and its stopped reporting
Time now is 12:41 - so should surely have responded in the past 5 minutes (esp since the power reporting is set to 1 second and it currently has a camera plugged into it)
Only about 4-5 hours ago, but I wouldnt expect devices to go dead after minutes....I can leave it 24 hours as suggested but seems to be displaying the same symptoms on channel 20 as it was on 12.
Its just annoying that some of my key motion sensors are zigbee so lights are getting stuck on because the motion sensors are stuck at active.
Only this plug, or all 10? As a test, I would back off on the power reporting frequency, enable logging for all plugs, and watch the live logging to verify it isn't a just a case of the mesh getting overwhelmed.
Re-pair each of your 10 outlets very close to the Hubitat. Make sure that the device page on all of them looks the same. Then move them to their final location. Then give 24 hours for the mesh to settle down.
I think there is a problem with the Generic Outlet Driver, @aaiyar. See posts starting here
Note that in my researching threads here, I've found several similar posts by others so this appears to be becoming a common zigbee problem. As best as I can determine, it happened around v2.2.4 but I can't say for sure.
Confirmed they're all listed as "Generic Zigee Outlet" but do display differently.
Removing and readding them isnt a trivial thing - so going to do that as a last resort.
@rcjordan that does look very similar, but because they're not reporting properly they arent routing ZigBee messages for my battery devices correctly....I guess I will read through the thread but looks like its something which needs fixing by the Hubitat staff in an update.
@kraegd you won't need to read that entire thread, but I think there are one or two post upstream in it that the @bptworld pointed to a driver problem. I have flagged staff already, maybe @aaiyar will check this out, too, and see if he thinks this is indeed a driver problem.
I'd agree with an issue with that driver, I'm not sure how Hubitat handles a device type thats incorrect.
If you have a mains powered ZigBee device will it route messages in the mesh, if its not the correct device type on the hub itself? Or is it intelligent enough to route around it - I dont know if its the device or the hub which negates the mesh.
For example, if I randomly unplug a mains device then my battery devices should go into panic mode and reroute. But if that mains device is just screwed but still 'online', i'd guess the battery device would just keep trying to push messages to it - which the hub wont receive....that'd explain a lot.
Also would switching from the ZigBee Outlet to ZigBee Switch get rid of power reporting? Would is also screw over any routing of messages since its a swap of the driver type - would Hubitat use it for routing messages or not (one of the main reasons I have these plugs is to improve my mesh)
the driver used for a device has no bearing on that devices routing capabilities.
not reporting properly?, how is this determination being made?
If you can turn the device on and off via the driver details, and the device current states are updating, then the device is reporting properly.
lastActivity times aren't always going to be a good indicator of device status, that's just the way that is right now.
If the zigbee device can't be controlled via the driver UI, factory reset the device (do not delete it in hubitat), then rediscover it, if it can't be discovered in place, then its too far from another repeater or the hub...
Not sure what the ADT monitoring has to do with ZigBee - from what I'm aware, the Centralite/SmartThings devices do follow standard ZigBee HA.
I dont believe the ADT Monitoring supports any plugs anyway - its for contact/motion sensors. The plugs wouldnt give an alarm company any useful information?
