Goose66

Also note that the diagram above of the circuit using/requiring 14/4 wire was obviously made before the price of copper got so high! ?

I am going to stick with recommending an electrician since it seems that you are unsure. That said, I'm curious to why the switches were removed in the first place - I don't think your original post said. If the original switches were removed to be replaced with Zwave or Insteon switches, I am hoping your take away here is that the circuit HAS TO BE REWIRED all the way back to the original location of the power and neutral from the breaker in order to make it work, so the current wiring scheme will not be sufficient, even if you could identify it. Also, non-contact voltage testers are good for keeping you from getting electrocuted, but suck in determining how a circuit is wired. I would suggest a volt meter instead. If your house is in the U.S. and built since the 70s, you can test all wires to ground. 0V to ground will be a neutral, 120V to ground will be a hot (line) and some interim voltage is likely an unpowered traveler.

I have noticed also noticed that the finder frequently doesn't work. The only virtual network I have is the VPN to my office, and finder sometimes works when that is connected and sometimes when it's not. Regardless of the VPN connection status, though, doing an Add with either http://isy or http://<local-ip-address> always works. However, sometimes when I return to finder the manually added connections are there, and sometime they are not, and if finder has not found the ISY, I have to manually add it again. There appears to be no pattern in my situation, but I will admit I haven't spent a lot of time trying to track down the problem.

Ah, I swear the 2413U showed "sold out" when I posted that post, but it does now show "in stock."

What are the PLM options? Just USB or will a serial PLM work? EDIT: Never mind - can't buy either, so it doesn't really matter.

Had you previously set a static IP on your ISY, or did you give it a IP address reservation in your old router?

As discussed many (many, many, many...) times before the Else clause is not that useful in ISY programs because of the fact that the trigger conditions for the program and the boolean logic in the if are all wrapped together and can't be separated. This has caused much confusion over the 12 or so years I have been on these forums. This is a classic example where you need two programs to get the "expected" or "desired" behavior (I understand this is just a test program). First program is enabled, and contains the "trigger" condition: If 'South - MS - Dawn Dusk' is switched Off Then Run Program SunRiseNotifications (If) Else <--- No Action ---> The second program, SunRiseNotifications, is disabled and contains the conditions you want to test in the if, but not necessarily trigger the program(s): If From 6:00:00AM To 9:30:00AM (same day) Then $Sunset.Flag = 0 Send Notification to 'Broyd' content 'Sunrise Now' Wait 1 minute Send Notification to 'Broyd' content 'Sunrise Now' Else $Sunset.Flag = 0 Send Notification to 'Broyd.Email' content 'Sunrise Now' Wait 1 minute Send Notification to 'Broyd.Email' content 'Sunrise Now'

There is a Polyglot Nodeserver for the Autelis for Jandy AquaLink RS in the nodeserver store. The one for Autelis for Pentair was a one-off for a specific user and could not be tested by the developer. However, as carealtor said, it is available in Github. A python programmer could add light support from the AquaLink nodeserver to the Pentair nodeserver fairly easily. Of course, that's all assuming you can get an Autelis. I've been watching a few projects to make an Autelis-like daemon for the RPi. Something like this would be a good replacement and would be better than iAquaLink (takes the cloud service out of the equation). The Autelis nodeserver could be converted very efficiently. Maybe when Polyglot 3.0 is released with paid nodeservers, this will be a worthy project to take on for Jandy AquaLink and Pentair.

May not like that answer, but you probably will like this one: There is an iAquaLink nodeserver in the Polyglot Node Server Store that will run on your Polisy or in Polyglot Cloud (no Polisy required).

I suspect a bot post, trying to establish some sort of cred on the site so it can then feed advertisements to users. As far as bot posts go, it's not bad. ?

How did I miss this?

