paulbates

I didn't read the entire thread, so if you haven't tried, in this order: Unplug / replug PLM. Restart eisy, check again Factory reset PLM, check again, if connected, restore modem

I hosted automation based pages on my 994i where I ran the Home Automation Dashboard, HAD. Here is a link to look at You can use terms from this link to search for more. It does mean opening a port on your router for external access... I decided a while ago to stop that across the board FWIW

Thanks, that was the question

Hi... it's not clear on the order of next steps. Should I go head and upgrade the yolink plugin now, prior to the next PG3x release, even though the current PG3x release doesn't support python 3.11?

10% may not be a good value for the fanlinc light switch. You need to validate that this setup can work and at what level before writing programs, Alexa integration, etc. Did you try using the UDM app or iox to manually apply different percentages (90%, then 80%, 70%, etc) and visually see what happens to the bulb?

Doesn't have to be voltage, just an indication that it's low. Thanks for looking, it's a nice-to-have but not critical

The insteon switch might dim differently. What happens if you use udm or iox to dim the light at different levels? Then run the same kind of test on the scene. Can you post a pic of the scene.

A low priority, but is it possible to present the ecobee's remote sensor battery level with other sensor data?

Does it show right in AC/iox? If it's a switchlinc, it's older. Have you tried pulling the air gap switch, if it has one, wait 10 seconds and push in? If that doesn't work, factory reset it and right-click in it, pick restore device

When I set up my eisy (new setup) I had the not connected problem. It took an unplug/replug (or 2) and then showed connected and that was the end of it I'd try that and see what happens with the green update icons. If still there try right clicking on one and pick "write updates to device"

2) Replacing the plm:

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.

(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

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 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.