BTW, are you going to add Modes as a Trigger? I see from ralph.vasquez's post that they are under Home Location. That wasn't obvious to me as I thought that would just be like Home or Away because a Mode can be Morning, Evening, etc. but there is nothing like that under Time.
So maybe Mode should be added.
MISTAKEN POST!
I tried having the Trigger between Sunset and 6:45 pm which didn't run - which was correct as that is before sunset when I did the test in July
Home Location / Modes are already in Triggers and Conditions
Make sure you have Modes setup in Hubitat. Both Triggers and Conditions here are pre-filled with all my modes setup in Hubitat's Integrated Mode Manager.
Had them working earlier, will look at this tomorrow.
Thanks
One other thing about Sunrise and Sunset, I think they need to always have an offset option, even when being used in a between situation.
Time is working. It was me. I was using 6:45 pm which is not after Sunset. So sorry. Hope you see this before spending hours scratching your head trying to figure out what is wrong with your code when the answer is that it was me who was wrong in my testing time.
I see you often (always?) end with a Do Nothing node coming out of a condition. Is there any reason we need to/should do that vs. just having nothing attached to that otherwise unused exit point (other than the clarity of reading "Do Nothing")?
There is no need to ever use this. I just like it for visual clarity.
For testing, I can clearly see why you want us to have to select the Trigger to be tested if there is more than one, but if only one then I'm not sure why it needs to be selected first.
Also, I set up an OR condition for a switch being pushed 5 times or after Sunset. They both worked, but when I tested the top/Switch node it put a yellow highlight around the bottom/Sunset nide and made that link green instead of the Switch flow path. When I tested the bottom/Sunset Trigger node it did make its link green but the Trigger node itself had a blue outline with yellow underneath it (it appears):
In the below screenshot I selected the top/Switch node but the bottom/Sunset, flow shows as being followed. (BTW, I did this at about 7:00 am so that flow wasn't actually true). You can also tell I was testing the top/Switch node as the test value is 5 and the top/Switch node has a blue outline.
In this screenshot I selected the bottom/Sunset node using a value of 23 (11 pm). The flow worked, but the bottom/Sunset node has a blue surround (which I prefer to the yellow, but that is a different story. ;-)) and you can see a bit of yellow peeking out of the bottom Trigger node. (So maybe the blue is being added after the yellow so it overlays it?)
When a new flow is created I think it should be Activated by default not Deactivated.
Having two triggers with an AND is not logical in event driven systems like automation. The AND will always be in a conditional test after an event trigger has been triggered, it has nothing to do with easier to program or anything, it's just the way it is.
It's impossible to work because HE (and all other event driven systems) will actually trigger one instance of the flow and then another instance of the same flow (it's a trigger) and those both instances run in parallel but fail to go any farther than the trigger.
Sorry, but no no no no no! That could release all kinds of hell on the hub as you build out the Flow. Think it out, build, change, build again, then activate the Flow.
Good point.
Since connecting 2 triggers to an Action or a Condition is an OR and with the AND OR logic built in as a parameter makes sense to get rid of AND and OR nodes.
Can you consider making the name box a bit wider? It seems like you have the room for it.
Ver. 1.0.024 - 'Repair'
The Current State isn't visible with 2 devices and a logical AND (BTW, thanks for adding that they do have Logical AND):
I'm also not sure why it says Device: No device when my iPhone was selected:
Having both lights on, which did make the Action have a yellow outline, otherwise did not show the Current in the Trigger or change the Action from No Device:
Outlines are also acting inconsistently. Here the Action has a yellow outline:
But here it didn't:
Will work on that
It did, you just have the node selected (blue outline). You can still see the yellow around the inner edge.
I see. Now I'm debating if I like the selected outline or the flow outline to take precedence (i.e. to be the "top"/"outer" band). In either case, could you make the inner one (right now the flow yellow line) a bit thicker when that node is selected if it also has the flow outline?
Since I think you are very, very, close to finishing up, at least version 1, to make it look and feel more like other Hubitat apps I would like to see:
Free text names with spaces and symbols. Maybe it's just me, but as I use Inovelli dimmers I often combine multiple clicks (Push for the "up" part of the paddle (and the #7 favorite/config button) and "Hold" for the "down" part of the paddle, in Inovelli/Hubitat lingo) into 1 name like Stuart's Den Hutch 1P=Ceiling Light 100%, 2P=Top Hutch Light 100%, 1H=Ceiling Light Off, 2P=Top Hutch Light Off, 7P=Ceiling Light 35% (etc.)
Have the flow names appear as drop downs from the Flow Engine App on the Hubitat Apps page. Here is just an example from my Button Controllers dropdown:
BTW, I have a could have subflows still appearing in my Pick a Flow combobox. I deleted or renamed the parent flow. Is it OK to delete these?
Download the Hubitat app
