hart2hart

Not much I can do to help. You said you’d installed latest FW. FWIW mine are at 6.93.

Can you ping the thermostats from the Polisy?

I wasn’t suggesting your WiFi was not password protected. I was suggesting they might be connected to different SSIDs and one of the ssid was setup on its access point without choosing encryption in its setup. None of mine say http.

Did you just turn them to enabled now and they still don’t discover in plugin? If so I’d find the option in thermostat menu to restart them. Are all three joined to a secure WiFi access name? If the one saying http is not it sounds like it’s saying secured access is required.

I have latest firmware on mine and use the skyport app and via the plugin. It’s been years since I set it up using nodelink and then migrating them to the Venstar Ct plugin but all I recall was having to authorize the local api. On thermostat it’s under WiFi enable local api. Probably can do it via skyport app too.

I’m not at home but if you select ISY, do the devices in the right hand pane show all your devices?

If you click on ISY, I believe you’ll see all your devices.

Try the three parallel lines above Home.

Whole House:Query All - If Time is 3:30:00AM Then Set 'My Lighting' Query Else - No Actions - (To add one, press 'Action')

Yes it’s called Restore PLM in the admin console and there are steps as I recall to power off eISY, replace the actual PLM and then to run Restore PLM. It then goes through each device and replaces the PLM address in all your devices including battery operated but have to wake them up to process the changes. However if you’ve done part of it manually, you may want to open a ticket and consult UD to get advice on next steps.

Did you use replace PLM?

As I recall, in the last year there was a major OS upgrade and there were cautions on jumping many versions. Unless others chime in, I’m thinking you will need to contact UD via a ticket to get it in back in working order.

I’m excited at ability to write programs in English and I was a long time programmer.

As I recall, later Insteon devices support the scene devices having repeat option so you might look into that. Not certain how it applies when eISY is the one issuing the scene command.

Not my area of expertise as I have small zwave footprint but have you run the zwave option to repair network? If not, you need to do it several times so zwave devices “neighbors” are sorted out.

Yes. I used them form eISY with the PG3x Schlage node server/plugin.

I’ve got Schlage encode plus deadbolts which are WiFi and thread with an Apple TV as border router. I use them with Schlage plugin which leverages a cloud api. They work great for me. Battery life has been 6-9 months.

You should be able to access it via eISY.local from your web browser. It a work in progress and is not ready to replace all of AC yet. That’s assuming your eISY is up to date.

My PLM is several feet away from eISY to get it away from RF storm of equipment so I’ve stuck with serial to extend it via twisted pair cat5e cable. Likely just as effective with usb but just haven’t done it.

Sounds like you need to open a ticket with UD.

Are you running wired (is there one or two Ethernet ports on it) or wireless? The individual interfaces will have different MAC addresses. Of course it could just be a misprint.

Thanks, @bmercier . Yes export configuration sounds great. I got most of them going back 15 years (which is excessive) and have referred to them many times. It’s been mostly research but something went wrong with programs a few years ago and I was much more comfortable using program listing to repair than restoring a backup. Have a great week.

Have you tried to ssh to eISY using something like putty? Also, try eISY.local from browser to see if eISY-II is reachable.

Thanks.

Again thanks. I thought you might be saying an eISY variable exposed to Alexa as a contact closure was at one second compared to an actual Insteon device exposed to Alexa. I believe you meant a variable triggering a webhook was one second. Do I have it now?