dbb1

I don't know if this is still of interest to anyone, so this is probably a dead topic at this point. I've been trying to chip away at this. I found the Autelis API reference and at the moment, I am able to get all the temps, equipment status, circuits, circuit names, system status info, etc. from my Autelis controller reporting directly into HA as sensors that I can display from entity cards, via RESTful definitions and template sensor .yaml files. No ISY involved. I would like to take the ones and zeroes from some of the binary-type sensors and be able to display them as On or Off, and convert the Unix time that reports back into some sort of human-readable dates/times, but have not yet been successful. I haven't gotten so far as to be able send commands from a button card, but have been able to send simple commands from the terminal using curl statements to turn equipment like the lights on/off, for example. I'm not a developer, so this has been a bit of a slug-fest...

Just checking in, here. Has anyone done any digging into this? I also have an Autelis Pool Control integrated with my ISY. But because of recent, ongoing issues with ISY and Insteon, I'm trying to slowly but surely move things into Home Assistant, but this time I'd like to use the HA Insteon integration, rather than the ISY one. Problem is, I've got some pool-specific actions built around various pool status points in ISY that I'd rather not live without, so that is preventing me from moving the other Insteon devices off of ISY. I'm not a programmer, but I see references to ajax.js from browser developer tools when I hit the Autelis web page and toggle some of my equipment on/off. Someone mentioned that the interface was more REST-based, and that digging into RS-485 signals may not be required. Could WireShark or Fiddler be used to intercept and decipher the REST traffic? I also see that someone developed out an Autelis Node Server, the code of which is in Github. Could this be used as a basis for porting over to HA? I mentioned that I'm not a developer, but I'd like to help in any capacity that I can.

EagleAye, did you ever find a solution for this? I also have my Autelis (Intellitouch/Easytouch) integrated with the ISY994i, but would also like a direct integration with Home Assistant. I've seen integrations for Pentair's EasyTouch controller. Since both work with the Pentair controller bus, I would have to think the HA EasyTouch could be modded to work.

