fmk2

Thanks for all the help, folks. I checked the memory as Techman suggested, and I have 48733 MB free. So definitely no problem there. As Geddy suggested, I checked and the eisy is on v5.9.1 for both the UI and firmware. Andy P's suggestion that it might be related to missing hardware seems to be the solution. I checked a couple of the programs that are showing "out of memory", and there is a missing device in those programs. I replaced a Z-Wave switch some time ago, and apparently didn't update the affected programs when I did so. So I'll go through those programs and update all of them. That should resolve the "out of memory" errors. I also noticed that "Matter Support" somehow got turned off. So I've turned that on and restarted IoX. As you can probably tell, I don't look at this system very often... it's reliable enough that I don't have to. So when I do need to fix something, I don't always remember the best way to troubleshoot things. Thanks to all of you for helping me straighten out these issues.

No programs running, and no issues since deleting the programs that were running on their own. I tried disabling programs but still had some issues. Deleting a couple of the problematic programs seems to have fixed the random turning on and off of lights. I suspect they were somehow corrupted, and they were both simple programs so they can easily be recreated later. I still see a lot of programs that aren't loaded because of the eisy being "out of memory". Is there a way to check the actual memory usage of the eisy? Maybe via SSH? I still some old X10 programs on the eisy, but haven't used X10 in many years. I'm going to delete them to see if the memory issues improve.

I'll try reinstalling the node server later. This evening I had a new twist on the problems I've seen. Turning on either the Kitchen or Living Room Insteon switches at the paddle resulted in the light immediately turning off again. I checked the Programs Summary page, and discovered 3 different programs -- all of which were on demand only, and not set to run on a schedule -- that ran whenever we used either switch. One of them didn't even have anything to do with those switches, but was forcing them to turn off anyway. So I've deleted those programs for now, and I'll just recreate them later. I also noticed in the Summary page that some programs have "Not Loaded" in the Activity column, and "Out of Memory" in the Status column. I have a very small number of programs, and can't imagine that I've come anywhere close to using up all the memory in eisy. How would I check that? Can I SSH into the box and run a "du" command on some directories? Or is there another way?

Never mind... the Inventory node isn't a big deal. I just deleted it.

Thanks for all the assistance. Since doing the package upgrades and a reboot, I'm now getting repeated Connected messages from the ST-Inventory node, one every 30 seconds or so. If I look at the log, I see this error is repeating with each notification: 2025-03-21 11:59:40 error: NS: uncaughtException: Cannot read properties of undefined (reading 'nodes') TypeError: Cannot read properties of undefined (reading 'nodes') at Controller.onDiscover (/var/polyglot/pg3/ns/0021b9026200_5/Nodes/ControllerNode.js:50:29) at new Controller (/var/polyglot/pg3/ns/0021b9026200_5/Nodes/ControllerNode.js:37:9) at Interface._addNodeToList (/var/polyglot/pg3/ns/0021b9026200_5/node_modules/polyinterface-v3/lib/Interface.js:523:19) at /var/polyglot/pg3/ns/0021b9026200_5/node_modules/polyinterface-v3/lib/Interface.js:582:20 at Array.forEach (<anonymous>) at Interface._onConfig (/var/polyglot/pg3/ns/0021b9026200_5/node_modules/polyinterface-v3/lib/Interface.js:578:18) at Interface._onMessageQueued (/var/polyglot/pg3/ns/0021b9026200_5/node_modules/polyinterface-v3/lib/Interface.js:361:17) at dataq.process (/var/polyglot/pg3/ns/0021b9026200_5/node_modules/polyinterface-v3/lib/Queue.js:28:26) at dataq.add (/var/polyglot/pg3/ns/0021b9026200_5/node_modules/polyinterface-v3/lib/Queue.js:18:10) at /var/polyglot/pg3/ns/0021b9026200_5/node_modules/polyinterface-v3/lib/Interface.js:336:26 I tried restarting the node, but that didn't help. Is there a simple solution for this, or is it something I should post in the Polyglot forum?

Thanks for all the assistance. I've now re-synced UDMobile as well. Since doing the package upgrades, I'm getting a recurring connect/disconnect from the ST-Inventory node. The log shows this error:

