dbuss

@Geddy @IndyMike @Guy Lavoie I appreciate all the suggestions on these two issues. Regarding the 2477D switch. I discovered why the programs weren't working...they were both disabled. I have some programs that for some reason get disabled and I've yet to discover why. I've done the event viewer test and there are three hops left. The device queries just fine. The only thing that I'm experiencing is when I start the admin consoles it says it can't communicate with that switch. Regarding the 2342-242 mini remote. I performed a restore, but it didn't resolve the issue of when the admin starts I get the message that that mini remote was added. Again, it performs as expected. I think I will factory reset the mini remote and re-add it. Thanks again for all your suggestions.

I have a 2477D switch that comes as not able to communicate when I open the admin console. I can control the switch from the admin console and UD mobile. However, it's not working when controlled by a program.. I've restored the switch twice with the same results. Any ideas would be appreciated. My second issue is with a mini remote switch. It added just fine and works as it should. However, every time I open the admin consoles i get a message that this switch was added. Is there a way to eliminate that message? Thank you!

Have you checked this? Slow or Hanging Admin Console: If the console is slow, you may need to allocate more memory to the Java runtime. You can do this by opening the Java Control Panel, going to the Java tab, and adding or modifying the -Xmx runtime parameter, for example, to -Xmx512m to set the maximum memory to 512MB

I’ve received this message as well, though only a few times — not enough to determine whether it’s coming from the same device each time. Could this possibly be related to Alexa+ relying more on internet-based communication rather than local communication?

Even with the slower response times, I wouldn't switch back. Alexa+ does so much more today, and I'm sure she'll do more as they work everything out.

I've been using Alexa+ for a few months. It controls the ISY devices just as before. However, Alexa+ doesn't store information locally as the Alexa does. I've noticed that running routines with Alexa+ takes a bit longer to get responses.

I had to use SSH when I updated to 6.0 over the weekend. All went well and I like the web-based interface.

I'm wondering the same thing about the app not supporting the Pro models. I have two sets of curtain lights, four strip lights, an on-off switch, an LED bulb string, and a TV backlight.

The Govee plugin controller will use the same name that you use in the app. Try pressing the restart button in the Govee plugin? Then try pressing load profile. The Govee lights must appear in the Govee plugin, or they won't appear in the admin console.

How many nodes do you see in the Govee plugin page? Where you see 9 in mine, you should see 2 in yours. One node is for the Govee controller, and one node is for your lights, with the name you gave the lights in your Govee app.

They should show up under "Govee" in the admin console. If you have one set of Govee lights, you should see two nodes in the Govee plugin. If you don't, restart the plugin.

Open your Eisy admin console. You should see the "Govee" plugin in the admin console network list. Click on it and then click on discover. It should discover your Govee lights.

Have you looked at this information? https://wiki.universal-devices.com/Eisy:User_Guide

Yes, you can.

I had the same issues. A reboot resolved my issues. This is the first time I've experienced any issues with the time changes.