I had ISY working within Home Assistant, and everything was working on the dashboards I set up. Then, I had some issues with some Insteon switches and so had some scene rework needed in ISY Admin. I also had a few NodeServer integrations set up in ISY, but since I wasn't using them I decided to remove them from ISY. Then, the ISY HA integration began failing. I have deleted and re-added the HA integration several times, with a full HA system reboot between each attempt, but still get ISY errors in HA. The integration says that it successfully completes, but I'm left with an integration that says "Failed to set up Check the logs," which seems coincidental to so heavily reference "nodes" in the logs: Logger: homeassistant.config_entries Source: components/isy994/__init__.py:175 First occurred: 1:29:28 PM (1 occurrences) Last logged: 1:29:28 PM Error setting up entry ~HomeUser's ISY994i (192.168.100.45) for isy994 Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 313, in async_setup result = await component.async_setup_entry(hass, self) # type: ignore File "/usr/src/homeassistant/homeassistant/components/isy994/__init__.py", line 175, in async_setup_entry await isy.initialize() File "/usr/local/lib/python3.9/site-packages/pyisy/isy.py", line 138, in initialize self.nodes = Nodes(self, xml=isy_setup_results[2]) File "/usr/local/lib/python3.9/site-packages/pyisy/nodes/__init__.py", line 108, in __init__ self.parse(xml) File "/usr/local/lib/python3.9/site-packages/pyisy/nodes/__init__.py", line 380, in parse Group( File "/usr/local/lib/python3.9/site-packages/pyisy/nodes/group.py", line 48, in __init__ self._members_handlers = [ File "/usr/local/lib/python3.9/site-packages/pyisy/nodes/group.py", line 49, in <listcomp> self._nodes[m].status_events.subscribe(self.update_callback) AttributeError: 'Nodes' object has no attribute 'status_events' Not sure what all this means. In trying to follow the directory paths above, it doesn't appear that I have a python3.9 folder. From putty, I see that my Python version is 3.8.10 (I'm running supervised via portainer/docker on Ubuntu server 20.04). Does the ISY integration install Python, or has it recently required a newer version than what I am running? Or is there some manual process to fully remove a prior integration from HA, prior to doing a re-installation?

Thanks Mr. Bill. As mentioned, I have the 2477D switches and I've been using the long hold set button method to reset them. I have these in a three-way installation for the family room, and a two-way switch install in the kitchen. I've reset these things so many times and re-added them to the ISY now, it ain't funny. It seems like the last attemp "took." They have now been working for the better part of two weeks with no random on/off events. The only issue I now have, is that the second switch in the kitchen configuration is doing a very slow 9 or 10 second ramp-up/down, which I can't track down. All the setting in the ISY for both of these switches are configured for .1 fast on ramp-up. One works as intended, the other has the slow ramp rate. I've used the manual ramp setting right on the switch, as shown in an Insteon how-to video (1 quick off taps followed by two quick on taps), but this doesn't seem to have any effect. But at least they stay on...

Haven't given up quite yet (see previous post). My factory reset method has always consisted of: - deleting the switch from the ISY control dashboard, - air-gapping them for 30 seconds or more, and - holding in the top of the paddle until the long-beep stops, and the switch lights ramp up Then I re-link them in ISY (have tried both letting the auto-link discover the device, as well as by manually entering them), while always using the default "remove links" radio button. In the case of the multi-way switch installations, I would then manually group them together using the paddle hold and link method, and then organize them to the appropriate folder in ISY. Not sure what else there is to do. I'm definitely going to have to read up on some of the tools, what they do, and when to use them, such as Restore PLM, Restore Device, Link Tables, etc. It's not all that straight-forward or apparent from the UI.

Thank you, I most certainly will if I can locate one. I may have to wait until it happens again. I think I currently have the 3-way family room switches squared away, but they lost their configuration the other night and I had to re-do them. I've pulled the kitchen 2-way switches out of the configuration, but will try it again this weekend. Any thoughts on this happening to only the multi-way switch installations?

This has been driving me nuts. I've read several posts that seem to mimic the issues I'm seeing, but I haven't been able to resolve anything. The ISY994 Pro f/w and UI are both on v5.3.4, but the random off/on was happening while on the latest v4 firmware prior to the upgrade. Lights are 2477D dual band and have worked flawlessly for years until about mid-summer. The kitchen lights began going on/off, sometimes fairly rapidly. Of course I rebooted everything with no luck, but the problem eventually seemed to go away on its own. Then the family room lights began going off of an evening, then coming back on a few minutes later. Now the kitchen is back in the act. Although I can't make a direct correlation, I did install a new Pentair Intelliflo pump this last year, which I understand is very noisy, but I honestly can't make a correlation with the pump installation and when the light issue began (but I know it's happened when the pump was not running). I've also installed new Venstar thermostats. There also does not seem to be a correlation with any of my programs or other devices, or a certain time, either. The odd thing is that both the family room and kitchen are multi-way switches - three-way in the family room, and two-way in the kitchen. None of my other, single switch controls seem to be affected - yet. I've deleted the switches from the ISY, factory reset them, and linked them back in (tried both the auto-detect and manual address entry methods), then moved them to my desired folder and scenes (also used the "paddle-hold and link" method to group the mult-way switches with each other). That seemed to take care of the issue in the family room at least, until last night, when the kitchen lights began acting up again, so I did the same for those two switches. Thought I had it all sewn up, but then later in the evening the switches stopped controlling the lights in both places altogether. Redid the family room, but gave up on the kitchen. I don't know what else to try. Should I hit the reset button on the PLM? Restore it? The PLM is one of the newer ones, after the original one died after a couple of years of use. Even though I've been running this gear for a number of years, I don't have much experience troubleshooting the platform or searching through logs - I never had to, so I'm not sure what some of the tools do. Sorry for the wall of text, but am at my wits end. My wife is wanting me to pull it out and go back to basics.

I’ve been looking at the Elk M1 Gold system for several years, but now that I’m remodeling my house, throwing that upgrade into the budget to replace my old PC-1555 may now make sense. The question I have is with monitoring. I like the service I now use - it’s fairly inexpensive, and I’ve added their cellular comm into my hardware mix. Problem is, they have stated that the Elk system interface is not something they support. I know there is a service that you all seem to tout for use with the Elk platform, but is it a reasonable assumption that the Elk interface would work with/emulate a popular and widely deployed system like the PC-1555, to allow for monitoring by most service providers?

