Andy P

I have a folder called Away Random Lights. It has a condition based on a variable that I set with a keypad button. So when that button is on, the variable is set to 1 and all the programs in the folder are enabled. When I turn that button off, the variable goes to zero and all the programs are disabled. Makes it easy to set random lights as I go out the door and turn them back off when I come back in. Away Random Lights - [ID 0023][Parent 0001] Folder Conditions for 'Away Random Lights' If $State_Random is 1 Then Allow the programs in this folder to run. AND, in direct response to your other question, it is true that if you create a new folder with nothing in it, the right click will show you options for enable and disabled, but when you add a program to the folder, those options disappear. I consider this a bug, frankly. I can't think of any reason an empty folder would be enabled or disabled. Folder status should always be set by the folder conditions.

I have several of those i3 keypads and went through multiple attempts at doing something logical. Similar I have scenes called bright, normal, cozy and off. In the end, I decided that trying to keep the keypad in sync with which scene was active would never work in a way that would make me happy. So I started over and decided to make the buttons momentary on. Which means when you press the button it sends and on, But then inside the scene, I turn that button off. So it turns on, sets the scene and then turns off. This means I end up with essentially no buttons on except during the moment I am setting the scene, except the load button will always reflect that load if it is controlled by that keypad, so I normally just use the top button to turn that individual light on and off. I know this isn't quite what you asked but maybe spark some idea.

OK< thanks, I adjusted the code to strip off the F and everything is working again! Appreciate the response. Thanks, Andy

My downstream programming broke and I found the reason is that the device names now have a 'F' after their name, like this - used to be yomotionsens and now it is yomotionsensF for some reason? <node flag="128" nodeDefId="yomotionsensF"> <address>n008_8b4c020013c921</address> <name>Motion Kitchen</name> <family instance="8">10</family> <hint>0.0.0.0</hint> <parent type="3">32793</parent> <type>0.0.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n008_8b4c020013c921</pnode> </node> Also true for <node flag="128" nodeDefId="yovibrasensF"> and <node flag="128" nodeDefId="yoleaksensF"> and <node flag="128" nodeDefId="yothsensF"> But not for <node flag="128" nodeDefId="yodoorsens"> It is not just in the admin console, it is also in the polyglot console Node Name 3 Address NodeDef Primary Node Hint Enabled Is Primary Delete Fan HVAC 1 8b4c0100097447 yovibrasensF 8b4c0100097447 0x00000000 true true

I used to do that, too, but my other house occupants couldn't get their heads around the idea that pressing off would turn on the light! However, I do make use of it to turn other lights off. For example, if you turn off the over sink light and then press off again it turns off the under counter lights which have a separate switch farther away.

Yup, I am back connected. Thanks!

ok, i did submit a ticket as you asked

Rebooted two of them. Still not connected

The portal maintenance was reported as finished 40 minutes ago. All of my EISY still show offline. How much longer should I expect it to be?

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: