Well, it seems it was a Hub Connect issue. (You were right yet again!)
After trying a few things, I found that there was an issue with the connection. (Maybe caused by my incorrectly programmed drivers?) It works after it is reset. I'm just hoping it continues working.
That is the one thing that bugs me about having to have those sensors on a second hub, if there are issues, it can take quite a bit of time to figure out the source (device, hub connect, something else...). It does make it more interesting though!
Yes, it doesn't really make things easier. I have multiple hubs, but keep most rules/automations local to where the device is. I don't use HubConnect or the like.
I'm surprised you're able to do that. You must be a really good architect/planner...
I find that I have too many devices that need to cross over from one hub to another... Echo Speaks being a big one! I have automations that tell us to close the windows if AC is on, or to keep an eye on the weather if certain windows are open and the weather is predicting rain, etc... And a lot of the time it needs to poll devices status on both hubs.
Not so much, I don't live in a house and don't use any voice assistants, if I did either I don't think it would be possible. For Tasmota devices I can control them from all hubs, just not get instant status updates on more than one. For the rest it can be separated.
I don't have one of those and wasn't even aware people used it? I've also never seen it in my local Aqara store nor from any of the online stores I buy from. As such it is not really on my list of drivers to write, but if someone finds a way to have one sent to me here in China I'll write a driver. Shouldn't take more than 1 hour or so. I currently only have the Xiaomi Gas Sensor left on my list of Xiaomi/Aqara devices to write a driver for.
Try my Aqara Wall Switch driver, they might work with these. Didn't realize it, but went through debug logs for that device a while back, test it and see if it works as expected, otherwise some minor tweaks might be needed.
I think I found the problem, all my other zigbee devices had the "Enable Last Checkin Date" ON except for this one sensor, when I changed it the sensor stayed present.
Is the the presence attribute direct linked to the "Last Checkin Date"?
Hi @markus
I have a temp/humisity sensor that is working just fine.
The only thing is I keep seeing this in my logs. dev:27552020-07-27 19:09:55.284 warnEvent interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
dev:27552020-07-27 19:09:55.261 warnOne or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 2 (maximum expected 1)
--- Live Log Started, waiting for events ---
When I look in the events for the device I can see that it is reporting in OK.
Not sure what to make of it.
Yes, either Last Checkin Date and/or Last Checkin Epoch needs to be enabled. These are the timestamps used to determine presence. The description of Enable Presence mentions this as a requirement for the feature to work.
It looks like you have entered Forced Recovery mode and not left it. Could have happened if you were on one Beta driver and switched to another with it running, there was a rename of some schedules recently. Take a screenshot of your scheduled events on that device (in case the issue is another one) and then run the "Force Recovery Mode" with minutes set to 0 and this should be sorted.
Thank you for reporting, there is no harm in these messages, but I've added a filter for them for the next release.
No On/Off buttons? That sounds strange, they are there as long as the correct driver is selected. Please provide a screenshot.
@mwboudro It helps. It does tell me that it doesn't seem to use any of the Aqara-specific clusters. Please try a new Beta driver I just uploaded here. After switching to this driver, run the Initialize command on the device page.
Actually this makes sense. I did use forced recovery mode mode but put in "1" as I just assumed it needed a figure. This ties in with the logs.
Did as you suggested and now it is OK.
Thanks for your help and of course, your fantastic apps/drivers.
I may have missed it but do you have a "donation" page?
I'm using your drivers exclusively when I can.
Thanks for offering Living in China I don't really have any good options for that. Paypal doesn't allow donation pages for China-based accounts. I don't know of any other services that do either. With that said I haven't really given it much thought until recently, it came up regarding a device and since it is very difficult to send devices here I did accept a payment through Paypal to cover me purchasing a specific device here in China. I'm doing this for fun and if someone wants a specific device implemented which I don't have that might be a good reason for a donation, if it can be purchased here in China that is. Not everything on AliExpress exists domestically. For these instances a payment to my Paypal can work even though I don't have a donation page.
Happy you like them! When I initially wrote them I wasn't so sure they would be liked since I don't conform to "HE standards".
On a different note: If someone has a Hue Bridge v2 they don't need and want to ship it to China (probably not possible/easy from USA) I'd be happy to receive it, what I find here seems to be some strange locked-down version without local API
Thanks @markus, I did that. Here's a snapshot of the device page. It looks as if it's initialized, but still no buttons to actually control the device.