dbuss

@asbrilTry closing the browser tab and then use the iox launcher to open a new pg3 tab in your browser. This has worked for me.

Look at this post.

Sometimes my eisy is not in the launcher. Most of the time all I need to do is refresh the launcher and it appears.

The second part of Michel's instructions solved my problem also. be sure and clear your Java cache and download a fresh copy of the launcher each time you update. These two procedures got my Polisy and eisy updated.

Is your router Wi-Fi 6 , No Is you connection on 2.4 or 5ghz 5ghz Do you get any error messages in UD Mobile when you're connected via Wi-Fi. No Are you connecting via a LAN or the Portal. I can connect either way.

That's it. Thank you!

I can't see my eisy on the wireless network either, even though it's connected by WIFI.

Does the ISY that has the 5.3.4 firmware have Z-Wave installed? If it does, it would have the series 500 board installed since it has the 5.3.4 firmware. The series 500 Z-Wave board will not work with 4.9 firmware. if it has the Z-wave board installed and you aren;t using Z-wave your could remove the board and then install the 4.9 firmware. Here's where you can fine the 4.9 firmware.

I have the same issues with Govee LED lights using the Govee node server. The lights will not stay connected. They will disconnect and then re-connect at some point. The lights seem to not have the problem of staying connected to Alexa. My node servers are in my Polisy. I haven't migrated them to my eisy yet.

The AC in my eisy has options for both.

I updated my eisy to 5.5.2 also with no problems. I haven't installed the matter board yet. Node servers work and I attached a PLM and added a couple of Insteon devices with no problems. I'm waiting for things to get smoothed out before I attempt any migration. My ISY and Polisy are working just fine.

I reinstalled the node server and that solved it for me.

Did you clear your Java cache and reinstall the ISY Launcher before you reopened the AC?

Have you enabled Insteon in the configuration/system tab?

I installed two node servers and had to reinstall each one twice to get them to start.

I requested and received a new API. With the new API the Govee lights were discovered. I had to query each to be able to control them. So, it may be that the lights need to be queried every so often. Problem resolved for now.

I just discovered the problem. A human error no less! The variable ID I was trying to use was already used for something else. Problem solved. Thank you for your response!

I'm attempting to expose a state variable as a motion sensor in Alexa. I've changed the name of the variable and the spoken several times. However, I continue to get "Device already has a spoken". I can expose the variable as a switch using the same variable and spoken names and Alexa accepts it. I have several other state variables exposed as motion sensors with no problems. Thank you!

All of a sudden the Govee node server stopped controlling my Govee lights. It's been working great until now. The AC can't turn the lights on or off and the status of the lights doesn't change when I turn the lights on or off with the Govee app. Any help on solving this would be appreciated. Thank you!

Have you looked through this post? It got my Polisy operating correctly.

I don't have my eisy yet. However, when you go to the node server store and click on a node server that you own, does it give you the option to install it or purchase it?

I have the lights configured to work locally. They work with Lumina Stream. However, I am unable to get them to work with the MagicHome app or MagicHome NS.

Will the MagicHome node server work with Govee lights? The node server will not discover the Govee lights. I manually entered the information and the lights were added to the nodes list. However, they will not connect. The nodes show up in the Admin Console as not connected. The log shows "socket connect failed". The Govee node server is working fine. I wanted to compare MagicHome to Govee if possible. Thank you!

Have you done this? Java runtime memory (when Admin Console is very slow to respond) - If the admin console is slow to respond, it is likely you need to increase the amount of memory allocated to the Java runtime (JRE). - Open the Java Control Panel, select Java tab, press View button, then add or modify the Runtime Parameter -Xmx to the following: o -Xmx512m - Press Ok to close the window, then Press Apply to save the changes

Same here.