apostolakisl

I use my Elk relays to control irrigation and have that integrated with ISY. Another option would be a webcontrol board and a relay bank. Maybe $50 for the two to control 8 zones. There is a webcontrol node server. I don't know if those boards are sold new anymore, but here is one on ebay. I have several of them doing various things around the house and integrated with ISY. https://www.ebay.com/itm/336129256923?_skw=cai+webcontrol&itmmeta=01K326SYWY1QYDW4H3MBND19B0&hash=item4e42dd6ddb:g:8YEAAeSwAkFooRsY&itmprp=enc%3AAQAKAAAA0FkggFvd1GGDu0w3yXCmi1eVIQeGiRgO5M5LmYnQEv3p%2BIhyUEtQquhsRINAxFdq%2FdRej98p42PvwfUkQWK0YUslj4JOnsT7zTlv7xZ2I9TpSQ%2B7c4z4LACz%2B%2BfgckFd7VeqKMKQqMhMngazOCAUAewwJSB8V2439LpHaX8%2BEmqtyRPcp42R78%2Bff%2FGBU86L8WOLMkXiGKWMmFfQsT7a8K0HzUyh6ig2%2BaBVTh8xe9uy23cg5aX7JgAvKAGm2nQ1W%2Fo88cneLD6vw3%2Bk%2BdnIbaY%3D|tkp%3ABk9SR9Du58aYZg&pfm=0 And then you need a relay board like this https://www.ebay.com/itm/185775465434?_skw=8+relay+board&itmmeta=01K326YRXR65XFCVN50QF35MQ8&hash=item2b4114a3da:g:hMgAAOSwO0lj2uFr&itmprp=enc%3AAQAKAAAA8FkggFvd1GGDu0w3yXCmi1dusklByeQzJ4KdARXnhds0p6i4GAMkfAaRYSzqfdQCGEvrZeSBYNHvuVNQugVF%2F01TX1YsHyurhi0rKB2fCpLM44ZFs5IaKU6%2BcJGR9vtY%2BUaIUOWoU8naevz0PnwLXdBQ3FQXxGNp2Dw2YOQ40FH4s9Yd1%2F%2BCP5DbKJZgfRt95537oaMC4FqQmRekUu8FBGqgM4UCVnD0g2AoRhUN0AuNgcdWdupt1XGEsu95xrQ76KZfSEHjTTU5utNwj818ClJ29%2BYOdPwK0LixygYq9Tz22dYF3hbPhxgDpTxcIVNSnw%3D%3D|tkp%3ABk9SR4qP-8aYZg&pfm=0 The relay board needs to trigger the relay using only ma of current. Basically, ones that say they can work with rpi or arduino. The webcontrol board does not have enough current on the outputs to power a relay, only a signal voltage.

Do they work with Alexa? I have some fans that are knock off Big A$$ fans that work with Alexa and I use that as a go-between. It is actually working quite well. Using variables Alexa will keep ISY sync'd to the fans regardless of how you control the fans. I can control them using the fans own remote, Alexa, and ISY and everything stays sync'd.

Are you using the itach node server or network resources? You say you are using the node server but you are showing network resource screen shot. The flirc and the itach are fully separate so having or not having a flirc is not going to affect the itach. This is an example of one of my "body" sections for a network resource. sendir,1:1,1,38343,1,1,16,179,12,183,12,183,13,182,14,181,16,275,19,176,19,272,19,176,19,176,19,176,19,3834\r\n\n And this is what my itach node server setup looks like for one device. I had an itach prior to the node server existing so I have some things still on the network resources but have been trying to moving everything over to the node server because it is nicer to work with once configured. "whole house on","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,178,19,274,19,178,19,178,19,178,19,274,19,3858" "whole house off","sendir,1:1,1,38343,1,1,15,180,14,181,19,176,19,176,19,176,19,272,19,272,19,176,19,176,19,177,19,272,19,4907" "system off","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,274,19,274,19,274,19,178,19,178,19,178,19,3858" "Zone on/off","sendir,1:1,1,38226,1,1,10,185,10,184,14,181,19,176,19,176,19,176,19,176,19,176,19,176,19,176,19,176,19,3822" "Volume Up","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,178,19,178,19,178,19,274,19,178,19,178,19,3858" "Volume Down","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,274,19,178,19,178,19,274,19,178,19,178,19,3858" "Mute","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,178,19,178,19,178,19,178,19,274,19,178,19,3858" "Do Not Disturb","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,178,19,178,19,178,19,178,19,274,19,274,19,3858" "Source 6","sendir,1:1,1,38343,1,1,16,179,12,183,12,183,13,182,14,181,16,275,19,176,19,272,19,176,19,176,19,176,19,3834" "Source 5","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,178,19,178,19,274,19,274,19,178,19,178,19,3858" "Source 4","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,178,19,178,19,274,19,178,19,274,19,274,19,3858" "Source 3","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,178,19,178,19,274,19,178,19,274,19,178,19,3858" "Source 2","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,178,19,178,19,274,19,178,19,178,19,274,19,3858" "Source 1","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,178,19,178,19,274,19,178,19,178,19,178,19,3858" Also: I noticed your are sending network resources on port 4997. Mine is setup on port 4998. ***Pretty sure your port number needs to be changed to 4998. All the docs that came up on a google said it works on port 4998.

