MWoods329

FWIW, I've had a PLM with serial connection work on a 30 ft run of CAT6 just fine. When I had the USB PLM, I tried the 50ft USB and couldn't get it to work. Also, I tried an active USB extension over CAT6 for 50ft and couldn't get that to work either. Serial was just the way to go for me.

I have a fairly vanilla network setup, running a pfSense gateway and Unifi APs. What should I be looking for that would interfere with auto-discovery?

Also, it looks like you have to change directories to storage before running the script. From a fresh terminal, try cd /storage then curl -s https://pkg.isy.io/script/create_ha_vm.sh | sudo bash)

What do you get when you run "zfs list"?

Hey, it looks like there hasn't been much activity here in a while so I hope this hasn't been abandoned. Following the PG3x upgrade to v3.2.30, I ran into an issue getting the nodes discovered. There's a whole chronology of the saga I wrote up here: But what this all came down to is: after this upgrade I had to manually add each node for it to be recognized. Is this a familiar scenario to anyone else? Not just this version upgrade, but has anyone had it in the past? B

Thanks. Guess I just got lucky.

Yes, was on 3.2.19 and was working fine there. Will do. Thanks

About 20 minutes after I added the node manually it started functioning. Saw a rapid on/off like it was catching up on all of the missed attempts then just started functioning normally. The rest still don't work.

Just upgraded and MagicHome is no longer working. PG3x shows all nodes in its configuration, but IOX cannot connect to them. Eight nodes shown No attributes in IoX Attempting to call one of the nodes from IoX (mobile app) shows an "address does not exist" error in PG3x: In an attempt to correct this I manually added one of the nodes in PG3x (mac, ip, name). When attempting to call that node from IoX (moble app), it gives a different error (socket connect failed): Reinstalling the plugin made no difference, rebooting eISY made no difference, rerunning the upgrade made no difference, etc, etc, etc.

Took quite a while and when it finally finished, it didn't restart PG3 after reboot. I couldn't figure out how to independently start PG3 so I manually rebooted the device and now everything appears to be working fine.

I can’t find the gray paddle change kit anywhere. Does anyone have one that they want to sell?

Hey @Javi did you get a chance to try this out?

That's what I needed to hear. Thanks!

I started down this route, but ran into not knowing how to get a neutral line over on the right side.

Not all of the whites are tied together. That might be just my terrible drawing skills. The white from the 14/3 (left box, lower right set) goes to the switch.

Yes, I’ve set up a dozen virtual multi ways in the past. That’s not the question. The question is how to determine which wires are which?

I have this new (to me) house which for the most part seems to have updated wiring. This was great for the few rooms I've put my Insteon switches into up until I got to one room which has a ridiculous number of multi-way switches. This is my first.... So the kitchen light is a three way. One box (let's call it the right one) only has red, white, black, and ground. No neutral or any other leads. The other box (let's call it the left) has three sets of Romex coming into it. Only one of those contains three leads. I need to put a KPL into the right box and a regular Insteon switch into the left box (see my sloppy diagram). What things do i need to test for, or what do I need to determine in order to get a neutral off to the right box without adding any wires?

Factory reset and manually adding it worked. Thanks!

If I just use the path Link Management --> Start Linking, the linking process just times out. Log shows: Sat 09/02/2023 02:47:09 PM : Start Insteon Device Linking Mode Sat 09/02/2023 02:51:18 PM : Stop Insteon Device Linking Mode, Final processing to follow And then nothing. Device is never added to the eISY console. If I use the path Link Management --> New Insteon/A10/X10 Device, and enter the address of the device, it also times out but gives the error: "Cannot determine Insteon engine". Both the PLM and the i3 KPL are on the same circuit, a few feet apart. Any ideas where to start with this?

I’ve tried both. Same result.

The Zmatter hardware is the dongle connected to the eISY. It is the only device connected to the eISY. The Zooz hardware is the multichannel device sitting across the room that I'm trying to include in the Zmatter's network.

This is a Zooz 700 series. Yes, I have the Zmatter hardware, Zwave enabled and other Zwave devices already functioning. When I add a Zwave multichannel (even the same device) via the Admin console, this behavior does not happen. But when I add any Zwave multichannel device from the UD Mobile app, this happens.

Anyone else tried to add Zwave multichannel devices from UD Mobile? A bit of back story: a while ago I had an issue with adding Zwave locks from UD Mobile, but attributed it to being pretty far away from the Zmatter dongle. But just recently, I tried adding a multichannel zwave device that was hardwired and within several feet of the dongle and still had the same issue when adding from UD Mobile. The actual event: generally speaking, everything was looking like it worked from the UD Mobile app. I went to Admin --> Zwave --> Add and put the device in inclusion mode. But when I pulled up the IoX Launcher a few minutes later to see the new device, it was still busy adding. And it wasn't just adding the lone device I had attempted to include, it was re-adding the same device under multiple nodes. For the one device I tried to add the Zooz 700 Relay (https://www.amazon.com/gp/product/B096LLL1C6/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1) it had added over nine times and was still going. I tried to use the Zwave -> Advanced -> Stop adding but that didn't stop it. Eventually, only a reboot stopped it. I took a screenshot part of the way through and collected all of the logs just in case someone smarter than myself could tell me what was going on with that. ISY-Events-Log.v5.6.4__Wed 2023.08.16 09.37.49 PM.txt

But regarding the ES1 - I have it. It’s Zigbee. I was able to connect it over Zigbee with the ZMatter dongle (but the only thing it did was print an error log that it’s not compatible yet).

Oh damn. I didn’t realized they made that change in version 2.