User manual added to post #2. 
1 Like
Clicking outside selected tiles does de-select all. However, distribute horizontally still did nothing and the flow is still not appearing when running a Test Flow in the flow or minimal.
- Removed the 'Distribute H' and 'Distribute V'. They have been flaky from the start and never worked right. Problem solved.
- My Test flow is showing without issue. Notice in the screenshot that the Trigger is highlighted (blue outline) and I have 'active' in the test input. Also notice in the lower right hand corner, you can see that the Flow was in fact triggered by the Test feature.
Just a note bptworld ..
Really like that you can change stuff now, and save it and test / try it
with out having to leave everything and come back.
really nice job on the hole program in general. Sure glad you are back doing your thing!
Ps .. What's with the different colors of join lines ?
Thanks !
1 Like
I don't know why, but the flow isn't visible for me when I do a Test Flow. You can see from the screenshot the Trigger is selected in both the main area and minimap. Plus, you can see I put in the value of "5" for the test which is what should have resulted in a True flow path.
When I pushed the Inovelli button 5 times the flow appears and it worked. (The switch is an Inovelli red dimmer, LZW31-SN and the flow is showing that it was not == off (i.e. it was on) and thus it was turned off (which is why the Condition box is now showing it is off.)
BTW, is there a way to make the flow more visible. Sometimes I really have to strain to see it as the flow outline is just a fuzzy yellow.
To WarlockWeary's question about the different connector colors, am I correct that they start off blue and turn green if that is the flow path? If that is correct, then the fact that all of my connectors are still blue in my first screenshot shows the flow wasn't tested when done from the Test the flow button (even though I got the pop-up saying it was tested - and I am doing all for this on my Mac Mini M4 Pro in a Chrome browser).
You've been wonderful about fixing/creating things so fast, so please don't take this as a criticism, just one thing that I thought of as I was typing on the off chance it slipped by as to the the H & V distrib. Are you turning off Snap to Grid (if it was on) before you were doing the spacing? Also, if it was on, maybe it was needed to do a final adjustment to be sure the lefts (for H distribution) or tops (for a V distribution) are on a grid line before you turn Snap to Grid back on?
Is it possible to add fields for the Left, Height, Top, and Width of each tile that would populate when the tile was clicked on and allow us to manually enter values so we could tweak each tile's position to our heart's content?
Blue is the default color, Green is the Flow running, tracing the path taken.
The Test feature is only setup to handle up to 3 taps, I'll have to edit it later.
All nodes will now turn the same green as the connections.
I don't personally use 'Snap to Grid'. Dist H & V are gone, never worked and caused more problems than they were worth.
Anything is possible, it's just code. BUT, that's not something that'll be added. Too much work/problems than what the outcome would provide. Moving nodes without using the mouse button really causes some serious havoc within the system.
Really surprised nobody has found any issues with the logic! That's a good (great!) thing I guess, lol.
- Minor cosmetic changes
'Repair'!
Just uploaded a new version...
- Added logic for more than 3 (up to 10) button taps
'Repair'
Also note, I'm leaving today for a few days - See you Sunday!
2 Likes
I did the Repair and I saw the green outline on the tiles when I did the physical switch push (albeit there was no outline in the mini map tiles and the mini map connectors didn't change color) but no matter what number of pushes I put into the Test the Flow it doesn't run.
When I changed the Trigger to have a motion sensor active then the test ran and the light changed. So there is something going on with testing the number of pushes on a switch (at least an Inovelli Red Dimmer LZW31-SN).
I also found it interesting that even when I was not actively testing the flow with the motion sensor as a trigger that the flow would show its current path as the sensor alternated between being active and inactive.
I did see that even when inactive (or on the non-current flow) there was a thin green outline around even the Condition and Don Nothing tiles.
If possible the tiles outline should match the tile's color when they aren't on the current flow path. That would make it easier to see the true flow.
Hope you have a wonderful weekend. It's good to have a fifth on the fourth.
I wanted to test a Trigger for between 2 times. However, the 2nd time box never appears:
I also tried to do a time test with an AND >= 8:00 AM and <= 1:00 PM (13:00) by putting in 11:00 AM and then tested it with just 11:00. The test never ran. BTW, I did these tests at 11:46 and 11 :47 am
Also note the current time does not appear below the line in either Event Trigger. I would expect that it would just like a switch or light reports its current state below the line
I'm baaaaack!
- Current time now shows on triggers/conditions
- Between now shows the time inputs correctly
- delayMs now works
'Repair'
2 Likes
One more quick one...
- Better highlighting on the mini map
'repair'
1 Like
I tried to test the Inovelli Switch again, but it didn't run. Here is a screenshot showing the Trigger was selected and value 5 was used.
Here is a screenshot of the logs showing that it expected a "5" but what it got was "on"
BTW, here is what the logs look like when I click the physical switch 5 times:
I also created a new flow to test the between times condition. I found that I had to save the flow, close it, go to the first FE1 window, activate the flow, then go back into the Flow Editor and pick it before I was able to test it.
My test was that if it was between 6:00 AM and 7:00 AM to turn Stuart's Den Desk Lamp On if it was off. As I did this at about 6:43 AM it should have just turned on by itself, but it didn't.
I then tried to test the flow using 06:45 AM, 06:45, 6:45 AM, and 6:45 but none of them ran the flow either. In looking at the logs it seems the time was being converted from "AM" to "am":
So I tried putting in the test time as "am" but that didn't help.
I went back to the flow to see if I could enter the comparison times as "am/pm" but couldn't. So I think it may be failing as the AM/PM isn't matching the "am/pm" part.
Here is a screenshot of the flow:
I then thought I'd do a test where the time comparison was the Condition, not the Trigger. For the trigger I picked that the Day of the Week was Monday. However, that was no exit point from the DOW.
I then tried to make the Condition that it was >= Sunrise. While there was a connector this time from the Trigger, the actual condition >= was missing the Sunrise portion:
I tried to test this with 8:45 AM, which I know is after Sunrise, but that didn't trigger the flow. Here are the logs for that test:
On the chance you have been working on FE, and maybe even have done a repair, but didn't post it yet, I went and did a repair about 2:35 pm Monday. It looks like my hunch was right because I was able to see that a time based flow was evaluated and the flow appeared in the mini map as well.
However, "Sunrise" is still not appearing in the Event Trigger tiles and it did not evaluate it correctly as my test time, 8:45 am, is >= Sunrise.
Here is the logs it produced:
As you hadn't posted for us to do a repair, of course, this was just on my own and I'm sure you felt you weren't ready to do a new "repair" post. As such, I don't know if you have worked on the Event Trigger Sunrise/Sunset yet and/or evaluating >=Sunrise vs. a time, I'm just posting this in case you have to let you know there is still issues with it and to let you know that at least it is running and that the mini map is showing the flow nicely too. So I hope you take this as me just trying to help the process by doing lots of testing and not criticizing you in the least. If anything, I hope you understand that by me doing so much testing (even when you hadn't posted to do new repair) that it shows how excited and enthusiastic I am about all you are doing. As I've mentioned before (too many times now? :-)) I really think this could go a gigantic way to silencing any critics who say they love Hubitat's power, price, and features, but find the rules UI cumbersome. So please take this as my enthusiasm and not negative meddling.
- Fixed, check your Flows as options have changed
- Yes you do, this is already documented.
- Reworked a bunch of stuff, please test and let me know. Thanks
'Repair'
Be sure to open and hit 'Done' on the One app after update.
I did a repair and then went into the FE1 initial screen, hit done (which took me out to the Apps level), went back in and then went into the Editor.
I saw that my time comparison one created a sub flow.
I tried them both using 8:45 am and they both failed. It also didn't fire off by itself as the time when I tested it (19:44 (i.e. 7:44 pm) is >= Sunrise and is before 8:00 pm.
The top one is the sub-flow and the 2nd one is the one I created.
BTW, I don't think the False choice coming off the 2nd condition (was Stuart's Den Desk Lamp On) should have fired as that condition wasn't on the path (although it should have been on the path as it is after Sunrise and before 8:00 pm. But if it had been properly on the path then the top/True choice should have been selected as the Desk Lamp is off. I'm guessing the 2nd condition (incorrectly) got fed a False so the False choice was selected coming out of it).
Don't mess with sub-flows yet, forgot to hide that! lol
The switch taps has now passed the test:
(Though I found the neon blue Taps Choice a bit hard to read).
Also, BTW, I thought my eyes might be deceiving me, but I'm now 99.9% convinced the tiles jiggle every so often. The least of all issues, but don't know if that can be prevented.
In the past when a flow was tested and the path took it to turn on a light it actually turned on the light. I can understand there are lots of reasons why a user would not want the actions to actually happen. (Let's say hubby creates a flow to turn on the bedroom lights at 8:00 am late one night while wifey is already asleep. Actually turning the light on then does not seem wise - a low WAF in technical terms. 
). But, I also can understand why one would want the test to actually run the flow and do the actions. Is it possible to create a checkbox to run the action vs. just to test the flow path?
Yes!
The actions should still work as before.
I'll add it to the list
Ha! Yes, they do. That's what keeps all the connection lines where they are suppose to be.
