I thought I would test a conversion from the community "Xiaomi Aqara Mijia Sensors and Switches" to the new supported drivers for presence. Mostly for battery change notification but also for the occation drop off the network.
The community uses "presence" which is a deprecated state for such devices AFAIK;
it only checks every 12 hours
I wanted to switch to testing for Last Message which the ZB status page updates every 3 hours with a ping.
I changes a water sensor over, config and test/rejoin.
However, I don't see that state in the device driver, just "water:"
Can these new drivers provide Last Message?
Do they also report battery, voltage et al as approriate to the device?
They report battery, if they don’t report battery on on the initial join they will if the button is pressed. I haven’t seen the devices that we support fall of the network so haven’t seen the need to poke them as previous drivers did.
1 Like
I don't know why but ever since I solved my "can't join any legacy devices" issue by changing ZB channels I find that on every beta update/reboot I loose functionality of many ZB bulbs.
I have to rejoin them and that mostly solves the issue.
These are Sengled Classic bulbs that used to work flawlessly on the Advanced Zigbee driver and now they either need to be turned off and on a few times after reboot, have a setlevel pushed to them or turn the power off to them for 10-20 minutes and flip it back on again to get life.
I have Groups of these bulbsd and after a reboot only partial bulbs of the groups come on until I sent a setlevel from the Devices page to get them all coming on/off.
It's all a bit weird after 3 years of rock solid.
The hunt continues.
I removed all my Sengled bulbs about a year or so ago. After years of them being perfectly fine, they started falling off my mesh. Hadn't made any big changes to my Zigbee setup, couldn't find any clear clues in logs, etc. IIRC it started back when I was still on the C7.
I wasn't able to troubleshoot my way out of it, never found any smoking (or even slightly warm) gun. They'd just stop responding to commands and would need to be re-joined. Eventually I gave up and replaced them w/Hue bulbs (already had Hue hub and a few Hue bulbs).
Others were also starting to report similar problems w/Sengled at the time, also not finding clear clues as to why, but still others were using them w/zero issues, so def a YMMV thing. 
1 Like
What I am discovering after many scenarios is that WebCore is failing to execute the commands as the optimization says the state for the command is already active so it skips the command.
The state seen by WC is untrue as I can visually watch a bulb or motion sensor activate BUT until I hit Refresh in the Devices tab on that device the true state is not reflected.
I'll bet if I Delete them from HE and join, link to a piston, they might start updating their status.
All 53 ZX devices update just fine, it's this darn ZB, something has changed.
Stay tuned yet again.
Change the settings to 'Disable Command Optimization' for your piston.
I do that for all my pistons to ensure that the command is sent regardless thus bypassing any device state confusion.
Yes I am aware of that fix, thanks 
It's just that I have been doing without that change since invention of WC way back in the ST days.
Everything has always worked and the devices always reflected their current state until a few months ago.
The annoying part is I have a 20-30 Aqara motion and Sengled that are running seamlessly so this is just pi@@ing my brain off. 
PS: Everything that is wrong now was working perfectly 4 months ago.
Even my System Start piston is goofy. It used to turn on all the bulbs and then turn them off so as to reset the state after a power outage.
Now it turns on maybe 1/2 the bulbs and never completes any reset.
1 Like
I appreciate this is a sticking plaster and not a solution. I suppose as it's just something I always do I thought I'd mention it.
Hope you can pin down what is actually going on. It's not always easy as you are well aware.
I removed both the offending device, yet again, and now they update in the Devices page without a Refresh.
Per your suggestion and my PS.
I went to change my System Start piston to your suggestion and found I had already done that. 
Still doesn't operate the bulbs as directed. I do have a 1 minute delay in the piston to give HE/radios a chance to settle in.
So, unfortunatly, I used up one of my "call a friend" lifelines for nothing. 
