paulbates

How old is the plm, from approximately what year? I'd start with unplugging/replugging. There are more detailed diagnostics to try later, but in my experience if that simple tests restores things to normal, then your plm is on it's way to dying

FWIW I use a couple original lamplincs from my last house on my eisy that got moved with the Christmas decorations that they control. They look a little clunky and discolored by the sun, but keep working.

For Insteon, the ISY/eisy is the "system of record" for all Insteon network data. That makes restores possible and is good, unless something happened to that data during the migration, and that could explain your difficulties. A quick way to test this theory is to pick a non-working module with very little programming / integration associated with it; delete it from the eisy and re-add it at the same location. Retest.

The range extender cannot be added to the isy. A few other things to try. Move the range extender to other outlets there if any and retest Temporarily replace the range extender with a lamp or appliance module and retest. They also function as i2 range extenders

(2) Haven't tried it on the eisy, but give this thread a try. Looks like variable substitution might break it. I used HAD pages served from my ISY's web server and accessed them through the portal, but many years ago.

Cloud always downloads the right AC/iox for your firmware

When you click on your eisy using start, a menu pops up. Do you pick "cloud"? If not you should

No. Go ahead an try it. The comment was that there is a limitation to the togglinc compared to the keypad that might or might not affect it's operatio in the location you're installing it

That approach sounds fine. With a but: Togglincs are powerline only, so you'll need to have good insteon powerline comms at that location for the switch to hear from the isy/plm

FWIW, I have an ISY/eisy folder where I put things that I don't want to see. Call it unused, etc. then you won't see it

When I sold my house last summer with insteon, i left all of the things that were 3 way & switch type things working, including the garage door. There were isy programs that "helped" the venstar thermostat and rainmachine sprinkler controller.. those work as long as the isy does... But... those 2 devices are standalone and will function ok with out the isy. Some timer on off programming would just cease to work like timed yard lights... But there are hard insteon switches for all of it, so there is a way to use it Long way of asking, is the new homeowner truly stranded?

I did something similar at my last house as it was a detached garage where the door could not be seen, and at the time with kids in and out, or even me, it did get left open. 2 comments I believe you can do it all with one program. Put the "then"s all in the first program.The only edge condition would be if the door were to be opened at 6:50am or later.. then it would not complete. My guess is if that happened, it was an unusual case, it was on purpose like you're leaving early for some reason To follow the comment under 1 above, what happens if a family member goes out to warm up a car early to leave in the winter (Doctors appointment, drop somebody up at the airport etc),, is 10 minutes enough? Wouldn't be for me, but something to think about. I finally changed the approach. The garage door was opened with a keypad button that would light up when the door was up... that helped a lot. After a certain point in the evening, the keypad would beep every 20 minutes if the door was up

Non prod 3.0.1 Prod 2.0

It's not stated, but it sounds like you followed the replace plm procedure? Any problems or errors when doing so? Can you pick one device involved in a scene problem, ideally one that might locally trigger a scene, right click on it, pick "Restore Device" and test again?

The 2 "Add devices" buttons are the "craw your network" options under start linking. Sounds like you had a better experience than me with this, so maybe you'll want to try it. I pretty much had to delete and rebuild scenes from scratch, but if you don't have a lot of scenes, especially big ones, maybe it will be ok. I think you have to start by pressing set of a few devices, its no smarter than the things it finds in devices. But its been about 10 years, so don't remember exactly.

Yes, for my new-to-me house, I started last fall and have a google sheet with all Insteon devices and info. Granted for i3 devices its relatively easy to get from behind the faceplate You can have it crawl the network, but I did that when becoming a udi customer in 2014. It created a mess as I had a lot of scenes and would do it that way only as a last resort. To add by address: Link management menu New Insteon/x10 device Use a . Between Insteon address octets: eg 01.02.03 While I tend to do it that way, in your case pushing the link button could save a lot manual work pain. Get a friend/child with a cell phone or walking-talkie and have them press. I'm pretty sure you can do multiples too... you can "Start Linking", go around and press and i will batch them up for one press in the AC/iox to add them all. Though I think devices only stay in linking mode for a few minutes... maybe room by room or floor by floor

It works for me. I also have an "Operational Log" pushover app and everything that goes there is silent - no chime or vibrate. I only use "Send Sys Custom with Params"

This is the link to the wiki for eisy. Per tehcman's post, when you scroll down, the eisy docs point to the link to the ISY Cookbook for docs on admin console/iox.

FWIW, All normal here, normal "respiration" of the getting updates from yolink things. Nothing in the log like the messages you posted.

I did the latest iox updated prior to experimenting with virtual and restarted. I then installed the virtual and restarted. Based on the above posts, I restarted again, and now the virtual device controller node has one value of "connected" which sounds right. The 2 things I defined didn't show up, and I want to remove my isy ip, user and password. I should remove the plugin, delete the nodes and start again.

@Brian H The on/off module precedes the 994i sunset and should work. But to your point about the inline and micromodules; better to know for sure if the motors can be dimmed. Mine were buried in far away and hard to get at places. Its better to use an on/off micro module to do it once.

There are several different micro module products from insteon.. One of them is an on/off relay I use to control a kitchen fan. If your requirement is on/off only, I recommend that one.

When I had an ISY and nodeservers on a pi that was important. I'm on an eisy; \ 8080 for http, and 8443 for https. Wasn't anticipating that level of config change for a plugin install.

Already stumbling a little. I got to the nonprod store and installed, isy,user and pw working.... I'm not getting what to do with this: Key (var ID) Value (device type) 78 switch 79 dimmer or generic 82 temperature (will be displayed as farenheit) 85 temperaturec or temperaturecr (will be displayed as celsius) (the r can be used to note raw data if you prefer) If I pick a state variable I do have, 15, and type temperature as the value, I get a switch showing up in the ISY I tried literally putting 82 as the variable as a long shot, I know that makes no sense... I don't have a variable 82 so it didn't help. It's not clear to me how to map the virtual device into my ISY variables (all are state). The Virtual Device Controller and my 2 defined devices all look like this:

2 ideas on the portal Web page There's a little icon with 2 concentric arrows pointing at each other on the right.. Click that.. Did that help? On the tools drop down, pick Information/portal access troubleshooting, it's meant to walk through things like this If those don't help, if submit a ticket. Switching CM MAC address several times may have caused a security issue or confused the portal