All Activity

Thanks

Thanks Paul - I finally got the HomeKit to work (had to take the ecobee off the AppleTV hub first, doh!). The HA server is pretty solid - working with my solar and other integrations, but this one is stumping me. The previous box had it working perfectly, so will keep plugging away at it.

looks like I will not be upgrading firmware. I do not have the option to download latest firmware as I am not connecting ISY to the internet. Unless there is a manual download and upgrade option I do not see how can I upgrade it.

It can be hard to get answers there but this more of a HA problem than an eisy problem. You'll need a solid/stable HA server to add Integrations like ISY and it doesn't sound like you're there. For ecobee, the most direct connection is through the HA HomeKit Device integration which uses bon jour to talk to it directly making it a totally local, cloud free connection (as long as its on the same LAN segment).

I had HA running a while back and the Droid box I was using bricked, so I "upgraded" to an Intel-based one from Pulcro. I decided to install from scratch and this has been a headache across the board. AppleTV (for HomeKit) won't connect - and I need that to connect my Ecobee as they stopped the API from working. But more importantly EISY won't load. Any ideas or thoughts? EISY is working as usual. No errors showing up there. Some ChatGPT searching points to a group/scene member not being in the right format but honestly I have zero clue how to look for that / audit it. Any guidance from you smart folks would be most appreciated! Errors from HA: Logger: pyisy Source: runner.py:289 First occurred: 5:42:21 PM (3 occurrences) Last logged: 5:42:21 PM ISY Reported an Invalid Command Received /networking/resources ISY Reported an Invalid Command Received /vars/definitions/1 ISY Reported an Invalid Command Received /vars/definitions/2 and Logger: homeassistant.config_entries Source: config_entries.py:769 First occurred: 5:42:22 PM (1 occurrence) Last logged: 5:42:22 PM Error setting up entry IoX (192.168.7.5) for isy994 Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 769, in __async_setup_with_context result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/isy994/__init__.py", line 111, in async_setup_entry await isy.initialize() File "/usr/local/lib/python3.14/site-packages/pyisy/isy.py", line 150, in initialize self.nodes = Nodes(self, xml=isy_setup_results[2]) ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.14/site-packages/pyisy/nodes/__init__.py", line 138, in init self.parse(xml) ~~~~~~~~~~^^^^^ File "/usr/local/lib/python3.14/site-packages/pyisy/nodes/__init__.py", line 465, in parse Group( ~~~~~^ self, ^^^^^ ...<6 lines>... flag=flag, ^^^^^^^^^^ ), ^ File "/usr/local/lib/python3.14/site-packages/pyisy/nodes/group.py", line 63, in init self._update() ~~~~~~~~~~~~^^ File "/usr/local/lib/python3.14/site-packages/pyisy/nodes/group.py", line 112, in _update node_obj.status is not None ^^^^^^^^^^^^^^^ AttributeError: 'Nodes' object has no attribute 'status'

It's possible that your Insteon mesh network is marginal, or that you have noise on your powerline that's interfering with the Insteon signals . How many dual band devices do you have in your system. If everything was working prior to moving over to the eisy try doing a restore device on the insteon devices that aren't working properly.

Yep. More time planning / organizing will speed the whole thing up

Yes, my old X10 chime was perfect. Disappointed that it stopped working. Even bought a second one as a test in case the first one had gone bad. No joy. It had two tones, I could make it go Ding or DingDong. I triggered it from my ISY to announce arm/disarm of an ISY program.

Thanks folks. @paulbates , that explains why HA could see the links by just plugging in the PLM. Looks like I have a project ahead of me. It would benefit me to take note of the Insteon addresses in the HA integration so I don’t have to pull the FanLincs down. The Insteon integration in HA is pretty bare bones (no dim/brighten signals, can’t programmatically change button light levels), so I’m going to try running eisy from HA through the IoX integration. The Hue node server is the best way I’ve found to control Hue lights with Insteon dimmers.

Truth be told I had one I bought a couple of years ago to announce for leak sensors and sump pump depth alarm in my basement . One of the leak sensors was in a well area and the floor gets damp there... so it went off as it should but not really an emergency. I was able to move it a foot or so to still work but not false positive. But that event was not a hit with my wife as it was not a real problem and home automation took a shot on goal when its otherwise really good. I got rid of it. I had the same problem with yolink version. Too screamy. Still looking. I also don't want to keep adding things like zwave, zigbee, wifi etc to solve one problem and throw other topologies at the problem. .. and I thought about that old X10 chime that gave a nice beep ..... beep ... beep several times.

