paulbates

To 'smoke test' the line noise theory... If the iolinc is one of the non-working devices, are you able to temporarily unhook it and plug it into the same outlet as the PLM and repeat the test?

The green arrows point to communication issues with the device. It might be that the keypad needs a factory reset (pull out tab and wait 10 seconds, push tab all the way and hold until it beeps). Then, restore device. The other method is to use the admin console in Linking Mode and go to the devices one at a time and press the set button quickly.. the devices will show up in the admin console and you follow the prompts there to finish You can right click on the remote linc and click delete device, but I'd do that after you get the keypad working

I owned a rainmachine at my last house and the connection is local api. Before the current plugin was written, io_guy supported rainmachine through his nodelink node server and that was local. &nbsp The rainmachine is built on android and its webserver provides pages to configure the rainmachine locally. My recollection is the the full URLs and port numbers were specific.. I believe :8080

Open a ticket with a link to the is thread https://universal-devices.com/my-tickets

You can buy new lamp or on/off plug in modules and experiment with placing them in different locations... They are dual band and will improve Insteon in places where it can't reach. IO lincs, including new ones, are powerline only

It could also be that the plm is a lot way from the electrical panel. Try to plug it in to an outlet that is closer to it so it's closer to the center of your electrical system

I'm not 100% clear on the setup... but what about this: Buy a wireless router with the multiple ET ports that has wireless bridge mode I bought a cheap plug in the wall one for my wife's mother's retirement community for similar reasons, but she did not need ET ports.. probably a router in your case Log that into the community's wifi, that has to be their intention If not, how will they know? just give them the internet wifi MAC address of the router The router will have a dhcp server to provide NAT IPs and internet to all of the devices you list Wifi or ET will all be on one local network and will talk to each other If you can't find something that provides wireless bridge with ET, get wireless USB Nic for the PC My RV has a device called wifi ranger which is used for similar purposes.. it logs into campground's wifi and and provides a hotspot for my devices... though I don't think it will support ET port. A good community to get specific recommendations is snbforums.com (small net builder)

Sometimes my individual node servers restart, one in particular and I get UDM notifications. Other times the portal disconnects. But it doesn't cause loss of node values that I'm aware of. Where I'm going is, could what you're seeing be isolated to individual node servers that are restarting and not the entire eisy?

This happens occasionally with major upgrades. The best bet is to use UDI's responsive support: universal-devices.com/my-tickets/

It looks like 2 things were going on at the same time? Replacing a computer that's used to access iox/admin console Replacing PLM. I'd recommend dealing with one of these at a time, and start with 1 I'm not familiar with copying files as part of moving to a new PC, the necessary files and data are in the ISY9994 Uninstall java Reinstall java Clear java cache Download the latest launcher Review this post for specifics Once you can access iox/admin console on the new PC (1), then we'll move on the PLM (2)

Logs are going to help of the time this happens: The general ISY log Event viewer, set to level 3 Logs of the ecobee plugin, set to debug level log EDIT: Any chance the kitchen 3 way is a scene, and somehow ecobee is in that scene? Review the members of that scene. I know sometimes my "mousing" of iox can drag and drop to the wrong place

There's 2 methods. One is linking mode. The other is to add a new Insteon device from the linking menu. You need the six hex digit Insteon id, formatted like this 12.34.5A. It could be digits or the letter A-F. Its found on sticker on the front of the switch, you'll have to take the faceplate off. When you do this, conversation starts with the ISY and there's nothing to do at the switch end. Typically, it will beep when the ISY contacts it. Try that from the linking menu.

It's a communication issue or a dying switch. Since it's single band, it's more vulnerable to line noise... new plugin transformers, tvs, fans.. could all be contributing to this new problem A new dual-band switch will help, but not necessarily fix the problem without eliminating line noise as the problem; this is more involved to exactly isolate A new switch is $55 +shipping, I'm trying to imagine how much less a repair would be compared to just replacing a high use, older device... repair usually means replace capacitors, but not the physical plastic parts that wear down with use There is a replace function, but it's highly sensitive to replacing with the exact device. It would probably work but there's a chance you'll have to visit scenes and programs if it doesn't. Usually its not that bad to do. If it were me, I'd replace an old, single band highly used device. If comm issues persist, post back and we'll step through it.

For submitting the ticket, do you have ad/content blockers on your browser? Try again in a private window or turn off ad/content blockers for universal-devices.com... or try a different browser

Do you use the blue UD icon that is installed on the desktop with the admin console? If you click that, it will bring up the launcher locally from the java cache. When you click on your ISY, do not pick the cloud option, and it will work locally from java cache. Look at this post for the step to restore the blue UD icon if needed