paulbates

You don't have to link each one if you added it through portal and your account is linked. Are you up to date with your portal subscription?

I did the same after Nodelink stopped being developed. Nodelink actually had that humidex feature/capability built in for Venstar years ago and it worked great.

1- This is typically done with smart thermostat, I've done that with the venstar colortouch and ecobee. 2- The alternative is to get a zwave on/off outlet or on/of plug-in module and plug 12 volt ac plug-in transformer (hardware store) to it, and wire that to the humidifier's water control actuator. Based on humidity levels from openweathermap, turn the zwave outlet/module on or off. I'd be careful with that as the sole source of data, I'd want a zwave humidity sensor (assuming that it exists) to confirm the actual building humidity.. have some iox watchdog programs to not let it humidity levels get "outside the box'

You want to be in linking mode first, so that the PLM/ISY catches the Insteon traffic from the device(s) being put into linking mode.

Try right clicking it and pick "restore device". Per @Guy Lavoie's comment, if it's a wireless device, put it in linking mode first

On Windows 10, it remembers for me. I don't have this issue I backup up based on material changes that I make to programs, configuration or notification settings. I would not backup unless a change has been made

It's discussed here: https://forum.universal-devices.com/topic/44142-nest-plugin-marked-inactive/

Since I've had eisy, this has behaved differently at different times and versions. Now, it sometimes can take 20 - 30 seconds to come up.... others right away.

It seems within the last couple of updates, one of the 2 advertisements was dropped, probably to eliminate the confusion of having 2

It's port 3000 for eisy / pg3 http://"eisy IP address":3000 You'll want to continue to access the pg2 on whatever you were running that on, on its ip address, not the eisy's.. rpi?

To add to @DennisC's great answer, UDI offers consulting help. It would be a good idea to buy that and let them remote in and evaluate and propose an higher level migration plan for you. Scroll to the bottom of this page. https://www.universal-devices.com/store/#top-row

Glad to hear you're working The capacitors can be repaired if you're good with a soldering iron and working on electronics. If not (I'm not), I would dispose of it

Can you post 10 - 20 log entries, especially ones that repeat?

Hard to say for sure, but relatively easy to eliminate as the culprit.

It's possible. I believe the admin console steps through the list of devices and won't avoid sensors unless that battery option is set. It's easy to try and see if it will complete.

I have had great experience with couplers. I had a signallinc from Insteon at my last house. Now that they don't make them any longer, I built my own from parts I found on mouser from a recommendation from Insteon for my new house . The parts were like $15 delivered. They have to go into your electric panel, so you have to be comfortable with that or find an electrician to do it for you.' If you're interested I can dig up the order from mouser

Do you have battery devices like motion or door sensors? Those have to be individually put in set mode for their turn. There's a little battery icon with a +/-on the top of the admin console you can click. It will avoid all battery devices so powerline devices finish. Then you unclick it and do each battery device one at a time

To add to @Techman's comments... outdated firmware means that it's i1, not i2 Insteon protocol and it wont support more modern Insteon devices, or not as well as they should be.

It's probably worth a factory reset it. Press the set button in and hold it till it beeps. Then go back and put the eisy in linking mode, and the go tap the set button quickly till it beeps.

For X10, enter the house code and unit code, eg C14. For Insteon, use the "Start Linking" option under the linking menu, and then press the set button. Do it order, or even one at a time if all over the house to keep it straight... or have a helper with a smartphone or walkie talkie to help keep it straight

I would order it from Insteon. I think the USB is cleaner, but if you have the cable and your eisy is already configed for it, serial probably makes sense. This is the procedure You would back up the eisy first. If your PLM is dying there may be some polluted links in the eisy's Insteon tables that will get backed up with it... usually fixed with individual "restore device"s based on which ones have problems. Also wireless devices have to be put in set mode and restored individually

That's an old PLM... 21st week of 2016. And if memory serves me correctly, 2016 was in the era of bad capacitors = bad PLMs. I'd order a new one and replace it on your terms rather than when it dies at an inopportune time You have a backup from right before you set up your eisy? When you get a new PLM, I'd restore that backup to the eISY, and then "Restore PLM" from that backup. Also, if your PLM is with in 15' of your eisy, you can get a USB PLM

It's never a bad idea to suspect a PLM 🤪. Seriously, the age of the PLM matters. Can you shoot a picture of the back with all numbers/IDs/stickers shown and post back here? Also, I would: Unplug the PLM, wait 10 seconds and plug back in Repeat the eisy power on/off.. did it report the same problems? Run the "4 tap test" on your access point or other plug in devices. Go look at your Insteon devices and see how they respond to it. Keep track of which is on which power leg, that will help with the next recommendation below. Start keeping track of the devices it reports in the messages, look for commonalities like which power leg they are on.

From an older manual https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order Another one: https://forum.universal-devices.com/topic/6507-program-order-of-execution/

This appears to be an out-of-the-box eisy problem. It happened to me fall of 23 when I bought mine, and there was recently someone else with the same problem. The answer is to leave it alone with the programs as written and give it a day or 2. It eventually starts working right and the problem will not return