Ever since I upgraded to the Esy thing not work as before. When any swith is left on for an outside light it should light up my keypad telling me it was left on. Also othe light that are on a timer if the light is left on, it stsyd on as if the esy is not reading the status of the switch left on or turned on

Thank you for that link. It is informative. Sounds like it won't quite do what I want: It doesn't have two different chime tones that I could separately trigger. There are warnings that make it sound like it is too loud for my purposes. I suppose I could buy one to test it out...

In systems like Indigo, HouseLinc or Home Assistant, the PLM is the system of record and the automation software looks there and "pulls" the network data from the PLM. The UDI / iox controllers on the other hand are the system of record for the Insteon network. These controllers maintain the master link table and "push" it to the PLM and Insteon network as each device as added. As mentioned above, what you want to do is not possible with the ISY.

I don't think you can "learn in" an existing PLM. Part of the module linking process is to learn the module type and create the appropriate node(s).

There is an older lengthy post. This particular comment covers it. If you are hemorrhaging time, you could read the whole thing, but picking through it won't hurt. My recollection is that there are features in the device's panel when you add it to iox.

If the PLM was linked to another Hub then you will might have to factory reset it as the PLM contains the link tables of the previous hub and may not be compatible with the eisy Do you currently have a working, and populated eisy? The replace PLM instructions are attached. Replace PLM Procedure (EISY or POLISY).pdf

