MWoods329

Impressive, as always. I have a few notes, but they read a little bit like I'm an idiot. Am I missing a tutorial on how to use the web interface? 1. Scaling isn't great on smaller screens 2. I wish the node list was fully collapsed when I opened it instead of having to scroll through and close everything just to check if all of my nodes were there. 3. While we're talking about the node list... As I was going through and collapsing them, they would all spring right back open at once after being collapsed for a few seconds. It didn't happen every time and I can't seem to reproduce it intentionally. 4. I am so happy I can sort on all of the columns in the Node page, so thanks for that. 5. Node search function works pretty well too. 6. Showing nodes in their folders is on the roadmap, right? 7. The "Home" link and the fold out menu link for "Favorites" both taking you to the same page is a little cumbersome. 8. Trying to set up a tile on a new dashboard and.... only option is Default Tile? Then why is it an option? 9. I guess I would have expected that to add all of the channels of that i3 Keypad when I selected the main. 10. Loading with an error that prevents it from being usable? I think we have different definitions of success /s 11. Tried to edit that widget to see if it's a property that I can change, and I was surprised to see that the widget is allegedly including all buttons. 12. I tried adding the rest of the nodes for that keypad and editing the commands and properties, but there were none available.

Install: sudo sudo kg install -f eisyui-0.4.1.pkg Is there something secret about the double sudo that I don't know? Also, what's the "kg" thing? 😁 ps - it did actually take me a minute to realize what the kg was supposed to be.

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?

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.

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

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.

Aqara Presence Sensor FP2 https://www.amazon.com/Aqara-Positioning-Multi-Person-Detection-Assistant/dp/B0BXWZMQJ3/ref=sr_1_1_sspa?crid=2WPBKDELB3DH5&keywords=mmwave+presence+sensor&qid=1691579971&sprefix=%2Caps%2C78&sr=8-1-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&psc=1 Linptech Presence Sensor ES1 https://www.amazon.com/Linptech-Presence-Automation-Compatible-Assistant/dp/B0C7C6L66J/ref=sr_1_4?crid=2WPBKDELB3DH5&keywords=mmwave%2Bpresence%2Bsensor&qid=1691579971&sprefix=%2Caps%2C78&sr=8-4&th=1

Thanks, but I gave up. I had increased the interview timeout, changed network speed, even set the lock up within inches of the Zmatter adapter. Nothing worked, so returned it and got a Yale Assure Lock 2 for about half the price and it worked flawlessly on the first try. Had to shuffle around where each lock is on the house so its less obnoxious to the wife, but I'll probably be liquidating the Schlage locks I have soon.

Can’t set user codes by hand. However, IoX does reflect lock/unlock. I think I might have to just bite the bullet and scrap all these Schlage locks.

Other post thing isn’t important. That’s why I made this post. I started to pull a “me also” on someone else’s and realized what I had started so…. New post. But anyway, the only reason I haven’t switched over to Yale is that all of the locks in the house match. That’s the way the wife wants it and I’m not about to drop > $1k to get all new hardware. Especially since we’re planning to move soon and may not even need that many locks for where we’re headed. I was just hoping some else had gone through something similar and had an idea.

I'm having trouble with a new Zwave lock. Well, actually two. Lock A: No longer accepts the programming code and does not respond to a factory reset (ie. still doesn't accept the factory programming code after a factory reset). Any ideas what I can do with this now? Schlage couldn't have been less helpful. After two months of cyber bullying though, they finally agreed to honor their warranty. Now, onto the replacement unit... Lock B. Was a royal pain to get added to the eISY. Many attempts later and it finally added all of the right channels to the same node at one time. (after 15+ tries). Anyway, Lock B will respond to a query of it, Lock B will lock and unlock on command from the eISY. However, it will not accept any parameters or new user codes. It says that it accepts them, then when you try to use the new user code that you just added the lock will not open for it. I'm hesitant to factory reset it, given my experience with Lock A. And of course, Schlage says they may have a replacement part in about a year (this replacement came from a third-party vendor that I had to locate on my own and that vendor has no more). So... ideas on how to force a BE469 ZP to accept a new user code?

They all mapped back to the same lock. Somehow it saw the channels separately and indicated the device was not multichannel. I DID eventually get this working however now, I cannot set any of the parameters on it. Can't set user codes or anything.