paulbates

Hi @Guy Lavoie, I do remember you from my ADI Ocelot days! It's part of my ha lineage and a lot of hair ago. I believe udi and the isy will resonate with your Ocelot experience... Powerful yet relatively easy to do and maintain

Integrators like udi, insteon and home assistant are not there yet with matter. Udi has mentioned their struggles with thread. Despite their other successes touted at their 2 year celebration zoom call last week, insteon kicked the thread discussion down the road till next January for their hub and director products. While home assistant has some thread capabilities, their last blog post that I could find is from this past January, where they consider it a beta capability. They ask users not to move away from working zigbee or zwave installations at this time. They also suggest using brand affiliated gateways with the devices selected. To me, the matter standard has a lot of practical barriers to it's own success as something that can actually be implemented to the promised vision of seamless cross manufacturer integration, and we remain in the "bleeding edge" phase. It's on the big manufacturers (Google, etc) and the matter standard committee to get it together. Udi is rightly stubborn about not implementing something that doesn't work and can't be supported... yet.

@hart2hart is correct. The motion sensor is returning to a "no motion detected" or "system alarm off" state before the 3 minute wait in the program completes. The "if" statement evaluates as false, and the program cancels at that moment during the 3 minute wait. A way around this is to make 2 programs: copy the program and call the copy "JP's closet detector 2" Remove the "if" from program 2, leaving it blank remove the "then" statements from program 1 add a single statement to program 1 that is a program statement that calls program 2.. Run program JPs closet detector 2 Because program 2 has no "if", it can't be evaluated as false, and it will run through without the sensor stopping it. If the closet sensor trips again in program 1, that will restart program 2 so the light will stay on if you are in the closet for a while. If you post the program steps as text instead of a graphic, i could copy that and show both programs

I set up my ecobee last year following the instructions... but as it was that long ago I don't remember exactly where I saw the pin. My guess is that it showed up first time on the plugin configuration page after first install and setup. The config page and node page are dynamic when they discover things like new nodes. (I recently added an ecobee sensor that showed up under nodes) @Jimbo.Automates will be able to help

Based on Jimbo's comments in the install docs, it says not to proceed until you have the pin, which is presented at first startup. I would uninstall the plugin, restart the eisy and try again.

That looks like the node pg3 uses for keep alive between it and the plug-in, which can be separate and have just the controller. There should be other nodes that sometimes only appear after reboot or 2 after installing the plugin. Have you rebooted it?

It's a guess; I can't think of a busier time on the insteon network than during a plm replacement. A number of messages to each device to reconfigure them. Sometimes messages don't make it, in either direction, and then they are repeated. My guess is that as iox stepped through each device to reconfigure it, collisions sometimes happened, but the iox code is also retrying what it couldn't finish until it was complete..... and you got a message each time it happened.

It may not be possible for your installation but I plugged mine into an old iPhone charger and a micro usb cable from amazon. Installed it 6 months ago and have not thought about it since.

Open a support ticket. I'm sure you'll get going soon. https://www.universal-devices.com/my-tickets/

My initial eisy experience was similar. Did you try the other USB port, restart?

Np Mike.. that comment was responding to hoosierdaddy, who was asking about scenes vs ISY programs with multiple Insteon commands back-to-back

My comment was sending multiple device commands back to back created Insteon colllsion problems, not scenes. In fact that's why I recommended scenes.

YW. If you do a number of insteon device commands back-to-back in an isy program, there should be a several (3?) second wait between each command to allow the command to reach the device from isy/plm plus the return acknowledgement from the device to isy/plm

Yes, I'm suggesting putting them all in another scene. Elegant is s matter of definition.. a single scene that shuts all devices off simultaneously with very little insteon traffic and no time used up involving the plm or program. A program would not be needed if the scene also included an insteon switch as the controller, which I believe was the op's requirement: Hit a switch at an exit door when he's leaving the house and have multiple inside lights go off at the same time. I had 25 insteon devices in a similar scene arrangement in my last house

If you choose to @Jimbo.Automates, I am interested in the smarthose timer if that could be supported. I went from a 15 zone rainmachine system at my last house to very simple 1, possibly 2 smarthose setup at my current house.

With udm, the occupancy setup on the portal is no longer needed. You create geo fences with the app and they'll appear a nodes on the isy. You do need an active portal subscription.

Sending that many insteon commands back-to-back will create collisions on the insteon network, doing it 5 times will be worse. If they are all insteon devices, you can create an insteon scene for this and no program will be necessary

(#1) 2. USB plm... Plug it into the USB port on the eisy. Conversion cable only needed of you buy a serial plm (#2) 2. Yes. But it would be best to plug in the plm to the USB port on the "out of the box" eisy, start it up and see the plm connected status prior to attempting the replace plm procedure. I had to restart the eisy a couple of times initially to get there (#2) 3. It won't hurt to have text copies of NRs, but I'd be more hopeful about the ISY restore

My experience with several on/off outlets is that line noise from the load can damage them if the length of cable is to short. Possibly putting a filterlinc or a filter cap in the device will help

I had low voltage lighting at my last house and had to filter every transformer to get them to work right. I used the old x10 xpf filters, but they are big.. The insteon ones look more workable in a j box

Review this post and give the suggestions a try https://forum.universal-devices.com/topic/24381-iox-launcher/

Is it more likely the low voltage lights turn on ok, but not off? It's likely that the low voltage transformer is creating noise when it's turned on, interfering with the switch's operation. Is there a way to remove the transformer temporarily? if that's possible and test again to see if the program works. Insteon offers some filters on their sites that you can wire in to the outlet that services the lights

Depending how many, you delete all of the scenes, and then the switches from the ISY. Use the set button method to manually link them... that's the complete/sure way. FWIW I sold my house last summer with the same concern. I left the ISY... removing the more complex integrations. Left a google doc with the basics... brands, logins etc. I created a "house" gmail account that the portal, rainmachine, Venstar thermostats used for their online account; that was turned over with the doc as well.

I had a related kind of problem a few years back. Its a problem with the Insteon device with the address 27EC8F First, see if the device is working, configured properly, look at the options. Is it an iolinc? My similar issue was with an iolinc. Here is the thread

Tinymce is an editor tool kit that can be served up remotely. UDI is using this toolkit to deliver the portal. The message appears to have no effect on how the portal operates. I went in and edited my ISY contact info... was able to and it saved. I would say ignore it, unless a functional issue has been found