I would suggest a little bit different structure. It is often the case that you need two programs when switching "modes" results in long running programs. You'll see the two tier programming structure in a lot of examples around on this site. Here you need two two-tier programs (four total programs): A FreezeProtectionMode On pair of programs and a FreezeProtectionMode Off pair of programs. The FreezeProtectionMode On pair of programs consists of a "trigger program" that is enabled and uses a state variable: If FreezeProtectionMode = 0 And PoolTemp <= 34 degrees Then Run Program TurnFreezeProtectionModeOn (Then Branch) Else <--- No Action ---> The second program in the pair is disabled, sets the state variable, and performs the actions: If Then Set FreezeProtectionMode Value = 1 Set FreezeProtectionMode Default = 1 Repeat Every 2 Hours ... The FreezeProtectionMode Off pair of programs also has an enabled "trigger program": If FreezeProtectionMode = 1 And PoolTemp >= 37 degrees Then Run Program TurnFreezeProtectionModeOn (Else Branch) Else <--- No Action ---> The "second" program of the Off pair could be it's own program that resets the state variable, kills any running TurnFreezeProtectionModeOn program and performs the necessary functions to restore the pool to normal operating mode, or it could just all go into the Else branch of the TurnFreezeProtectionModeOn program to keep all the statements together. The other good thing about putting it in the Else branch is that any running instance of the TurnFreezeProtectionModeOn is automatically killed (i.e. any Repeat or Wait is preempted) in favor of the new instance of the Else branch of the program.

There's lots of info online about interfacing an Arduino Uno Wifi with the sonar sensor. There's also code available online to install a REST server on the Arduino. You could have the Arduino constantly reading the garage bay(s) and storing the height of the car in each, and then make that info available through a REST call that the ISY could poll on a regular basis for determination of which vehicle is in which bay. Eventually, it could be a nodeserver in the nodeserver store along with instructions for building the unit.

How about a couple of these connected to an Arduino with a wi-fi shield (or ethernet port): https://www.amazon.com/WMYCONGCONG-HC-SR04-Ultrasonic-Distance-Measuring/dp/B07JJHCVRG/ If mounted on the ceiling pointed down, you could have power from the GDO outlets and it could fairly accurately (~ 3mm) read the height of the vehicle below, allowing identification of the car.

This sounds like the one I was talking about, but I wouldn't consider it "new." It's been out there for quite some time and discussed in these forums. This is the one I called about before I bought my last PLM and was told by Insteon support it wasn't being developed. It was before COVID. EDIT - found it:

Insteon support told me they weren't producing the new PLM (the "PLM Pro," I think). That was over a year ago. We had many conversations here and on Slack channel about it then, as I recall. Maybe we (I) are conflating the "new" PLM (PLM Pro) with a "new" PLM (new revision of existing PLM).

A lot of people of afraid of where, if anywhere, Insteon is going. E.g., if they drop support for PLMs, then where does that leave ISY users, etc. See:

+1 The Range Extenders just work. They don't have to be linked to the PLM that the ISY uses. The only setup is the phase bridge, and I believe that is more of a verification routine then an actual linking between the devices. The way the ISY works (and the Hub, for that matter), is that EVERY device is in a scene with the PLM as a controller. But range extenders are passive devices that operate down at the network level to repeat signals, and thus don't take part in the scene communications of the PLM and devices.

I have Wi-Fi temp sensors that last over a year with batteries. I change the batteries in my wired smoke detectors every year. I'll do a lot to save $80. Hopefully Wi-fi 6 will move Wi-fi for lower power IoT devices forward.

All this technology built into these things and no Wi-Fi? $229 for the sensor and you have to pay another $80 for a hub to connect it to the Internet and use it outside of the Bluetooth range of your phone? If I had a tiny house over a fracking site, maybe, but I wouldn't buy this for my home on the engineering principles alone!

The are in the Installation and Programming Manual available online.

Never done it on a Vista. I factory reset my DSC PowerSeries 1832 with 16 zones, 5 smokes, 3 heats, and 4 keypads and reprogrammed it from the worksheets in an evening. The worksheets were key!

I really don't know much about tuxedo touch keypad. I imagine the 4-wire bus for the connection of keypads to Honeywell/Ademco systems is pretty universal, and is the same four wires as needed for keypad connections to other systems (GEM, Elk, DSC, etc.). As long as the keypad says it supports the panel then it speaks the right language. The main point I wanted to make was try factory reset before abandoning your current Vista board.

It is possible that the panel may still be functional (i.e. capable of working) but that water damage caused problems with the memory/configuration. Before abandoning the panel altogether, I would try factory resetting and reprogramming the panel. You should be able to do this if you know the installer code. The installer code may stay the same after the reset, or may go back to factory default installer code. If the panel turns out to be bad, I would favor a different system over the Honeywell if interfacing with the ISY is desired. The EnvisaLink interface to the DSC Powerseries is far more functional than the EnvisaLink interface to the Honeywell Vista. Of course, then you are replacing keypads too, which makes it more expensive. You could also look at going to something completely different with built in Ethernet connectivity and home automation integration, like Elk M1 or Ring w/ Retrofit kit.

Ok, now we've really gone off the rails...