lilyoyo1

Thats not what Im asking. If you click on the controller of your scene in the admin console (each keypad which should be RED), did you configure what your switches are supposed to do there also?

Did you update the controllers of the scene too? Both controller and scene itself must be updated.

Did you follow the migration procedure or simply did a restore?

Nothing changes from what you are accustomed to and how those things work. Mobilinc hasn't been updated in years (disco'd), so while it'll work, it will not be capable of doing everything that EISY does. You have access to the nodeserver store which has been covered extensively on these forums so I wont go into details on that.. There is a whole subsection on the forums with the different nodeservers that are available. In addition, if you get the zmatter dongle, you have access to zwave, zigbee (growing support), and Matter in the future.

I e tried many different lightstrips over the years and none compare to hue (my opinion). The ease of setup and app use is a major reason. Lifx is much more confusing and disconnected. While other strips have some novel features that I wish hue had when it comes to Multi-Color strips, hue's take on it still seems much more elegant though I wish they were cheaper. Since you're using the dish, I say why choose 1? While I use hue mainly, I still have a couple of lifx strips that I use for specific effects in certain area that hue isn't capable of. You can do the same thing though I'd recommend keeping things all the same in singular areas. That way, when you make a change, all devices changes at 1 time vs each device 1 by 1 which lessens the experience.

On these forums. Look for the sub forum software release and updates. Click on recent firmwares. Because there may be manual intervention and udi wants you to read the instructions in it's entirety, there is no auto update to 5.xx

Hue isn't the only game in town when it comes to zigbee based bulbs. You also do not need the nodeserver to control them as network resources work with them as well (I use network resources with mine). You just won't have 2 way communication. If you're like me and don't use the app, it's not a problem anyway. Google isy hue for dummies and you'll find an easy to follow write up. Whether it's the isy or eisy, it takes time and patience to learn. It's a great system. You just have to be willing to put in the work to experiment. It would be like that for any of these systems.

My stuff is pretty simple. All of our outdoor lighting is Hue stuff. During Halloween and Christmas, instead of turning on normally, everything will be based on the event we're celebrating.

You can't assume anything when it comes to automation devices since companies are able to fork codes to use it how they desire. Sticking with zigbee for example; Directv peanut remotes uses zigbee but you can't add it to other zigbee based systems. Ditto for Control 4. Hue used to be a lot worse than they are now but still isnt easy to work with for direct integration. The best path is to ask if something is compatible prior to investing (or purchase 1 for testing).

That's not normal behavior. What's your firmware and UI? What's the first program that runs when you reboot?

You need to use the hue nodeserver or network resources to connect your eisy to your hue hub

Do you have a recent backup? If so, just upload that.

On the Insteon side of things, they had a separate dual relay outlet and a single dimmable outlet (that you're referring to). The i3 version simply replaces the relay version. Hopefully they'll release a dimmable version in the future.

You're correct. Isy does not support i3 devices. Only polisy and eisy on the latest firmware

Are you still running any network resources? If so, do those stop working as well?

There is a full thread on this issue:

Are you still using network resources too? Do those work when the nodeserver doesn't

There is no timeout for the remote. Your options are toggle, non toggle on and non toggle off. For what you're trying to do, you're better off using it as a 4 button so that you have separate on/off buttons. Then you can program normally using toggle mode. If you must use it as an 8 button, non toggle on mode is best, you'll just need to use variables to keep track of your button presses and write programs accordingly to ensure the variable is correct regardless of how you control your system. Due to the amount of work involved, this is why I recommend using your remote in 4 button mode. Everytime you turn on the lights, the variable is set to 1. If the variable is 1 and you hit the remote in non toggle on mode, then you would have a program run that turns it off and sets the variable to 0 If the variable is 0 and the remote sends an on command, the lights would turn on and set the variable to 1.

The easiest is through a paid portal subscription. Otherwise, you'll have to open up ports in your router etc. You can find the instructions for portal subscription in the wiki

I'd update your isy to at least 4.9 to see if that works.

factory reset the device then try again. Make sure that your UI matches the firmware. If you're manually putting in the device address, make sure that its the right one. Sometimes, people mistake a B for an 8 or D

A device can only be a controller of 1 scene. You would create a single scene and add every device/kpl button to that scene and control it vs. Each individual scene.

I think this is an individual choice. While the eisy has better performance, I don't know if the amount of work you'll have to do is worth the upgrade. The jump from isy to polisy is much greater then the jump from polisy to eisy. It's like smart phones. Sure the galaxy s23 processor is faster than the galaxy see, but are the gains noticeable enough to justify upgrading?.

I don't use X10 nor the app so I can't answer those questions. The isy wiki shows how X10 works without the module you have and what it allows you to do. Without the module you would not be able to name your X10 devices like you can now.

Are you sure your "new" one isn't a 994? I don't believe udi is transferring modules anymore; especially when it comes to the 99 which has been disco'd for 10+ years. Unfortunately you're stuck with your setup as is. Eisy should work with x10- you just won't have the devices in the device tree like the module allows.