Why? These drivers are ridiculously complex, and AFAICT, not supported anymore.
I stopped using the OLL drivers several years ago when I noticed that using them with over ~40 devices made my zigbee mesh very unstable. There were a few others here with similar observations.
Probably becuase you are using outdated and poorly constructed drivers from
here.
I would encourage you to try other drivers to start with.
It would help alot if you could suggest which of the several options (drivers) actually work. I found others had issues with temp readings. I find it interesting that they worked fine for months, now they are bad.
Kind of hard to do without any indication of the exact model numbers of the devices you have.
If you have old (legacy) Mijia and Aqara devices, I would recommend @veeceeoh's drivers. There are also drivers from @chirpy and @birdslikewires for these devices.
If you have newer (zigbee 3.0) Aqara devices, I would strongly recommend @kkossev's drivers.
Those have been working well for my devices. I might have one from veeceeoh, but I seem to remember moving to the chirpy or birdslikewires versions as they were newer and developed on more recent firmware.
I use all of these. I tried
I am clearly not the only one with issues although with different drivers:
I recall why I didn't use a few of the drivers. Receiving this error on the vibration using Chirpy:
2023-08-08 22:56:32.029[error]org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_waytotheweb_Xiaomi_Aqara_Mijia_Sensors_and_Switches_934.recoveryEvent() is applicable for argument types: () values: [] (method recoveryEvent)
(/logs#)2023-08-08 22:54:32.037errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_waytotheweb_Xiaomi_Aqara_Mijia_Sensors_and_Switches_934.recoveryEvent() is applicable for argument types: () values: [] (method recoveryEvent)
2023-08-08 22:52:32.041[error]logs#)org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method:
The driver used has absolutely no effect on whether the device will stay connected to the hub or not. All drivers work the same way - they just decode the messages coming from the devices.
What matters is whether the the Aqara battery-powered sensors are paired via a compatible Zigbee router (repeater) or not.
What mains-powered Zigbee devices you have in your network?
SONOFF S31 Lite 15A Zigbee Smart Plug ETL Certified
Smart Plug,DOGAIN Zigbee Smart Plugs
I have used these both for almost a year in 2 houses without issue. I only replaced the C7 that worked flawlessly with C8 around March 5. Replacement went well and everything has worked fine until 2.3.5.152.
Even the frient smoke detectors have stopped reporting in....
There are a lot of reports that the Sonoff S31 plugs are causing issues with the Zigbee network… But I don’t have any of these and I can’t confirm from my experience.
I will research on Dogain plugs, these seems to be better as repeaters.
Will write a suggestion how to proceed after some hours. But the way to a stable network when using Aqara device is this - pair through a compatible Zigbee repeater.
With the additional range of the C8 isnt it also possible devices that were connecting to the C7 via a router are now direct connecting? I think I remember that being a problem for some people. I know a bunch of work went into Zigbee stuff between .122 and .152 so possibly something in there caused more devices to shift to direct?
Yes, most probably this is what happened- devices that were previously stable connected via a repeater are now connected directly to the C-8 hub.
My C-8 Zigbee radio power level is 8.
Is it possible my ZigBee antennae flaked out? No ZigBee reporting in. My network graph is empty. Kasa and zwave devices appear to be working.
Need to go to bed. Will check in a.m.
ZigBee isn't working at all now. No graph, no activity, not even wall plugs. What now?
Turn off the power of the C-8 hub for a minute or two.
If the power cycling does not bring your Zigbee radio working, it may be a hardware issue, and Hubitat support could probably help checking the engineering logs remotely.
The first thing is to make sure the mains-powered Zigbee devices are reliably working.
FWIW, I have nine of those and they have worked well with my Xiaomi, Aqara, and Mijia devices with my C-3, C-7, C-8 hubs all on current firmware.
You can also swap the two external antennas - they are dual-band fully interchangeable.
Any idea why I can no longer be able to disable any of my apps? I used to be able to for both the button controller and rule machine. Now, I can only stop the rules but not the button controller.
If you click on the 'X' (highlighted in the screenshot below) at the top of your apps list, you should be given checkboxes to disable any app.
Please start a new thread. This one is focused on a zigbee issue experienced by @goldbond1’s hub.
Download the Hubitat app