A sensor that tells you the door is moving and which way would be nice. I have issues with my automation where, for example, the garage door is already closing, and a program gets triggered to close the door, and it doesn't know the door is already closing, so it "hits the button", which of course reverses the door to go back open.

I believe I have this solved. I put all 40 codes on the flirc (both codes for each button). ISY Codes 1-26 are Flirc keys A-Z, then 28-37 ISY codes are flirc keys 0-9, then 38-40 ISY codes are flirc keys F1-F3. I attached the flirc config file. Not sure if matters, but you might need to be in keyboard mode in flirc when you import it. They were obviously created in keyboard mode. ISY40CodesHarmony.fcfg

Good to hear it is all working again. But something isn't right with your communication. It shouldn't have struggled to do write to those devices, and required multiple attempts. Perhaps your PLM is weak or perhaps you have signal suckers or noise makers on your network.

You can tell if the links are writing by watching the pop up window. Unfortunately, ISY doesn't make it obvious, but if you watch the small print writing in the bottom left corner of the pop up window, it will show you the traffic that is going on. It will show you all kinds of random traffic, but if you watch it will show link numbers. If every few seconds you see a that number has gone up (ignoring other random other messages in between), that is a good sign. If you keep seeing it stuck on the same number, not good. Also, the devices on the left window will start returning one by one to their normal appearance without any 1011, exclamation points, or other.

I went through and manually added every one of the 40 buttons twice. Mostly this works. However, 3 pairs of buttons appear to share codes at least as far as flirc is concerned. This was not the case when 994i was receiving the signals using the same Harmony remote. I installed the ISY codes on that Harmony from the Harmony library which had the ISY codes in it already (did this like a decade ago). I deleted and readded these buttons several times without any success in fixing the issue. Matching ISY IR codes according to flirc are 10/13 11/14 12/16

Not sure what gives here. I have the flirc installed and loaded in the default ISY 40 commands found in this thread. They showed up as I pressed the buttons. But it only works on every other time I hit the button. I tried deleting the whole thing and started over teaching the flirc manually the 40 commands. Same story. I confirmed every other button press by watching the "pressed" vs "idle" reported in the admin console as well as creating a program that runs on the button press. It is like it is a toggle or something, but there is no option to make these things a toggle. I tested it with a bunch of the buttons. I am using my Harmony remote, the same remote that worked flawlessly with 994ir. EDIT: I think I found the answer here in the forum. I'll need to play with this, not sure how to get the same button to respond to two different commands in flirc.

