You do want to update the files for html/css/js to the latest from the repo for the HE builds (which the early post shows a method of doing this if the cloned the proper repo).
You then want to logout of the webCoRE UI, and login in again.
I also run a local server, and I'm having a different problem after doing all of that.
I updated my repo, restarted Apache, logged out, logged back in, and it works on my desktop but not on my phone. When I open a piston from my phone, none of the conditions show any devices, but from my computer, it works fine.
For example, if I have a condition "If Device1's battery changes then...", that shows up fine on my computer, but on my mobile device, it shows as "If then...".
First I cleared the data with the Android Chrome app. Then I cleared the entire cache of the Chrome app. Which worked for me. Long press the Chrome icon and go to "Storage & cache" and "Clear cache". That helped in combination with logout and re-login.
Now I am seeing on the UI a message no my nested IFs. THinking on how I write my pistons, I ask the following:
I have a switch and an IF statement (IF SwitchX is on then) and this switch represent "automation". So I put my entire routine inside that IF and if I want to "disable" the routine I just need to turn OFF that switch and to anable, I turn it ON. What would be a good way of doing this? Am I doing it the right way?
adding the switch is on to each nested if statement (and un-nest the the if statements with 'changes' in them. That would move the trigger comparisons to out level (left to right) vs. nested.
extra credit for keeping the trigger comparison first in the ifs that are 'AND'.
You want the if statements with 'changes' in them to be crossed on each execution (so that 'changes' can be tracked). What is currently happening is 'changes' is only tracked when the switch is on, which may sound right, but on first runs after switch becomes on may be wrong...
What if using the switch to pause/resume the piston - I could create a piston that pause/resume pistons regarding that automation switch. Is it healthy? Increases processing?
It is ok to have a switch control the execution of the piston. In this short piston you are subscribed to the events being tracked by 'changes' so if you watch the piston it is waking up when those things change, it just runs the first if statement then exits.
Having it run 2 if statements (if you follow my earlier suggestion) vs. one is negligible to additional overhead.
I meant that if you click this button in the editor:
You will see a bunch of "only when" blocks pop up on the screen. Put your outermost "if" condition in the "only when" block that's above the "execute" statement, then you can move your two inner conditions to top level.
What about groups of condidtion+triggers? I am using groups like the one below - disregard the "automation switch at the beginning which I will take out and include on each conditions bellow. Like this is a problem of overhead?: