MWoods329

I started getting this recently whenever I try to add a Zigbee device. I already have (had until I tried a ZMatter dongle reset) others that ran Zigbee just fine. Anyway, when I would attempt to add, the log would show an interview start and then the messages ZBEE-Log Terminating, then ZMATTER-Log terminating, then the whole system would freeze. I waited about a half hour once for it to unfreeze and it didn't so every time after that I've tried forcing it to reboot by pulling the power, because once this happens the whole thing freezes. Also, the ZWave and Matter menus show not available even though the Zigbee menu is still present (doesn't respond to anything you click).

I finally tried to get a node set up for my YoLink water valve (with Local hub), so I installed the YoLink Local trial but I'm just getting this. Its persisting through reboots, reinstalls, etc.

Sadly... nope. Still getting it after restoring the eISY from backup.

Thanks. Found it, but that didn't do anything for me either Maybe a little bit of progress. Now there's only one error I get every time - the AutoUpdate Error

Any idea what directory those files might be in? I'm not seeing them in the temp folders or anywhere else.

No luck. Same problem, even with the UUID before the url.

I guess that's what I'm not understanding. What would be the "correct information"? That's already the right IP address. I'm on 6.0.4

When I clear the messages, it displays exactly what I would expect. The IoX finder does appear to be locating the controller correctly. That's the right IP address and as far as I can tell that's the right URL format. What am I missing?

This has been an ongoing trend for a while (probably over a year now), but I'm just now getting more annoyed with it since I have to open the admin console more for the updates I'm making around the house. Anyway, whenever I open the admin console, I am met with the ghosts of error messages past. Sometimes more than one (as seen below), sometimes only one (usually the AutoUpdate Status/Authorization Failed! message) will always appear whenever I open the admin console. It doesn't matter if I clear the message, clear the Java cache, try a different machine, reinstall Java, reboot IoX, reboot eISY, etc. I am always met with a slew of error messages when I open the admin console. Has anyone else encountered this and know how to get rid of them for good?

A few things: 1. Nice overhaul. I'm liking the UI so far. 2. Whenever I try to use the search bar on the nodes page, I get this: 3. The nodes list will re-expand itself almost on a timer. Let's say that I'm collapsing the nodes to make it easier to find something further down. Maybe I click on something within a node to check it out after a few collapses. Sooner or later (usually withing 15 or 20 seconds) all of the nodes re-expand.

Upgraded to 0.5.1 and now I can't even save a dimmer tile Config: Widget Config:

One day, I will have an intelligent question to post here. Maybe that day is today? Anyway... I'm curious why I can't take a dimmer on a Hue light down to zero? That means I'd need to have two tiles to handle the dimming on these. Or is there a better way to make the slider both dim and turn it off? I know that's a limitation in the admin console, I guess I just would have expected a more user-friendly UI would handle those types of interactions.

Ah, thank you. I didn't understand that it would be a dependency once installed. Got it now.

When I rebooted my eISY, I noticed that eisy-ui did not start on its own. And since I didn't plan on doing any more testing for a little bit, I didn't manually restart it. But the bigger issue is that during that week or so when eisy-ui wasn't running I couldn't access my eISY through other interfaces and the eISY couldn't reach the portal. I thought I was troubleshooting a networking issue or something (Ticket #27059): - couldn't connect via IoX launcher or I could but it would disconnect and throw errors -UD Mobile could only connect locally because it said the eISY was not connected to the portal -could still connect with the eISY through the API and Home Assistant Once I ran sudo service eisyui restart, all of those issues resolved. Is the eisy-ui service (or lack of) supposed to be able to cut off all other UI access like that?

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?