I've done syncs on UDMobile recently, the most recent being yesterday. I didn't realize my firmware was out of date. I'm used to the ISY telling me when there's an update available, but the eisy hasn't done that. But no problem... I did the update — including Update Packages — so everything should be current now. I have a total of 3 programs that ran at random times without being triggered, but all of them ran at 21 minutes after the hour for some reason. We did have a power outage recently, and I realized that these issues popped up shortly after that time. So I suspect that may have scrambled some things in the eisy. Now that I've updated the firmware and rebooted, I'm hoping things will settle down. I'll let the system run for today, and see if there are any other incidents overnight.

Firmware and UI versions are 5.6.3. Looking at the programs summary, I do see a couple programs that ran when we saw unscheduled light changes. One at 11:21pm last night (I woke up around 2am to find the living room lights on), and another at 11:22am this morning (my wife reported that the kitchen and living room lights turned off at that time). But neither of the programs that ran are scheduled... they run only on demand via a button on the UD Mobile dashboard. I'll run diagnostics on the devices that are in these programs and see if there's a problem with the link tables. If so, I'll run "Restore Device" on them.

No, I haven't run a sync lately. That's a good idea, I'll do that now. I now also have another issue. A couple Insteon lights — specifically the Living Room and Kitchen — are turning on without any program or switch being activated. It always happens at 21 minutes after the hour, but not every hour. I'm still investigating, but I can't find any reason for it so far.

After fairly extensive testing, both on the problem switch on its own (with a test program), and by making various modifications to the program in question, I've learned a few things — and effectively solved the problem: I discovered that the feedback from Z-Wave switches to UD Mobile is very slow... on the order of 20-30 seconds. I noticed this by watching the status of the switches in UD Mobile when running the program. That led me to wonder if the delay with Z-Wave might be interfering with communication to the problem Insteon switch, which was the last switch in my program. Playing with various "Wait" times to try to let the Z-Wave communication finish didn't help. Moving the problem switch to the top of the program (making it the first switch to be turned on) did work, but only if I used the "On" command to that switch. Using the "On Level" command that I had been using resulted in the Insteon switch not responding. I've now set the default On Level for the Insteon switch at the level I want the lights set to when the program runs. With that set, I can issue the "On" command in the program and the lights come on to the level specified in the switch settings. So in the end, the problem was likely the use of the "On Level" command rather than any delay or interference from the Z-Wave devices, although it may have been a combination of the two... it's hard to tell. Regardless, it seems I may have found the solution.

Pulling the switch into it's own program as a test is a good idea. I'll do that this afternoon and see if the program runs successfully at the designated time. I had something else odd happen last evening. A program that I have to dim the lights when watching TV ran on its own. It isn't a scheduled program — I normally run it from a button on the UD Mobile dashboard — but it ran twice within about 10 minutes. At that point, I decided something must be scrambled in the eisy, so I rebooted it. No strange behavior yet today, so we'll see how things go.

Yes, I have tried reselecting the switch, hitting "Update" and then Saving. No change. I wrote a quick test program that was set to execute at 1:45pm. It included that switch and one other so I had a known-good switch to compare with. In the test program, the problem switch came on as expected, but the so-called known-good switch did not come on and the eisy reported no longer having communication with it! Maybe it's a coincidence, but the timing seems suspicious. I'll try deleting and reselecting the problem switch (again) in my program and see if that fixes the issue. Worst case, I guess I could delete the program and recreate it in entirety — it's not like it's a huge program. As for the known-good switch that now has communications issues, I suppose I need to address that separately. Tons of fun.

OK, here's the program: The switch in question is 'Living Area / LR Lights'. I haven't tried creating a test program as Guy suggested... I should have thought of that. I'll try that today.

Thanks for the replies. Yes, I've run the program from the "Run Then" option, and all the lights in the program respond except this one switch. Likewise, everything but the one switch responds to "Run Else". And as I mentioned, this isn't a new program — it's been running fine for years. I was hoping maybe there was something I could do to get it to start responding, but it sounds like the switch is probably defective.

I have a program that turns on certain lights in the evening, including the cans in our living room. This program has been running for many years without issues. But recently, the living room Insteon switch has stopped responding to the program. The switch works fine locally and via the Admin Console or UD Mobile, but when my program runs the switch doesn't respond. I've tried resetting the switch and then Restoring the device, but it hasn't helped. Are there other things I can try, or is this switch now defective in some way?

Thanks very much for the quick solution... that did the trick.