As far as filters go, wouldn't the less expensive XPPF X10 filters perform the same functionality as the FilterLincs? The only difference that I could tell between them is the pass-through outlet and higher amp rating on the FilterLinc. So in my mind, it's just a matter of application (don't need the pass-through outlet, low wattage device to filter, etc.). Whether marketed for X10 or Insteon, these filters are all operating the same way electrically, right?

So things have gotten a little strange. Now that I can consistently control the Insteon 2477S from the ISY994i (after moving the ISY/PLM to the wiring closet), I moved on to see if I could access any of my X10 switch installations. The downstairs master bedroom X10 devices seem to work when programmed from the Admin Console (although I do occasionally lose the ability to control them). Other X10 switches across the house not at all. In fact many of my wired x10 switches are not working from the PalmPad I previously used to control them (RF to a plugged-in receiver, which then sent the signal onto the power bus). I can only get these lights to work by plugging in the old X10 tabletop MC460 mini controller, but even then, the mini controller has to be plugged in to the "right" outlet for that particular light to work. The X10 coupler I have been using is the SignaLinc 4816A2, which plugs into the dryer outlet. Removing it makes no difference. So, either the SignaLinc is shot, or, I've got something killing the powerline signals. Does the old X10 SignaLinc need to be replaced with something newer, that also works with Insteon, and/or do I need to start deploying FilterLincs?

I came home from work today, prepared to spend the evening with all this... First thing I tried was moving the ISY and PLM up to the wiring closet, and plugging in directly to a port on the Uverse gateway. Bada bing, the 2477S is responding to both on and off commands from the Admin Console, and seems to do so reliably. So for now, it seems as if the issue has been resolved. I don't yet know if it was due to getting it on a different power leg, or moving it off of the circuit that the PC is on... Or both. Will have to give it a bit to see if it holds configuration, while I see if I can get some X10 commands to work.... Finder still doesn't automatically detect the ISY (have manually added the static IP). This seems to be a common problem I've seen lots of posts on - does it ever work for anyone? But not having it automatically detected leaves a feeling in the back of my mind that something's still not quite right. I'll pull the phase coupler a bit later, and see what impact that might have on things. Thanks again to everyone for the assist! -DBB

All good info, here. Thanks, Paul, Stu, and Brian! Paul, my Insteon switches only came with a single sheet of instructions on how to install them, so thank you for the link. I do have the ISY/PLM on the same outlet as my PC; it's where all my easily accessible network gear is located, so it might be a tall order to relocate things to another point with a network drop handy. Could this also be the cause of Finder not detecting my ISY? I'll double-check the X10 plug-in coupler to see if I can tell what it is - I put it in a long time ago. I've also seen mention of a 4-tap test, but have no idea what that is. Will see if I can find more info on that. Will report back with what I find. Thanks, again, DBB

I have have several X10 switches around the house, but recently got the UD ISY 994i and a few Switchlincs. I've only installed one of the 2477S switches to test. It's installed to is a single, incandescent ceiling light, and works fine. It's the remote operation of it that fails... I seem to be having communications issues. I've updated Java, etc. per the Quick Start I found online, but the Finder never picks up the ISY; I have to add it manually using its IP. The PLM shows all good in the diagnostics. From the ISY994i, I can occasionally link to and turn on the Switchlinc, but can never turn it off, due to a communication error. More times than not, though, the Switchlinc can't be reached at all, and shows a red exclamation in the console. I've only been able to find a couple of posts elsewhere that were similar, but the issues were usually due to LED or CFL loads. Is this a power line issue? Does Insteon require a phase coupler, like X10 did (I have a plug-in coupler at the electric dryer, so I wouldn't think that could be an issue). I've also seen posts on firewall issues, but the WiKi has no content for Windows Firewall, so I'm not sure what, if anything needs to be added/opened up there. I also see that Avast creates issues - I'm running Nortons AV, and have not seen anything relating to that. The ISY/PLM is plugged into a Cisco switch in my home office, which runs back to the UVerse residential gateway upstairs. Was hoping for more of a plug and play setup with this and more stability than what X10 gave, but would welcome any insight someone might have. Thanks, DBB