larryllix

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.

I had about 10 units at one time and there were so many different versions of HBs.

IIRC the button in the leak sensor toggles the wet/dry signal for a quick test. However IIRC the HB goes on a separate channel. Paul's restore should work. If not, factory reset the LS and then do a restore. Make sure your monitor programs include HB ON, ORed with HB OFF. Some versions put out both signals but only every alternate day for each.

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?

Ohhh one more thought. My original single AX92u seemed to have weird problems during summer hot days. Even though it was in a A/C controlled home. Placing a Tag on top of it I found problems when it showed over 45c. Many routers I have had had poor ventilation convection paths and mounting them vertically on a wall solved that. Now I have USB plugged muffin fans underneath each piece.

Well that was one thing that made me really happy with Insteon. It was it's own network, own protocol, and not dependent on WiFi or a router. That gave me power to power cycle my router using a simple OnOff plug-in module. My thoughts were when all devices were initially sent a "get your free IP address", at the same time, some devices just lost out. I could never prove that but it seemed a select few devices took turns not getting an IP address. My worst was my ISY, while I was in the Carribean, contained an assigned IP address of 00:00:00 and the router didn't like that one. It scrambled my whole network until I rebooted the router and then my ISY. I had three ASUS AC5100 s (can't remember the model number now AX92U?) and the vendor rebuilt one (after tearing my hair out for a year and a half) seemed to work better, the older one short of NVRAM went into a background, low usage, position, and the third was always a problem until I moved, and went back to a single router, without a crippled WiFi Tx power again. They never state the maximum devices they can handle in the device table, only the count per band. With your only 14, that shouldn't ever exceed and limits. It would likely be extremely hard to recreate it but you could try power blinking both devices at the same time for 1/2 second. Nahhh..too much work, unless it happens again! Good luck

I found rebooting the router would correct things mostly. I suspected my older router had too little NVRAM inside and couldn't remember that many connects. The magic number for that router seemed to be around 51 devices. Later versions had more NVRAM installed.

I had a lot of problems (using an advanced ASUS mesh router system) in years gone by with problems like this. Not sure how your electrical grid operates in your area but many use Reclosing schemes, to minimise the area that gets affected with lightning strikes. The basic idea is, when there is lightning on a transmission line and it arcs to the earth, the ionised pathway conducts the grid energy behind it, and can cause much more system damage. Generalised: the reclosing scheme detects this and trips the line out, with an almost instant reclose (picks the line back up). This breaks the lightning discharge arc and allows the ionised air / wood pathway to dissipate so the grid energy doesn't follow. This usually followed by longer and longer delays coupled with "toughened" sensing, to detect whether it worked and/or there may be a pole down and a tree branch laying on the line. Techniques vary by area and system needs, and Engineers ideas. /lesson done What this means to my routers was that a sudden and fast blink of the AC was enough to scramble some of the router and device(s) logic but not long enough to make the router see the power supply blink and it wouldn't reboot going through a cold start-up process issuing invites to all the devices to relink to the router. My solution to that was to build an algorythm for ISY to see some "all the way through the system and back" packet detection and cause a series of increasing length power blinks for my router equipment. IIRC I used a web timeclock for proof of passthrough system and a second algorithm on some local device along with a query to detect at two levels. I found these routers would just forget some devices were allowed to talk through to the Internet at times. Everything but one device worked fine but one just couldn't talk through, despite everything inside the router showing as perfect. Anyway, I installed counters for occurrences and almost all my problems went away on that front. The counters proved it was still happening but could be automatically corrected. My conclusion was that different devices had different time lengths before cold booting. It may be worth investigating. I know you are a tech aggressive guy.

I don't understand why you want to turn the fan off first. This adds more chances to glitch the control with elctrical spikes causing damage to the circuits,