larryllix

Event triggered software systems can really screw up linear programmers. They definitely present some quirks. Think domino chains with lots of split out paths.

Any time a program executes a Wait or Repeat it allows the system engine to re-evaluate things and do I/O processes etc. When the ISY logic engine discovers your state variable has changed, it re-evaluates every program that contains that state variable. If it finds that variable in your If section has changed, it cancels any action already taking place in that program, and executes (starts over) the Then or Else section, depending on the outcome of that If logic. IOW You have created a monostable multivibrator oscillator that will never get past the next Wait 20 minutes line.

Well back working again...mostly. Suddenly started accepting my usual URL again on IoX Finder after about ten minutes. From inside ISY, I then found the HTTPS port and installed that URL. No IoX Finder icon on desktop. The only icon to be found and working is the old start.jnlp launch icon now. I can't find any option to install the IoX Finder. Seems similar to a few years ago, when it would be found in totally random places in folders. LOL More hunting to be done.

My IoX Finder just dropped out also. No changes were made. I have deleted all java files, uninstalled java completely, rebooted PC, reinstalled java latest version, loaded Iox Finder new copy. IoX cannot find either of my two polisys still. When I attempt to add a URL to the list I cannot remember the whole URL using the HTTPS format so I am locked out of my polisy(s). Very strange for a non-cloud dependent system this can happen without any local file changes to java, Windows, Iox, or polisy.

How many skills do you have loaded into your Alexa ap? My sister=in-law used to love to add every funny skill she could think of into my system and that seemed to slow down my HA system response while the Alexa servers would sort out where the commands needed to go. However, never that many minutes. I am talking 10-20 seconds, at times. With my blinds and other two server daisy-chained skills I ave experienced many "I cannot contact your xxx server". or "your server xxx seems to be offline" responses and then the device operates anyway, about 20-30 seconds later. Must be some sort of handshake back failure on those ones.

We have all been very surprised by the speed.

Interesting! However too small to read and browser magnification doesn't change video text size.

Maybe post your program here so that others can have a look at your logic. BTW: If Sunset would leave your program icon green after it ran the first time, until another logic triggered it False and turned it red. I am not sure what you are basing your deduction on.

As per @kzboray above. Open a ticket with UDI. I had the same problem a few years ago and it was just one module that didn't load properly. Michel sorted it out in a few minutes over the Internet.

Have you installed the IP address for your Eisy in you router's DHCP reservation table? This appears similar to what happens when two devices try to occupy the same IP address. Usually a power cycle of the router fixes that temporarily.

As per @IndyMike above, your If section is getting re-evaluated and running Else, which will stop the Then section from completing. Remove the time frame and make it a single time so it only can evaluate once per day, and not re-evaluate. There is no hysteresis in your temperature evaluation and the logic can bobble True/False quicky inside your five minute window. If 'WeatherLink / WeatherLink' Temperature > 97.0°F And At 2:45:00PM

@Chris Jahn

Are they both still freeBSD O/S?

Agreed. See you again in another years when somebody raises the need again.

Yeah I got it working eventually. However, that technique does not indicate the status of a scene. It only indicates the last scene command scene command sent out from ISY for the scene it is embedded into. Changing any component device inside the scene via another scene command or device control does not affect it's status despite the scene's resultant statuses not being true anymore. Again, people are attempting to assign a status to a trigger signal. It isn't really possible as they are different types of Insteon elements and not relatable to each other.

I saw no definitions or instructions to add any keys or values to it. That may be the problem??

I don't consider a state variable used for conversion into a pseudodevice as useful in an Insteon Scene. I find no way to incorporate these variables, or the pseudodevices the ISY Portal converts them into, even seen inside ISY at this point. Maybe I missed something there? However, it was mentioned about the Virtual device PG3 node server, that appears to be able to perform as a pseudodevices inside ISY, can be inserted into an Insteon Scene, and has intrigued me. I have installed the Virtual node server into my PG3 and it shows up inside ISY via IoX, but I cannot get it to perform anything except read one parameter that is permanently set to "True". I can drop it into an Insteon Scene and it appears as a valid device but never changes to show anything except "True", whatever parameter that is supposed to represent.

I am confused. Your original post showed it basically correct. Your program was sunset+30 minutes. Now you are complaining about sunset-30 minutes and it not operating today? I offered an explanation for the 2 minute calc error but now you are saying it didn't operate one evening but it did the next it did? Perhaps listen to some of the experienced helpers here, that have given advise, think about it, and respond to them. i see no problems except your story appears to be changing about what the problem is.

It may have been slow to come (as most UDI improvements) but the pseudodevice was an improvement made by UDI after much discussion over the years. Perhaps they just don't brag enough when they produce updates? However, it still doesn't solve all the scene monitoring possibilities that I can foresee. Now you have me interested to experiment with the technique (now that I am aware of it). I do not use many Insteon Scenes anymore, now that my lighting is almost all WiFi, ISY programs, and three MS IIs with buggy firmware in them.

I am not sure either of these techniques will work for many situations though. If I add a spare device or a pseudo device to a scene and turn it on, and then rest the level of one (or more) device(s) with another scene with the monitoring techniques actually see the original scene is not in effect anymore? With the spare Insteon device, I know it will into indicate properly, but with the pseudo device inside ISY, who knows how many smarts they put into it?

Sunset and sunrise change by about 2 minutes every day of the year except peak winter and peak summer.

Does this "virtual" respond to external devices initiating a scene, say from a Switchlinc dimmer button press? That was always one of the problems with attempting to detect the status of a current Insteon scene. Perhaps another Switchlinc sends out a different Insteon scene command that modifies one of the devices to a different level? I believe these reasons may be why a status flag has never been successful to detect whether a scene is still intact. They are not binary statuses with just True and False....sort of.

First, scenes responders do not send out any acknowledgements. Only program commands get ACKed, so there is no way to even know if they were successful. or the device even exists. Is another device sends out a new scene no monitoring would know about it without a distinct new query for status. Scenes were only ever meant to be a one way comm. I don't use them hardly at all, anymore. However most of my lights are WiFi bulbs. There is likely a complex way the PLM could tell ISY when a device has been fiddled with but it was never implemented due to too many errors that could occur.

If really needed I would write a program to detect several devices' ranges and consider True as the scene being activated. My method would be to define a state variable with a program that detects the variable to be non-zero and controls the scene with that. Now you can detect the state of the variable and turn it on and off via the variable. Of course this doesn't work for controls done outside of your ISY box. The program mentioned above would though. Remember levels are not always reported as exact numbers so a range of detection is required fir each device. Sent from my SM-S711W using Tapatalk

Possible coincidence with your schedules correcting it just after you press the button?