paulbates

That's done through the scene and it has to be edited.. I don't know of another way

In addition to providing Insteon programming, the ISY manages Insteon configuration including scene management If you haven't removed the old switch, open the scene you are talking about under Main in the admin console. Right-click on the old switches entry in the scene and pick delete. (There will probably be an error due to the old switch not responding, just move through the errors) You can then right click on the old switch in the ISY and pick delete Install and add the new switch to the ISY Under main, click on the switch and drag it to the scene name and drop it. Make sure to click "controller" in the window that appears and then complete That should do it.

So do the following: Box 1 Upper right black/white wire pair. White to white bundle Black to Insteon switches red lead, cap together Upper middle red - cap off separately black to black bundle White to white bundle Insteon switch Red to upper right black as noted above Black to black bundle White to white bundle Turn on breaker and test... do the lights come on? If yes, add the switch to ISY Configure as dimmer if its an i3 and you want a dimmer Box 2 Cap red from box separately on its own cap red from Insteon switch separately on its own Black to Insteon switch black White to Insteon switch white turn on breaker, does switch show it has power, leds light up? If yes add switch to isy make it a dimmer if i3 and needed create a scene and put both switches in, setting them each as controller Test everything from both sides Push wires in, mount switch, etc,

Insteon makes a noise filter that the UPS could be plugged into so you can keep everything there. It is bulky like PLM so maybe a short extension cable too... or I use a one outlet to three outlets horizontal adapters to fit my PLM in with lamp module

If it happens again, I would unplug the UPS temporarily, and unplug/replug the PLM... and wait to see if it reoccurs. UPS's can be a powerline noise problem and affect Insteon devices.

Seems odd that a 6 month old PLM would need this. Have there been any eletrical system anomalies; brown outs, low voltage, etc? Is the PLM plugged in electrically near something like a washer/dryer, window air conditioner etc.. something that uses a lot of power?

It appears that light fixture is coming into the first picture, down on the top right with the black and white wire. The left box is the j box that inteon switch controlling the load with its red wire will go.. red on the switch connecting to the black on the upper right. But.... I'm confused too, why black is connected to white on left wire nut. You're sure about that? The Insteon switch in the other box will not be happy, and likely not under warranty, if the black and white are backwards.

Before giving the PLM an "all clear", how old is it. To complete your list of things, I would unplug it, wait 10 seconds and replug in, re-run your tests.

To add to techmans comment, It's much more responsive when you put the sensor in the scene with lights. If you haven't already, change the settings so it's "on only", no off messages- so it cuts down on transmits. Also extend the amount of time it waits to retransmit, make it close to the time you have it stay on... this also cuts down on transmits and extends battery life. To get it to turn off, I have the scene turn the lights on, and than an ISY program "wait" x minutes and turn it back off. I sold my last house recently with the MS1s turning on the driveway lights, they were at least 5 years old. One down side of adding existing MSs to a scene is that you'll have to get to them and press the set button to get it to work.

I asked recently on the Insteon Forum, and "Insteon John" provided the schematic for the signalinc with the parts listed. I made my own. Follow this link to the Insteon forum, and scroll down to the bottom, I provide the parts list from mouser.com there. It's 2 very small parts that can go in a single gang work box on the side of the panel. An electrician can do it if you don't want to. If you have one meter then I'm guessing only 2 legs feed the house and only need to add one of these. You could try with one and see what happens. But if you choose to try, buy 2 sets of parts... the shipping is more than the parts.

From a recent discussion with yolink support about local API: " 2. We understand the importance of local API capabilities, and I'm pleased to inform you that a Local API is expected to be released by the end of this year. Waiting for the local API could indeed be a beneficial decision for your application, providing a more streamlined and responsive solution.'

Mine says "Rev 2.7 2023". I bought it in October 23 and as we discussed the other day, pressing the All On button in iox had an effect on more devices than it should. Knocking on wood as I say: "I no longer have phantom ons or offs". I do have the potential for them

No, sorry I may have said it to wrong. I was in support of your comment, and agreeing that they respond to their user base... we're all good. 👍👍