So if indeed you had amazing amount of noise in your network that you have now removed. You should be able to restore you plm and you made need to do a restore devices as well. If you have a backup of isy that is current, you could start from scratch. 1) Restore backup 2) Plug in PLM (if not already) and reboot 3)Confirm PLM attached via tools/diagnostics/plm info, 4) Factory Reset PLM (shouldn't be needed, but why not) 5) Restore PLM - note if you are restoring the plm and it is not the same plm as you were using when you made the backup, then it will need to write to all of your devices. I would set the isy to not do wireless devices at this time if you have any by clicking off that icon, also, disable any devices that are not currently plugged in/working so as to not slow down the restore. 3) Restore Devices if needed (same stuff in the note section applies here)

It sounds like your plm isn't working or your connection between eisy and plm is no good. Regardless of how screwed up your links may or not be, when you write to devices, eisy will write the links assuming you are able to communicate with the devices. And you are not communicating. Check under tools/diagnostics/plm info Make sure it lists your plm and says connected. I suppose it is also possible that something is so awful in your network that even though the plm is connected and working, there is so much noise that it can't talk to a single device. unlikely to say the least, but I suppose possible.

Yes, reinstall of node after development package install fixed it.

I did that. Rebooted eisy, still have the same error.

Dev packages? Where/how do I do that? Thx. Lou

I have had plenty of instances where a node looks good, but doesn't function. Reboots typically fix it. Just yesterday I had to reboot blue iris node. Blue iris said connected, but wasn't. The heartbeat system in nodelink never fails me. I actually went through some hoops to get nodelink back because it was so stable.

My emporia vue was offline. Restarting did nothing. I then deleted it and reinstalled it. Still says disconnected. Double checked my username/password and it is correct. The Android app and the web app both access the unit and display the current data. The log is as follows. A bunch of errors there at the end and no further log develops. These same errors were there before I uninstalled and reinstalled. I know it has worked quite recently, but can't recall if that was before or after I switched to eisy from polisy. I made that switch 2 weeks ago. I also, I recently updated eisy to the new firmware that supports the web ui. 2025-08-07 14:57:09.773 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2025-08-07 14:57:09.773 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2025-08-07 14:57:09.773 MainThread udi_interface INFO __init__:<module>: User=None 2025-08-07 14:57:09.774 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9027119_23 2025-08-07 14:57:09.774 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9027119_23 2025-08-07 14:57:09.774 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6NzE6MTkiLCJwcm9maWxlTnVtIjoyMywibG9nTGV2ZWwiOiJERUJVRyIsInRva2VuIjoidkRVQk9kQlE5QkctYksvaCIsIm1xdHRIb3N0IjoibG9jYWxob3N0IiwibXF0dFBvcnQiOjg4ODMsInNlY3VyZSI6MSwiaXNQRzN4Ijp0cnVlLCJwZzNWZXJzaW9uIjoiMy4zLjIxIiwiaXN5VmVyc2lvbiI6IjUuOS4xIiwiZWRpdGlvbiI6IkZyZWUifQ== 2025-08-07 14:57:09.774 MainThread udi_interface INFO __init__:<module>: Loading interface module 2025-08-07 14:57:09.817 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2025-08-07 14:57:10.336 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2025-08-07 14:57:10.560 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2025-08-07 14:57:10.560 MainThread udi_interface INFO __init__:<module>: Loading node module 2025-08-07 14:57:10.560 MainThread udi_interface INFO __init__:<module>: Loading custom module 2025-08-07 14:57:10.560 MainThread udi_interface INFO __init__:<module>: Loading isy module 2025-08-07 14:57:10.560 MainThread udi_interface INFO __init__:<module>: Loading OAuth module 2025-08-07 14:57:10.561 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2025-08-07 14:57:10.561 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.3.18 Starting... 2025-08-07 14:57:10.562 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2025-08-07 14:57:10.562 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9027119_23/vue.py", line 10, in <module> 2025-08-07 14:57:10.563 MainThread udi_interface ERROR udi_interface:write: import pyemvue 2025-08-07 14:57:10.563 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9027119_23/pyemvue/__init__.py", line 2, in <module> 2025-08-07 14:57:10.563 MainThread udi_interface ERROR udi_interface:write: from pyemvue.pyemvue import PyEmVue 2025-08-07 14:57:10.563 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9027119_23/pyemvue/pyemvue.py", line 8, in <module> 2025-08-07 14:57:10.563 MainThread udi_interface ERROR udi_interface:write: import boto3 2025-08-07 14:57:10.563 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2025-08-07 14:57:10.563 MainThread udi_interface ERROR udi_interface:write: : 2025-08-07 14:57:10.563 MainThread udi_interface ERROR udi_interface:write: No module named 'boto3' @bpwwer

Don't delete ISY Portal or you will lose your portal access. Unless you are getting rid of using ISY portal. I assume you are intending on using the portal. Without portal you will have to open ports on your router to access from offsite and you won't be able to use Alexa/Google and all of that stuff. And what you did to delete those orphan plugins is correct. However, you need to make sure you didn't have any of that stuff referenced in programs. Any program that referenced any of the deleted plugins will now be broken and won't run at all even if the rest of it makes sense. ISY program icons turn yellow when the program is broken.

With Polisy and 994i, there was a "pro" version, but with Eisy, I don't see that. Only the standard and ADR version. So I suppose that all Eisy units are "pro".

If a device write fails, you will also need to manually "write changes", so it is not just used for the pro version. If you make changes to a device that is not plugged in for example, or the com just fails for whatever reason. But "writing changes" only does anything at all if there are changes to write and you will know that by the presence of the green "0100" next to the device.

Write changes is mostly used for the pro version that allows you to make changes but not write them until a time of your choosing. Very helpful when making lots of changes to not have to wait for each change to write before moving on. Also if isy tried to write changes but had a com issue you can trigger another try.

You need to plug the plm into eisy or it will give you errors. The whole point of what I just wrote is that eisy won't change anything in the network unless you tell it to. Just plugging it in won't change your links.

Eisy won't change anything on any devices unless you tell it to. Scenes are all written on the plm and on the devices. ISY keeps track of what is supposed to be written in those links so you can restore the devices. But if you never tell it to restore a device/plm, it won't write anything and they will stay the same. In short, if you don't tell it to restore the plm or restore devices, your insteon network won't be changed.

I don't see where it would be a problem to have the 994 on and no plm attached in an insteon network that has an eisy running as well. I would shut down polyglot if you have that running on rpi and I would disable any programs using network resources and I would change the elk module credentials so it can't mess with your elk whilst you configure the eisy. Or you could isolate the 994 by plugging it into another network. Easy way would be if you have a spare router. Plug a computer and isy into it and nothing else and then it can't mess with anything.

I assume you could use "<name of location> fans <speed>" and create a routine that is not device specific. And the do "fans <speed>" that is device specific. Personally don't see myself controlling fans in a room I am not located in except for my shut down routine, and that is a single command that triggers an ISY program that then executes a shut down of all kinds of stuff.

This discussion got me playing with Alexa a bit. I discovered that you can have each device respond uniquely to a command. So for example, the Alexa on my back patio would respond to "fans high" by turning on the patio fans, and that same command in the exercise rm would turn on the fans there. To the point here, by isolating commands to the relevantly located Alexa, Each Alexa will have fewer commands to understand and thus lower the chance of it confusing commands.