larryllix

I have no disable option or enable option for any of my FOLDERS, only programs. However folders can be disabled via conditions added to their "IF" section. Eg: If X is not X always evaluates as true. Folders can also be disabled by program lines. This can be a convenient way of turning off a complete function all inside a folder. However one big caveat is if a program is currently running inside the folder when you disable it, the running program will stop immediately and not conclude, possibly necessary steps to terminate the process. Programmes inside a disabled folder can still be called as subroutines AFAIK. This needs to be confirmed because I avoid actively disabling folders due to being a very obscure practice and bad programming practice. I do use them for defunct programmes not in current usage.

Incorrect person flagged. @TInoue

As a usage example of the Repeat While construct, here is one to generate the absolute value of a variable. I have used this technique to get the difference between two temperature sensors in different rooms (indicates air circulation is needed) Variable = tempSensor1 Variable -= tempSensor2 Repeat While Variable < 0 . . .Variable *= -1 Repeat for 1 times Here is a more complex example of averaging only valid values while disregarding unwanted values. https://forum.universal-devices.com/topic/18921-v5-averaging-using-only-the-best-values/#comment-176418

Likely 240vAC and 50 Hz. and instructions will be in sandscript.

There is a nasty way of doing most of these using "repeat while" construct. If whatever Then do something Repeat While 'lamp' < 1% do somethingElse set 'lamp' = 100% Repeat for 1 times do anotherthing Else -- Of course you can set a variable before the repeat while loop and then modify it in the loop. Dirty but it can work in most cases. Multiple Case type constructs can be built by terminating each Case with a line: Stop 'ThisProgram' . Note: Repeat For X times is a program logical syntax error. 'Repeat 1 times' means no repeat at all. Should have been named: 'Execute for 1 times'.

From the ecobee status webpage. "Scheduled - On May 6, 2026 from 9:00am-10:00 EDT, we’ll be performing some scheduled improvements. The important thing to know is that ecobee thermostats will continue to operate as usual on the set schedule and by manual adjustment, including all in-progress energy-savings events. There’s a chance that the ecobee app, web portal and third-party apps might be temporarily unavailable. Thanks for your patience and sorry for any inconvenience! May 5, 09:13 EDT"

UPDATE: Rebooting IoX resolves this. IoX appeared to function normally for about 30 minutes before this started. Weird.

Logical operators are not showing in "copy to clipboard" text or on the graphical screen. Kitchen.sink.passthrough - [ID 0075][Parent 0055] If Program 'Kitchen.counter.passthrough' is True $sTheme.kitchen < $cMODE.FULL.ON <----- AND missing Then // delay time must be longer than Kitchen.counter.passthrough delay Wait 3 minutes and 15 seconds Repeat While $Kitchen.theme.saved is not 0 $Kitchen.theme.saved = $sTheme.kitchen $sTheme.kitchen = $cMODE.RESET $sTheme.kitchen = $cMODE.FULL.ON Repeat 1 times Else Wait 15 seconds $sTheme.kitchen = $Kitchen.theme.saved $Kitchen.theme.saved = $cMODE.OFF

After all the algorithms I have use to control temperature ramping down during heating, and temperature ramping up during A/C (no brand does this), I ended up only using my third ecobee for Home/Vacation status. It was a much more reliable status than any other method I had fund in years of experimenting. Hopefully this status will survive as it demands only one status point, unlike weather with it's dozens of analogue points. ecobee has been the best stat I have used for HVAC from almost a dozen brands, so far. No the brand has had the accuracy of control, yet. Best of luck with this. Your PG2/3 bridge plug-in has been the best.

As ELA (above) suggested, this is a utility problem to enforce the power quality being shipped into your home. The neighbour may be causing it but the utility has a responsibility to quench it before it spreads to their lines. Their are very strict rules on these kinds of things for most utilities specified by government regulations and/or boards that enforce these things. The neighbour then has a ticket to push the installer into correcting the cheap inverter system and clean it up.

I don't know of anything else that uses java anymore except maybe a few vehicle O/Ses.

For non-automation controls ie: manually (human) operated, trigger a program to operate the scene in ISY. With manual operations a few milliseconds of delay is not perceptible.

polISY -------- Updated to v6.0.5 from v6.0.4. Went smoothly. Asked for and needed a reboot to operate properly. IoX needed no updating and java cache was not cleared.

I had an ISY and a polISY running together at one point in time. I set up a bank of variables duplicated in both devices. I wrote a program detecting if each variable changed and would send it via the Network Resources into the REST protocol to set the equivalent variable in the other device. Since I run most of my lighting scenes and levels via state variable already, it was a piece of cake to have one device doing logic and sensing, while the other operated my WiFi based lighting systems. Eventually all got ported to the newer poLISY but the system worked like a charm during the port over. No delays were noted.