I am very impressed with the responsiveness of yosmart support. I've found a few things wrong and the app and they have acknowledge them, as well as acknowledged feature requests. I realize the path to implementation is longer, but I really appreciate not being sent generic links to generic solutions. I asked them recently and got the opposite response, there are new features but not local api for hub 3

Thanks, this explanation helps me. My first application is an 8003 TH module in the bathroom to activate a vent fan. I used the app graph and log data to determine the "slope" for humidity increase for iox programs to know it's the shower being run vs ambient humidity changes What the sensor shows, the app shows and the nodes in iox can be different things, following each other. I get that the sensor doesn't update the cloud right away, but I've been watching its operation, and I think its natural time gaps in sensor->cloud, and additional gaps cloud->plugin & iox. This is not a complaint and I don't have enough data ready right now to report. This plugin is a great thing and I have plans to expand my yolink sensor network, especially now I know what to expect.

It happened to me at my last house. In 2007 ish I bought original Insteon devices and used in x10 mode and eventually migrated. Some were re/de-programmed successfully. Some were buried, like inline lincs in the ceiling or attic and wasn't going back up there to press something to reprogram x10. Other times I got unexplained X10 in my log but given my x10 origins, I just programmed around it

Insteon devices haven't supported X10 for a number of years. See this comment from Insteon from 2016 as a point in time reference. Start with the oldest devices by model number and FW version to see what you can find.

If you look at the 2 screen shots in the Insteon forum post, those show the difference- # of hops before and after throwing the breakers for the signal linc. That was my last house where I had a number of dual bands. That screenshots are of the homeseer plugin, from homeseer that I no longer have. I don't have homeseer at the new house, but I did use the event viewer and on/off and query every Insteon powerline capable device several times after the installing the parts. Everything has 3 hops left almost every time. Maybe an audit of ~5 devices and try that yourself.. but also add any problem devices like micro module.. how many hops average?

The AC wasn't available to me at the time to report the FW versions of recent devices that "All On"-ed 2450 iolincs .41 Micro dimmer 2442-222 .49 Siren 2868-222 .46

Signal linc 2406h. It's a hard wired insteon phase coupler https://forum.insteon.com/forum/main-category/main-forum/118349-does-a-compatible-phase-coupler-still-exist

While I've not had an "all on" event, I took the challenge too see what would happen based on another thread here.. and pressed the iox "All on" button on the main view. What I observed that responded, all recent model micro dimmer alarm module 2450 / io module What did not respond: I3 paddles and outlet My installation is eisy/iox and everything is new as of last October. The light controlled by the micro dimmer started occasionally coming on randomly, every few days. I first thought it was the i3 paddle that controlled it as it always worked properly from eisy. Brightening/dimming with the i3 paddle occasionally had jumps and flickers, where 2 lights of the same brand/type connected to the i3 paddles load did not. Unrelated to this happening, I was given the parts list for the guts of the old signal linc on the Insteon forum, got them from mouser and installed. It was a few days before I noticed: that was the end of the random ons from that one micro dimmer' that was early December. The dimming isn't as exact as the load on the i3, but nobody but me would notice.

Another possibility is that the wrong port was selected to plug the cable into the acadyan. The deco's WAN port should be used to plug into an acadyan LAN port (if there more than 1). it can have yellow coloring If the wrong port was used, both DHCP servers would be active on the LAN and explain the symptoms

I asked them directly about local API recently in reference to the new hub 3 and got this response with no comment on local only support:

There's a number of moving parts here. After connecting and starting the isy, Can you look at the connected devices on the acadyan, is the isy there? Most routers have a page of connected devices and DHCP assignments Same for the deco I'd do ping tests from other connected devices and see what their subnets are and can they ping the isy Can you look at that and respond back with that info?

I recall others doing this in the past. It's not particularly pretty, but can be done... assuming the rest api has not been deprecated. You could push device states and variables back and forth with Network Resources with substitution {,,}. If the shop will not be changing frequently from a device perspective, it might be worth it. Pass variables back and forth for a few devices/functions you want to control or monitor from the main building. https://wiki.universal-devices.com/ISY_Developers:API:REST_Interface Scroll down a bit to devices and variables. I've done the variable setting from my own python programs, it does work well. Here's a related how to for zwave