I just installed a Vue and got it connected to my utility provider (PG&E). I can see in the Vue app that it's working fine. I then installed the Vue Node Server on the eisy, but I'm seeing the same "file not found" errors repeatedly. I've attached a file with the errors that I'm seeing, but it appears that the problem is that the "boto3" module is not found. Has anyone else seen this and found a fix? VueNode_FileNotFoundErrors.txt

Never mind... I decided to just go for it. I've been able to add one of the Z-Wave switches (enbrighten ZW3010) successfully after doing a factory reset on it. It seems to be working. Frank

I've migrated my ISY to the eISY, and all my Insteon units are working well. I now want to add a couple Z-Wave switches that I formerly controlled with a Hubitat via a Polyglot unit. So I purchased the Z-Matter USB option, and have plugged it into the eISY. I can see the "Z-Wave" menu drop-down in the AD, but I want to know if there's anything I need to do before adding Z-Wave devices. For example, on the Configuration->System tab, I have "Z-Wave Support" checked. But I also see a button labeled "Migrate to ZMatter Z-Wave". Since I wasn't using the ISY's internal Z-Wave, I assume I don't need to click that button because I have no existing Z-Wave devices to migrate, but is that a correct assumption? In short, my question is: What are the steps to take after plugging in a ZMatter USB and before adding Z-Wave devices? The lack of documentation on this is really frustrating, by the way. There really should be some installation instructions included with the unit, or at least a QR code link to online documentation. Maybe just plugging it in and clicking the "Z-Wave Support" checkbox is all there is to it, but there's no way to know that because it's not documented anywhere.

Thanks for the reply. I did still have a couple programs related to the Zigbee power management enabled. I also had a couple programs related to weather alerts that relied on the Ambient Weather node but they were based on the PG2 version of the node. (I haven't enabled PG3 yet.) Neither the power management or weather programs were running, but I deleted all of them since I'll need to recreate them once I get PG3 up anyway. I then waited about 15 minutes to make sure they were truly deleted before trying to run UD Mobile on the iPhone. No luck. When I look in AC, I don't see any programs currently running so I don't think that's an issue at this point. I'll open a ticket.

I've migrated my configuration from the ISY to the eISY, migrated the portal, and things appear to be generally working. I can control Insteon devices in Mobilinc on my iPhone, however I can no longer get UD Mobile to run on the iPhone at all. When I click on it, I see a brief flash of the app, and then it disappears. If I look at what apps are running in the background on the phone, UD Mobile is there, but selecting it doesn't work. Any suggestions? Did I perhaps miss a step in the migration from the ISY somewhere? Thanks.

I prefer an option where updates get pushed to the device and I'm notified that they're available, but don't get activated until I say so. That way I can make sure they are implemented when I'm around to monitor the result. That said, I'm probably OK with being nagged (via recurring emails, maybe?) if an update doesn't get activated in my system for some prolonged period of time. But of course then you have to define "prolonged period of time"...

That makes sense, but the other Node-Servers on the Pi (ISY Inventory and Hubitat) are working fine so it must be something specific to the Ambient Weather node server. Maybe running an update on the Pi will fix the network problem. If not, then I’ll try reinstalling the Ambient Weather node server.

Thanks for the assistance, Bob. Other priorities kept me from getting back to this for a while, but I did figure out what I needed to do to get the Ambient Weather node values into variables, and in turn use those in an alert. However, the values for the Ambient Weather nodes aren't updating in the ISY. I see all the nodes, but the values in those nodes get set when the Ambient Weather Node Server is restarted, update regularly for a few hours, and then stop updating until I do another restart. Based on the log, it looks like MQTT is running into an SSL error: ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2341). But I don't know why it would run for a while and then suddenly fail. A Google search didn't give me any useful info. I've attached the log. If anyone recognizes this and has any suggestions for fixing it, please let me know. AmbientWeather_1-28-2023_100707.txt

Sorry, I should have posted my fix some time ago. I did finally fix this by doing exactly what @Techmansuggested. I ended up doing a factory reset and a restore on all 15 2477D switches in my house. It was a nuisance, but it solved the problem. I don't know what caused this problem initially. We did have a brief power outage in late November, so perhaps that scrambled things in the ISY? But we've had subsequent outages and there hasn't been any problems afterward, so who knows. Thanks for the assistance.