paulbates

Ok. You mention above you replaced the PLM... did this problem start about that time?

Ok, you're welcome.. did that solve it?

Ok. Did you unplug the PLM from the wall, wait 10 seconds, and plug it back in and retest as listed in my first response? What happened? If that doesn't help, it looks like it might be some kind of new power-line noise; something new in your house that would have been added around the time the problem appeared. The way to start isolating that is to get a plugin x10 module, and temporarily plug it in to the same outlet as the PLM and repeat trying to turn it on with eisy / UDM. What happens?

The PLM/eisy saw the device at House Code B, Unit Code 3 switch on. IThe question is, what programs, if any, do you have that act on B3? The same is true a few lines up for House Code N, Unit code 11. In a nutshell, your PLM/eisy is seeing x10 traffic so not the issue That takes it to what programming do you have for X10 devices, especially those 2 HC/UC combinations?

I have yolink too and it is a great compliment to insteon on a UDI system. I don't have the contact sensor but the devices I have all function as advertised.

While I don't get errors, I don't get any response getting past the button on the login screen. I can click Portal Login or Go to my ISY.... nothing happens at all EDIT: I eventually get a 429 error, too many retries.. meaning my spastic pressing of the login button is getting rejected 🤪

If the conditions of the program changes to false, the program will stop executing in its tracks during the Wait. Since you turn off pool/waterfall, that kills the program in the first then statement What you need to do is have 2 programs: Reset Waterfall - If Time is 2:00:00AM And 'Outside / Pool Waterfall' Status is On Then Run Program Reset Waterfall 2 Then Reset Waterfall 2 If (No condition) Then Set 'Outside / Pool Waterfall 3way' Off Wait 10 seconds Set 'Outside / Pool Waterfall 3way' On

In addition to @Guy Lavoie suggestion, go to tools/diagnostics event viewer. Trigger events with your remotes, the ISY should be seeing them

Since X10 is working outside of eisy/plm, here are a couple of easy steps to eliminate the PLM: In iox, go to tools / diagnostics / PLM info. What does it say? Unplug, wait 10 seconds, and replug in the PLM. Retest If that second step works, we should talk more about it here as it might be symptomatic of a failing PLM

Insteon wireless heartbeats are sent daily. Your results of weeks between heartbeats say that the contact sensors are in a box that is shielding their rf, and/or They are far away from the PLM or nearest dual band device Do you have an insteon lamp or on/off module you could temporarily plug between where the sensors are and the house powerline to test this theory?

Didn't all the 994is have basic x10 capability? I think the module added the ability for extended x10 codes naming nodes versus HC/UC Depending on what features you're using, it could work with potentially some basic programming changes. Plug in the backup unit and see how it would work for you programming wise as well as test to see if perfection returns

What you could do (psuedo code) program 1 If sump pump activated Then: Send notification Run program 2 Program 2 (No if) Then Disable program 1 Wait 1 hour Enable program 1

There are options that include timers and/or state variables. What's needed is: How do you define how often you do (or don't) want to know? How is the program triggered? I use a yolink plug in a similar way to monitor my dryer so it turns on the room vent fan when the dryer is used, based on configuring a yolink alarm state when the current draw of the dryer is sensed... Is that what you're doing? Can you post your program if you have one?

There's a similar post in the past specifically for the Kasa pluggin Asking @Geddy to move this to the Kasa pluggin area so that @Jimbo.Automates will see it

Log in and take a look. I have no developer access, just looked and I can "Load Profile" on all of my plugins

There's always a few simple things to try with Insteon that don't take that much time to try and see if they work. In iox try right clicking on the sensor for the garage door open close (assuming an iolinc) and click Restore Device

Guessing "no". The forums indicate that they haven't logged in since August 14, 2022.

There's software under development that would replace the admin console a web and/or app that would be served off of eisy. The end of year 24 announcement was that the foundational underpinnings were installed with the big update from earlier this year... which is different than the finished product being delivered and ready. In a different post, I recall that initially it would be Insteon only in the first rev when that's delivered. It's not there in usable form yet.

It sounds like you did everything to eliminate java on the PC (assuming its a pc). Anything else PC wise change? New PC, network card, virus software?

This does happen with Insteon from time to time per @Techman's explanation. In my experience keypads and the old togglincs tend to be the biggest culprits, sometimes needing a restore device every few years. Another factor is sometimes new devices come from the factory needing to be factory reset. You may have had 2 from a production run where this was the case.

I do have several N-ways but no resume dim. What I have noticed on the i3 paddle flags is that value presented by iox is not what's actually in the switch. Have had several "hmmm?" moments on that. The way to check is to go to the flags value for one of the responders and see if resume dim is what you think it should be.... Then press Query while on the flags value. What happens? In either case, press the resume dim button in the flags again to force the setting to the switch One that got me was "disable rf". I have an i3 paddle in a far away location and it was not communicating properly. On querying the flags, Disable RF was on(?) and the approach I described above fixed it.

There is an SD Card. The SD card is essentially the hard drive of the ISY. The operating system and all of your automation are stored there. Though this article is for the ISY26, it is still relevant https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card

Flashing blue is a SD memory card issue. Try reseating the SD card issue. It can be cleaned with a pencil eraser before reseating If its an older ISY 994i, chances are the card needs to be replaced

It will take to statements to get the total in the variable: $TempGradient = $inside temp $TempGradient -= $outside temp The -= means subtract $outside temp from $Tempgradient. $Tempgradient has to be a state variable, as is any variable that is used in an If statement

Take a look here https://wiki.universal-devices.com/ISY_Users:V5:Program_Variables