Andy P

This is not something I would normally expect to do, but I had a perfectly running EISY R1 with a ton of devices in my house and I want to set up a small EISY/Insteon setup in a different property. It seemed like a waste to put the new more powerful R2 at the small property, so I decided to swap out the R1 with the R2 and then factory reset the R1 to use at the new property. in doing this, my first thought was, I am going to preserve all the devices by moving the PLM and zwave dongle from the R1 to R2. That is exactly what I did and it made the change very simple. Run a backup of the R1 both the admin console and the PG3 console. Shut it down Move the PLM and dongle to the R2 and power it up. Open the admin console on the R2 and make sure it is running nicely (with no devices). Run restore on the R2 and wait many hours. In fact I waited over night and then finally just rebooted it because it never really told me it was done with the restore. After the reboot, everything is already working! Except the Polyglot stuff. Go into Polyglot console and do a restore. Oops, I dont have any licenses. Buy all new licenses for the node servers. Restart everything. All the nodes are now alive. Buy a portal license for the R2. Activate it and rename the R1 to old house - oops, can't do that unless I power it back up again, Ok, now everything is looking good on the R2. Well, except Alexa is tied to the R1. Delete all the commands from the R1 in the portal from Alexa Add all the commands from the R2 in the portal to Alexa Give it a day to make sure everything is working. Ok, factory reset the R1 by pressing the front button 10 times. So, this all ran smoothly and now I have the R1 to install at the new location, It already has the portal license and node server license, so I just need to plug in my spare PLM and should be ready to go. Just sharing my experience. Anything I could/should have done differently? Take care., Andy

Yes, exactly. The original EISY had a usb-c port next to the ethernet jack for power input and then a blue usb A port next to the hdmi ports. The new R2 still has the usb-c port for power input next to the ethernet jack, but the blue usb A port on the back was replaced with a usb c port. There are still 3 usb A ports on the side.

When Insteon was on the ropes I started down the path of installing zooz switches controlled with habitat. I was disappointed by the primitive programming method of the habitat but I could see why it might appeal to non programmers. I really missed the scene support and multiway flexibility of the ISY plus Insteon. So when Insteon was resurrected I got a couple EISY hubs and some new i3 stuff and pretty much removed the habitat and zooz, but the few items I have remaining there have been rock solid with no real motivation to change. I never had more than 10% of my devices on hubitat so the decision to move back was easy for me. For a simple set up with few complex automations I think hubitat is fine. Some of the stuff I do with multiple dimming levels, motion triggered temporary lighting and timed automations would be difficult on the hubitat and are pretty easy on the EISY. Also love the REST interface for custom dashboards and the polyglot integration of Lutron, Yolink, etc. So my advice is only move if you have a compelling reason that the current setup does not support for you.

Ok, probably a joke, but actually no, it might not improve the cooling. For one thing the thermal contact between the EISY and the heat sink is sub optimal. You need to grind the top of the case smooth and then use thermal paste to attach the heat sink. Also, you have blocked the radiant heat from the device. May be possible you have unintentionally reduced the effectiveness of your z wave dongle by partially blocking the signal with the large fins. But, I got a good laugh out of it! I think I have one of those sitting around somewhere.

Glad it worked for you! I also had no issues on two production EISY units. I did also manually add the local access to the finder so I didn’t have to use the portal credentials for the ones that it found automatically. One thing I noticed a couple days later was a polyglot node not updating the node correctly, So I ended up restarting everything and it cleaned up just fine.

I started down the path of subscribing to EISY events and after a couple weeks, I dumped it in favor of polling with the REST API. You may have a better experience but I found that pulling the data at my defined interval was less of a load on the EISY than the subscription and I was getting a lot of stuff I didn't need. Look here ISY Developers:API:REST Interface - Universal Devices, Inc. Wiki and try this in a browser with your EISY IP address 192.168.3.19:8080/rest/status And that allows me to use the data to format it like this:

I don't know if it matters, but your finder shows http. Try ADDing an entry with https:// and use port ipaddress:8443

In the finder, is the URL listed as an IP address or some form of the name of the ISY? If it is not listed as the IP address, click on ADD and then enter https://123.123.123.123:8443/desc as the URL where you substitute the correct IP address. oh, @IndyMike just posted the same thing!

I use the Aqara FP2. Unfortunately, it does not connect with the EISY directly. I am using it with Apple Home(kit). I like how you can set up zones and count the number of people and duration of presence.

When referring to a node, the # becomes the node identifier. Besides the insteon address, you can also use polyglot created devices like this Rain Tomorrow ${sys.node.n007_forecast_1.GV18} ${sys.node.n007_forecast_1.GV13} Accumulation ${sys.node.n007_forecast_1.GV8} When you use a program to trigger a notification, the # automatically gets replaced by the ID of the program that called it. ${sys.program.#.address} ${sys.program.#.name} ${sys.program.#.status} ${sys.date} ${sys.time} program[97] Garage Closed True 2025/03/30 06:10:00 AM

This is a shot in the dark, but I had an issue kind of like this where the remote switches work but didn't turn on the load switch. Turns out that in the scene definition, somehow those remote switches were set to turn the remote on to 0% instead of 100%. When I fixed the scene, the remote switches worked as expected. Just another quick thing to check.

You probably did the calculation, but at 5200 lm/fixture, 12 fixtures, 1080 square feet you are around 58 lm/sqft. That is fine for general lighting but you would want more like 75 lm/sqft if it is a work area.

My imagination says that they will use what they learned from the U-D mobile app and apply that to a full function console.

Every i3 keypad I get from the factory is incorrectly set with the bottom as the load. I posted previously my interaction with Insteon on this topic and they added a warning to their product page that says this as well. Anyway, you need to factory reset the device to get the load back to the top button. Read the information at these two links. i3 Keypad Setup IMPORTANT: We’ve discovered an issue where some i3 devices may have shipped with a configuration issue that impacts performance and reliability. To ensure best performance and reliability, factory reset before using. How to manually configure Insteon devices Wall Switches and Keypads Air gap the switch by pulling out the set button, LED will turn off Press and hold set button all the way in and hold down. You will hear a long beep. Keep the set button held down until the end of the beep, then release. Switch will double beep. Then, LED and connected fixture will turn on to indicate factory reset is completed. 

agree with @paulbates - I had a similar issue with UFO lights in a barn. I ended up splitting the lights across two circuits. The added benefit was the ability to turn on/off half of the lights when I didn't need full illumination. Then i used an I3 4 button keypad to control the switches in different scenes. btw each light is 18,000 lumens and 150 watts (which is 120 lumens per watt - pretty standard at the high end). So 7 of these was also more than I felt comfortable putting on one switch.