@NewB , Suffice it to say that things have gotten a bit hosed (technical term). The PLM links table you posted is extremely short (21 entries). The PLM is listed as the controller for all the devices in the ID column. There are no scenes listed. It is possible that the PLM read process was interrupted. Try this a couple of times to see if you get the same result. If so, proceed with the "recovery below". The device table you posted indicates that the "Dining Vanity Mirror" is a Responder to the devices listed in the ID Column. It can't control anything. Recovery: Please verify that your PLM address is 71.18.59. Since your PLM link table is incorrect (after multiple PLM restores), you'll need to perform an ISY restore. LOOK at your backup file sizes. If you have a recent backup that is significantly different in size (from previous), it's suspect. Choose a recent backup that looks consistent. If you get socket errors during the restore (or a backup), do not trust it. Logout of the admin console, clear the cache, log back in and restart the process. When the restore ISY complete correctly, it will reboot the ISY. Log back in, turn off "writes to battery devices", and perform a "Restore Modem". This should re-write the PLM records. After the above completes, re-check your PLM records. If it's still very low (<100) post back and we'll rethink things. It's possible that that the ISY will not re-write the device link tables in step 3 (if it didn't detect a PLM change). The Only way to know for sure is to perform "link table read/compare's" on devices. You can address these individually by running a "device restore", but if there are many, it's may be easier to use the "restore devices" from the file menu.

It is possible that my X10 chime stopped working when I switched from ISY to eISY. I haven't been able to figure out from available documentation how I would tell that siren module to make a ding dong noise from eISY.

I have a 2413U PLM that I was using with Indigo, and I wish to come back to IoX/eisy. The PLM is already linked to all the Insteon stuff so I want to do this without having to re-link it all. I plugged it into the eisy and did Tools/Diagnostics/List PLM Link Table and everything seems to be there but I don't know how to see the devices in the sidebar in IoX.

I experienced the same thing., was running 5.9.1. My process was: take backup launched UD mobile and kicked off firmware upgrade while watching it upgrade, cleared all JAVA files and cache after about 10 minutes I would say, UD Mobile said firmware update complete BUT then immediately told me another update was available. Decided to wait on applying another update in case it was confused. Went to ISY Web Portal and selected "ISY Web Access" This launched a web version of my EISY. Then went to Settings, "Install Admin Console (internet). This got the EISY Admin Console installed on my PC and was able to login like before. Using local credentials. Then tried to access eisy.local and nothing. Decided to wait the full 60 minutes like the upgrade instructions said. After the full 60 minutes, still no access. Went back to UD Mobile and let it do the other update it mentioned. This updated PG3X to version 3.4.18. This time it said a reboot was required, so let it reboot. Tried to access eisy.local and still no access. Decided to try and do the eisyui install from CLI. SSH'd into the appliance Ran "sudo pkg install eisyui" It did say this package wasn't installed and did I want to install it, said Yes. Monitored it installing and doing numerous migrations. Then restarted ISY "sudo service isy restart" Tried to access eisy.local and still no access. And I could no longer get in with the UD Mobile or the Admin Console. Rebooted the EISY appliance This time the UD Mobile worked and I could access the Admin Console Now the Admin Console required me to use my ISY Portal Credentials, not the local credentials I was using in the past. AND.... FINALLY, I could get access to eisy.local I believe I have seen numerous posts that say the upgrade package installs eisyui, for me it didn't. Anyway, hopes this helps someone else in the future.

@NewB Scenes reside in the PLM and the devices. You could disconnect the ISY and the scenes will still work. It's possible that when you initially restored the new PLM the scene's links got corrupted. Take a scene that isn't working and do a restore device for each device in that scene. If that corrects the problem then you'll have to do it for each scene that isn't working correctly. If that doesn't correct the problem then you'll have to rebuild the scene

Yes, I'll wait, to see if this was just a freak one time occurance. For the link count, are you suggesting that I check if the link count has changed, or just if the link count is getting high? I only have about 340 links.

and here's what I get back when I do a diagnostic on the bedtime scene with all programs disabled... Sat 04/04/2026 01:36:29 PM : [GRP-RX ] 02 61 12 13 00 15 <html><font color="red">----- Bed Time Lights Test Results -----</font></html> <html><font color="red">[Failed]</font> Curly Light Front Entrance (17 32 CC 1)</html> <html><font color="red">[Failed]</font> TopStairsKey-Picture (49 EF 8B 1)</html> <html><font color="red">[Failed]</font> Dining Vanity Mirror (4F 3A F7 1)</html> <html><font color="red">[Failed]</font> LR Floor Lights (57 3C F8 1)</html> <html><font color="red">[Failed]</font> TopStairsKey-BedTimeLights (49 EF 8B 4)</html> <html><font color="red">[Failed]</font> Pool Pot Lights (12 4A 7F 1)</html> <html><font color="red">[Failed]</font> Cast UpLighting (25 CD 12 1)</html> <html><font color="red">[Failed]</font> LR Fireplace Light (57 3C D0 1)</html> <html><font color="red">[Failed]</font> Crystal Ball (4C D2 32 1)</html> <html><font color="red">[Failed]</font> Loft Keypad.BedTime (F 95 D3 4)</html> <html><font color="red">----- Bed Time Lights Test Results -----</font></html>

Thank you again to everyone for trying to help. Here's what I did and I'll try to give you as much information as possible for a solution as to why my scenes won't work with my new PLM but the individual devices will work from my admin console. 1-I did a factory reset of my new PLM to erase all tables and start from scratch 2-I followed the replace PLM instructions provided by Tuchman to see if that would work...(like when it worked fine 3 months ago when my previous PLM (that was only 6 months old) broke). 3-After following the instructions and factory reseting the new PLM modem and restore modem (PLM), there was no change. 4-When I create a new scene, the new scene does work...which probably means that the old saved scene instructions are not getting to the new PLM...but someone more intelligent that I on this forum can let me know if this is true. I have a ISY994i with a PLM and both firmwares are 4.9.0. With the event viewer this is what I see after I select turn on "Scene Bed Time Lights" with 8 devices attached... Sat 04/04/2026 01:30:29 PM : [INST-TX-I1 ] 02 62 00 00 12 CF 11 00 Sat 04/04/2026 01:30:29 PM : [INST-ACK ] 02 62 00.00.12 CF 11 00 06 LTONRR (00) Sat 04/04/2026 01:30:32 PM : [ Time] 13:30:34 0(0) Any ideas?? Thanks... NewB ISY Links Table dinning vanity Mirror .v4.9.0__Sat 2026.04.04 01.28.18 PM.xml PLM Links Table.v4.9.0__Sat 2026.04.04 01.26.20 PM.xml

That is a sign. If either restore PLM or unplugging from the wall and replugging fixes it... highly likely a dying PLM. Look at the link table count can help, but..... wait for it to happen again as once you restored, it has its memory of links back for a while. If it is a failing PLM, these events will cascade until its finally dead.