Thanks, no rush, not something that will happen often.
+1 from me for the delay @mjarends requested and your proposed solution. A delay after the first door opening for me would also work (where the threshold is 1 sensor). I want to turn off my dehumidifier in the garage if the doors are open, but don't want to turn it off if I just go in and out to get something, so want a 10 minute delay before showing the doors as open.
Could I also request that a group of contact sensors also include an the On/Off switch state variable (attribute)? I.e. On when open, off when closed. Would be nice to be able to use the device in other apps where a switch is needed.
Version 1.8.3 Released
Mainly just an update to the Contact Sensors child app. This update includes:
I could do with Acceleration attribute being counted as motion then I can add my SmartThings motion sensors to a motion sensor group
I can add it, but I'll have to either add a secondary device selector or just list all devices. The device selector lists can only be populated based on either one attribute or all attributes.
Version 1.9.2 Released
Thanks for looking at the delayed activation. I found a small issue though. I only set the delay for activation, with no delay for de-activation in a group of contact sensors. If I open one of the contact sensors the only change is in the list, which is good, and the contact and switch attributes change after the configured delay, as expected. But if I close the contact before the delay ends, the contact and switch values still get set to open and on after the original delay completes. You need to be able to cancel the delayed action I expect.
Thanks for the acceleration feature! 
On list gone crazy OTL
I think something is wrong with unicode decoding or encoding..(I'm using korean)
Umm....yep. I'll take a look when I get a few.
Just to confirm...are these the device names?
νμ₯μ€κ±°μ€μ€μμΉ2
νμ₯μ€κ±°μ€μ€μμΉ3
Yes. That's correct
If you change line 131 in the app code to this (just adding two slashes to comment out the line), it will correct the naming for you until I can get a permanent fix figured out:
//onList = groovy.json.JsonOutput.toJson(onList)
Thank you very much for your quick response. Fixed by commenting out line 131. But other groups in the same switch sensor group were not fixed. Driver is also the same omniSensors, why is one fixed and the other not fixed?
Each group will need an update before the listing will show correctly. So, if you just toggle a switch in each, then it will update. You can also click back through the app instance and it should update.
It works! Thanks alot!!
One suggestion I would like to make is for the "OpenListTable" state.
Currently the state uses table to layout the data, while effective, it does restrict some of the customizable options via CSS. There generally are more steps involved in tweaking table output with CSS.
I wonder if it is possible to change it to using < ul> tag to build that list? There are no shortage of methods to style UL, and it is also a more concise tag schema-wise
Another suggestion is maybe we can remove the header for the openListTable state? That would allow for easier customization in templates.
I didn't even know about the UL tag to even consider it. HTML is definitely foreign to me. Using it though, does appear to be cleaner and a little easier to code. Looks like the default Hubitat dashboard does automatically center the text in the tile, which was what got me going the table route in the first place. Only problem I found is that the Android dashboard app doesn't handle it at all, so I've reached out to that dev.
Here's the list using UL in the contact and power apps. The only thing I'm defining is to not use an actual bullet:
"<ul style='list-style-type: none'>"
I will add...the table attribute was an inadvertent push on my part. I was pushing a different change and had forgotten about that bit of code .
Version 2.0.1 Released
Can you add lock as a group?
Download the Hubitat app
