Is that a community driver? There are a few other community drivers like that.
The way I deal with this is with an app that takes one (or more) real sensor as input and sets a virtual sensor as output, to be used in automations. The app can apply whatever heuristics one wants. Kind of like a mirror, but with additional logic in between Could be done with RM, too.
1 Like
Well, this is exactly what I just did in Rule Machine. It's sorta drives me nuts that now I have several rules firing off and virtual devices doing things every time any door is opened or closed, but I guess it's a solution until I learn how to make my own drivers...
Yes
The way I deal with this - is to use only trusted and reliable sensors.
1 Like
Hopefully yes.
In the past I have had sensors 'stuck' in an active state when the batteries get low.
I have pistons that monitor my motion sensors and if they remain active for 30 minutes, I reset them to inactive, send a notification to me and then I can check them and change the battery if needed.
So yes, an incredibly 'useful fix'.
It stops lights etc. from staying permanently on.
Mine have been bulletproof for almost 5 years. It's not until I had to switch to built in drivers that the problems arise, and the problems aren't with stability, they're with usefulness. And honestly I'm kind of astounded at the responses I got.
I know what you mean.
I swapped to the built in drivers then changed back again to get all the options I need to monitor/manage the device.
I'd still be using Markus's Oh-La Labs drivers because they were amazing - until I started using Hub Mesh. It started with all the scheduled jobs getting bungled on the linked hub, and then somehow all the values became corrupted and every device just started throwing errors anytime any event was received from any device.
I am happy to see that the built in drivers exist, but I'm starting to realize that if I ever want to have my old functionality back, I'll have to make my own aqara contact sensor driver and I have no idea where to begin that process yet.. Maybe I'll dissect Markus' driver and see if I can strip out all the unnecessary stuff that was crashing Hub Mesh.
Can your give some more details?
Are you saying that every driver/app that shedules a periodic job has a provem in HE when the device is share via Hub Mesh?
Yeah. Everything worked fine for a few hours. Then I would start getting warnings in logs that scheduled events were unable to function correctly. Then after another couple hours, warnings turned into errors saying that the driver couldn't interpret the values of sensors because they weren't integers or decimals. Nothing worked after about 12 hours, just errors, none of the problematic device drivers were functioning at all anymore, on either the main or the linked hub.
If I had to provide a guess, I'd say there was some sort of buffer overflow or something going on that eventually just broke everything.
No, definitely not. I seem to have no problems with most of my devices. I only had problems with Aqara Contact Sensors and Aqara Temp sensors, and both of those I was using Markus' Oh-La Labs drivers for. It's clearly a problem with the drivers, as changing the drivers solved the Hub Mesh problems.
1 Like
Interesting...I've used Marcus' drivers on Aqara contact sensors w/hub mesh in the past w/out issue. Of course, this stuff always has a YMMV aspect, but I don't think this is a common/general issue, as I don't remember hearing it discussed before (but I can't read every post). 
Have others here echoed your issues?
No, I haven't seen any other people echoing these issues.
But I tried it twice, same results both times. Both the main and the linked hub started throwing all sorts of errors, and switching the built in drivers solved all those problems.,.
Well, this is nothing more than band aid which is masking underlying problem(s).
But if this works for you ...
1 Like
Depends how you use it. Previously, all of my exterior doors had notifications when the door was left open. But, I have a button pad next to those doors and pressing button 4 would just set the contact to closed, preventing the notifications while the door was intentionally left open. Closing the door again would just reset the whole system, and if the door was opened again the notifications would resume. Honestly, it was a very simple solution.
Now, to accomplish the same thing, I have a global variable for each door, and the button sets the variable to false, which prevents the notifications. Closing the door again reset the variable to true. Same functionality, slightly more convoluted, but accomplishes the task, I guess...
2 Likes
Talking about reliable sensors.
Of course now thing could be much better but I have my personal taboo for using Aqara (as well as Tuya) toys. In a past this was only huge headache with near every Aqura/Tuya sensors.
Yeah, I've read that as well but honestly with both the C-5 and now the C-8 Pro, I haven't ever experienced the constant disconnects or huge difficulty pairing the devices with Hubitat that others seem to have reported in the past. I was blown away when I saw that the Aqara devices had been added to the official compatibility list, I had always thought Hubitat recommended to steer clear of them.
Regardless how you use sensors they ALWAYS must report a correct status. Good and stable logic/automations for covering all potential corner cases is a very different story.
I'm just going to keep disagreeing with you on this. But that's OK. Not every mind thinks alike.
If I can manually set the status, then in my situation, the correct status is the one I intentionally set for the situation. As people have pointed out, there are work arounds, but I will disagree with you on this point until the very end. Hubitat is by far the most open-minded and flexible automation platform in existence. It's all about flexibility, except sometimes, I guess ..
My point is (a bit exaggerated):
Sensor which produces coin flip style results is useless.
Instead it will be much cheaper to use a random number generator.
Once again (sure, you can disagree):
All Sensors ALWAYS must report a correct status which MUST NOT BE ALTERED artificially.
How logic/automation is dealing with Sensors is a very different story.
