Guy Lavoie

First step: if you go look at one of these lights in the admin console (in the device list) and turn them on or off at the switch, do you see the status change on the screen?

Mousetrap automation. Wow...I hadn't thought of that. I almost wish I needed one!

What do you have in the pavilion that needs to be controlled, and how many? Does your IP network work well there, wifi or wired? If so, there might be IP based devices that you could use instead of Insteon for that location.

I can choose between my eisy and Polisy directly on the app, at least for local access. If you're accessing them through the portal, they will likely each need their own account. If the number of devices is limited in two of the buildings, you could use one eisy as a "master" (the one with most devices), and use the networking module to send REST commands to the other two. It would require more programming, but would make it look more like one large system, all controllable from one account.

For posterity...what did you end up doing?

1- you can usually choose the backup file by browsing your computer 2- Could you see the status changes in the admin console when operating the switches manually? 3- If the switches are already listed in the admin console, did you delete them first?

What's that saying: opposites attract?

Seriously though, if you're in Canada and looking to buy a eisy, I'd do it now. Sale price at Canadian distributor is ending tomorrow Feb 3rd, and if it gets hit in this tariff war, it could jump up an extra $100.

And let's not forget the groundhog's prognosis.

So around Jan 41st or so... Always out for a laugh here, it'll be ready when it's ready.

The Venstar T7900 has that capability, and there is a plugin for it. But the plugin itself doesn't have the ability to switch heating mode to auxiliary.

Not for long...

From zero to two solutions...isn't life grand? Really, whatever works for you. I don't think we can say there is a right or wrong way. I usually like to stick to the most adaptable way (that I can reuse in the future). The sockets method is the lowest level, and can be adapted for use with other things like tcp connections, raw, etc. Think of the options you see in the networking module on the eisy.

If you have other routines using fast-ons on other switches, do they still work?

Good luck! Keep us posted.

Well that's the thing you need to determine. That test program is pretty well the absolute minimal program you can have to try this. If you're getting a timeout error on the "recv" part, then the initial "connect" seems to be working, but not getting the response. Try just connecting first. Like this (changes are after the "else" statement). import socket HOST = "192.168.0.145" PORT = 8080 with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s: s.settimeout(2) try: s.connect((HOST, PORT)) except socket.timeout as err: print("timeout!") except socket.error as err: print("error!") else: print ("connected")

Start by sending a hardcoded value, just to test that the plumbing works. Then you can work in your actual data and other details.

I had a bit of time this afternoon and got it tested and working. Here is a python test program that sends "/rest/vars/set/2/6/9" to a eisy at IP address 192.168.0.145. This sets state variable id #6 to a value of 9. Notice the part "Basic cGFzc3dvcmQ=", that's the admin password "password" encoded to a Base 64 value (I used "password" so that you can test that you get the same result, you'll need to encode you own password). You an encode a password here: https://www.base64encode.net/ Let me know if that works! import socket HOST = "192.168.0.145" PORT = 8080 with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s: s.settimeout(2) try: s.connect((HOST, PORT)) except socket.timeout as err: print("timeout!") except socket.error as err: print("error!") else: # send REST command s.sendall(b"GET /rest/vars/set/2/6/9 HTTP/1.0\x0d\x0aHost: 192.168.0.145\x0d\x0aAuthorization: Basic cGFzc3dvcmQ=\x0d\x0a\x0d\x0a") data = s.recv(1024) s.close print(f"received {data!r}")

Oh my, my first computer was a TRS-80 model 1. The best $1000 I ever spent. The things I learned with it, including assembler programming, served me so well for my 40 year IT career.

I learn that way too. It's slow, but the knowledge acquired sticks! Two noobs should be able to get this figured out...

Well let me dig up the sample Python code that I did to do that. I'm still learning Python and created two plugins, in wanting to learn to create a fancier one. I have a code sample that connects to a socket and writes data, and I also have VB6 samples of creating REST commands, so know how to make http GET commands with raw bytes. I'll just need to put the two together... I might have a chance to check that out tomorrow.

Are you able to open a socket in Python, connect to a tcp socket, and send raw data? If so, I can give you some help with what the raw bytes need to be to create a REST request.

The eisy uses unix commands. This will be very different from any controller previous to the Polisy and eisy. As for copying files in and out of it, the "scp" is what's available. Thankfully Windows supports scp. There is no ftp, rlogin, rcp, rsh or any of those in the eisy.

That 5.9.1 has me intrigued. And I'm not alone...

Well wait a bit... Maybe you have another issue that's affecting performance, like something stuck in a tight loop, making it slow. Is the eisy itself unusually hot to touch? If you look at the "summary" tab under programs, does anything look unusual in the "Activity" column? Anything strange like "running" constantly or even "out of memory"? You could try disabling some of the programs that appear to be running constantly, as a test.