Version 0.4 just released, based on @wogfun feedback now has an option (defaults to on) to autostop an effect when the condition is false. Can be turned off for more advanced use cases.
Current Roadmap:
Here's a question..
Let's say you have all your LEDs set to green for the alarm being disarmed.
Now a door opens which changes the LED to orange, now the door closes.
Does your dash have a way to set the LED back to the original color?
Each time an event happens, all the rules are re-evaluated based on the assigned priority (and its the priority levels that are key to this). So for your scenario we could have:
Priority 1: LED color: green, Rule: Alarm is disarmed
Priority 2: LED color: orange, Rule: Any contact is open
When this runs, if the alarm is in the disarmed state, the LED will be green. However, if a door opens, the higher priority 2 rule overrides and the LED will now be orange. Once the door is closed, it will re-evaluate all conditions and see the alarm is still disarmed (i.e. true) but now priority 2 is false so the LED will be green again.
@jonathanb My reading skills are lacking tonight.
I was just rereading the thread and this was asked and answered already.
Just wrapping my head around the LED Priority stuff, I get it now
Thanks for the response.
No problem, I'm really using this time as an opportunity to find out what kinds of things people might do with this that I've not thought of yet 
Beta testing version 0.6 is now available from the link below (folder and filename has changed since previous versions) You will also need to go back into existing conditions to select the right device type and check the notification settings (most likely the color will need reselecting)
Along with some bug fixes and functionality improvements, the big change is initial support for multiple device types. I've added support for the forthcoming Inovelli Blue Zigbee Fan Switch and initial support for the Inovelli Red Z-Wave Switches and Dimmers.
Since I do not have a Red dimmer/switch to test with, I've no idea if this works so consider it experimental and feedback is welcome!
got it installed, running into this
When I do click on 'Select to add a new activation condition'
I get this -
Unexpected Error
An unexpected error has occurred trying to load the app. Check Logs for more information.
Error: Cannot get property 'null' on null object
Log shows -
java.lang.NullPointerException: Cannot get property 'null' on null object on line 214 (method editPage)
-Update-
Looks like I only have this problem when I select a Red Series Dimmer or Switch from the drop down menu. If I select a blue series it brings me to a mini dash where I can configure everything
The new Blue Fan switch is still in beta and has a slightly different device name match.
It is currently "Inovelli VZM35-SN Zigbee Fan Switch" your current code is looking for something different and doesn't match. Note this naming may change when it goes into production later.
No problem, easy to update the driver name as you likely saw, won't break anything to change it when its production
Thanks, it should now be fixed. I had split out effects based on the LED number and device type and it seems I had some old code still.
This is because the effects for the Inovelli Blue when selecting an individual LED are not the same list as when selecting "All" LEDs and I originally just had one option for both. For the Red, there are no individual LED options and that was not handled by some older code 
Thanks, I think I've got the manifests all updated now. That 'null' should no longer show up with a new dashboard (it should now default to just 'New Mini-Dashboard' as a name)
OK, no more error. But didn't activate the LED
Your App, setting Master Bed Room #1 to Solid Orange when a contact sensor is open.
Doens't work
dev:5682022-12-03 05:56:03.506 PMdebugMaster Bedroom #1: ConfigurationReport(parameterNumber: 16, size: 4, configurationValue: [0, 0, 0, 0], scaledConfigurationValue: 0)
app:8452022-12-03 05:56:02.307 PMdebugstartNotification(0)
app:8452022-12-03 05:56:02.301 PMinfosetting Master Bedroom #1 LED #All (id=condition_1, name=Door Open, priority=0, effect=0, color=null, level=null, duration=null null)
app:8452022-12-03 05:56:02.296 PMinfocondition_1: condition returns false
app:8452022-12-03 05:56:02.293 PMinfocondition_1_contactOpen: 'Contact sensor is open' is false
app:8452022-12-03 05:56:02.283 PMinfoevent contact received from Test Contact (value closed)
dev:5752022-12-03 05:56:02.259 PMinfoTest Contact was closed
app:1122022-12-03 05:55:43.438 PMtraceReceived ping from Smartthings.
dev:5682022-12-03 05:55:40.123 PMdebugMaster Bedroom #1: ConfigurationReport(parameterNumber: 16, size: 4, configurationValue: [1, 0, 10, 7], scaledConfigurationValue: 16779783)
app:8452022-12-03 05:55:38.922 PMdebugstartNotification(16802823)
app:8452022-12-03 05:55:38.920 PMinfosetting Master Bedroom #1 LED #All (id=condition_1, name=Door Open, priority=5, effect=1, color=10, level=100, duration=null Infinite)
app:8452022-12-03 05:55:38.918 PMinfocondition_1: condition returns TRUE
app:8452022-12-03 05:55:38.916 PMinfocondition_1_contactOpen: 'Contact sensor is open' is TRUE
app:8452022-12-03 05:55:38.913 PMinfoevent contact received from Test Contact (value open)
dev:5752022-12-03 05:55:38.872 PMinfoTest Contact was opened
Old Dash Board App setup to do the same thing but with Cyan color
This worked
dev:5682022-12-03 05:59:02.825 PMdebugMaster Bedroom #1: ConfigurationReport(parameterNumber: 16, size: 4, configurationValue: [0, 0, 0, 0], scaledConfigurationValue: 0)
dev:5682022-12-03 05:59:02.724 PMdebugMaster Bedroom #1: ConfigurationReport(parameterNumber: 16, size: 4, configurationValue: [0, 0, 0, 0], scaledConfigurationValue: 0)
dev:5682022-12-03 05:59:01.385 PMdebugMaster Bedroom #1: ConfigurationReport(parameterNumber: 16, size: 4, configurationValue: [0, 0, 0, 0], scaledConfigurationValue: 0)
app:8452022-12-03 05:59:00.175 PMdebugstartNotification(0)
app:8452022-12-03 05:59:00.172 PMinfosetting Master Bedroom #1 LED #All (id=condition_1, name=Door Open, priority=0, effect=0, color=null, level=null, duration=null null)
app:8452022-12-03 05:59:00.169 PMinfocondition_1: condition returns false
app:8452022-12-03 05:59:00.165 PMinfocondition_1_contactOpen: 'Contact sensor is open' is false
app:8452022-12-03 05:59:00.146 PMinfoevent contact received from Test Contact (value closed)
dev:5752022-12-03 05:59:00.084 PMinfoTest Contact was closed
dev:5682022-12-03 05:58:56.292 PMdebugMaster Bedroom #1: ConfigurationReport(parameterNumber: 16, size: 4, configurationValue: [1, 255, 10, 126], scaledConfigurationValue: 33491582)
dev:5682022-12-03 05:58:55.378 PMdebugMaster Bedroom #1: ConfigurationReport(parameterNumber: 16, size: 4, configurationValue: [1, 255, 10, 126], scaledConfigurationValue: 33491582)
app:8452022-12-03 05:58:54.023 PMdebugstartNotification(16802823)
app:8452022-12-03 05:58:54.018 PMinfosetting Master Bedroom #1 LED #All (id=condition_1, name=Door Open, priority=5, effect=1, color=10, level=100, duration=null Infinite)
app:8452022-12-03 05:58:54.016 PMinfocondition_1: condition returns TRUE
app:8452022-12-03 05:58:54.014 PMinfocondition_1_contactOpen: 'Contact sensor is open' is TRUE
app:8452022-12-03 05:58:54.005 PMinfoevent contact received from Test Contact (value open)
dev:5752022-12-03 05:58:53.954 PMinfoTest Contact was opened
Your debug log was good, helped me figure out where I was going wrong trying to calculate the notification value. However, pretty sure I've got it right now so if you want to grab the updated code and give it a shot that would be great
Looks like it's working now, thanks!
Can you add Mode Manager to the list of conditions?
Another thing I'm after is a way to put a delay in a condition, doesn't look like you can do that now.
For example, If a contact sensor has been open for x amount of time have the LED blink orange
Good suggestions, mode manager should be be a quick add, the open for "x" time requires a little more work but has been on my todo list anyway!
edit
Looks like I found a bug / oversight with the conditions which is also in the original app.
I'm trying to trigger the LED when all the locks are 'locked'.
When you select multiple locks what you get is 'if ANY' of the locks are locked it triggers the LED.
This type of condition works great for door contact sensors, not for what I'm trying to do.
I should probably be using rule machine however that thing has kicked my butt and I give up trying.
Thx
Thanks, found the error that wasn't passing the "All/Any" option to the method that does the actual comparison due to the wrong setting name being used.
Fixed that and added the mode check to beta release 0.8 now available!
That seems to do the trick, thanks.
Looks like there is a bug with the variable effect option for the LED - you're unable to set one.
Thx
Can you check you have "string" variables defined in the hub? A quick test on my copy shows it does pickup any defined string variables for those fields.
Download the Hubitat app
