eisy-ui 0.4.0 - Alpha release - Feedback

[tazman]

I installed 0.4.3 and the status are coming through on eisy.local except for the yolink plugin does not show for my temperature sensors. I also noticed UD Mobile does not load status unless you click on the item then it brings up the status but they load automatically when I'm on the local network.

[bmercier]

9 hours ago, tazman said:

I installed 0.4.3 and the status are coming through on eisy.local except for the yolink plugin does not show for my temperature sensors. I also noticed UD Mobile does not load status unless you click on the item then it brings up the status but they load automatically when I'm on the local network.

> the status are coming through on eisy.local

In eisy-ui? AC, UDM?

> except for the yolink plugin does not show for my temperature sensors.

What is it that does not show. The properties? The status values on the properties? Is that in eisy-ui, or AC and UDM connected on port 80 or 443?

[sjenkins]

great job, I have status & properties on everything, Insteon, nodes, zwave 

except yolink devices from that node server, get a status but no properties on any devices

Edited Thursday at 11:40 PM by sjenkins

[bmercier]

36 minutes ago, sjenkins said:

 

except yolink devices from that node server, get a status but no properties on any devices

 

Can you see the status for Yolink in AC?

[sjenkins]

4 minutes ago, bmercier said:

 

Can you see the status for Yolink in AC?

yes

[bmercier]

33 minutes ago, sjenkins said:

yes

Then I can think of one possibility.

There is a known issue in the current IoX release that would affect eisy-ui, but not the admin console. That will be resolved in the next IoX build.

To confirm that, open eisy-ui, open the browser console, and navigate from another node to your Yolink node. You should see and error related to a missing "editor".

[tazman]

13 hours ago, bmercier said:

> the status are coming through on eisy.local

In eisy-ui? AC, UDM?

> except for the yolink plugin does not show for my temperature sensors.

What is it that does not show. The properties? The status values on the properties? Is that in eisy-ui, or AC and UDM connected on port 80 or 443?

> the status are coming through on eisy.local

In eisy-ui? AC, UDM?

I was referring to the eisy-ui

For the yolink plugin I see the same as what @sjenkinsposted in his screen shots and it also shows correctly in UDM.

I think the issues I s waseeing with UDM might be related to the portal issues of lately because I did see it work at times today.

[GTench]

15 hours ago, bmercier said:

To confirm that, open eisy-ui, open the browser console, and navigate from another node to your Yolink node. You should see and error related to a missing "editor".

I have the same issue as @sjenkins

Not sure if this is exactly what you mean but I opened the nodes screen in eisy.local, selected a non Yolink node (shows properties correctly) then selected a Yolink node (no properties shown) but I do not see any error message

Not sure if this is at all related but I notice when I add in a Yolink node server, the Yolink devices show up scattered among all existing nodes in the AC. That is, they are not automatically grouped under a Yolink master node

[bmercier]

1 hour ago, GTench said:

I have the same issue as @sjenkins

Not sure if this is exactly what you mean but I opened the nodes screen in eisy.local, selected a non Yolink node (shows properties correctly) then selected a Yolink node (no properties shown) but I do not see any error message

You would not see an error in eisy-ui. It's in the browser console. Use the same steps, but look at the browser console (F12 on Chrome, tab "Console")

[GTench]

58 minutes ago, bmercier said:

You would not see anu error in eisy-ui. It's in the browser console. Use the same steps, but look at the browser console (F12 on Chrome, tab "Console")

Interesting. I see errors when I click on Zwave but not insteon or Yolink or other node servers like weatherflow. Here is what I see in the console

[bmercier]

4 minutes ago, GTench said:

Interesting. I see errors when I click on Zwave but not insteon or Yolink or other node servers like weatherflow. Here is what I see in the console

The 5 errors at the bottom should be fixed with the next IoX update.

If Yolink does not give you a similar error, then I need to investigate further why the status are not appearing.

[sjenkins]

I get the above, the last line will come up when I select any node except for the YoLink.  It will repeat if I select another node.

No additional lines come to the console when I select a YoLink node & receive no parameters.

 

Edited Friday at 09:26 PM by sjenkins

[bmercier]

3 hours ago, sjenkins said:

I get the above, the last line will come up when I select any node except for the YoLink.  It will repeat if I select another node.

No additional lines come to the console when I select a YoLink node & receive no parameters.

 

Ok thanks, will investigate further.

[apnar]

On 6/7/2025 at 8:13 PM, bmercier said:

Make sure to login with your portal credentials. Everything on port 443 requires portal creds, not IoX creds.

To get back to the regular IoX, I'm pretty sure an upgrade packages would do it. But I don't think that would fix statuses though.

@bmercier  Is this the future direction of the platform or just short term for easy testing?  One of the main appeals for me of the ISY devices over the years is they can be run 100% locally with the cloud stuff being optional.  Tying local device management to cloud credentials would obviously contradict that.

Regardless, exciting to see a replacement for the admin console in the works.  I have a straight forward all Insteon setup and the install went smoothly.  Only annoyance was having to add a manual entry for 8443 back to the launcher finder as mentioned by others.

[xlurkr]

18 hours ago, apnar said:

run 100% locally with the cloud stuff being optional

100% agree.  I love the cloud benefits, but I need to be able to configure and control everything when my broadband is down.  Not all nodeservers, of course, but all Insteon and Z-Wave.

-Tom

[bmercier]

@apnar, @xlurkr, eisy can run without connectivity, and it will stay that way. We have customers that need to run it in completely disconnected environments, and that won't change.

Currently, it can be confusing to use eisy. You need to use the admin console, PG3x, IoX and portal... and sometimes you need to use portal creds, sometimes IoX creds. In PG3x in particular, you need a double login, one locally and one to portal (System | Switch portal profile). 

With eisy-ui, one of the design direction is to simplify all this by providing a single interface with one set of credentials for everything, all while allowing to run completely disconnected.

But how can you use portal creds and run disconnected you may ask?

When you login to eisy-ui, if there is connectivity, it will validate the creds against portal. In addition, when you login, the creds are cached locally. If you attempts to login and eisy has no connectivity, login will work against the local copy of the creds. When you login "locally", cloud features will be disabled. The only requiremnent to use eisy-ui is that it must have had connectivity at least once. For corporate customers, this is done during provisioning.

What I describe above is partially implemented in the current eisu-ui release 0.4.3. It is implemented in dev, you will be able to test it in the next release.

FYI, portal creds cached locally are hashed, so if an eisy is compromised, your portal creds can't be discovered.

[xlurkr]

5 hours ago, bmercier said:

If you attempts to login and eisy has no connectivity, login will work against the local copy of the creds.

Thanks for the explanation.  You addressed the one thing I was worried about.  I worry no longer.

-Tom

[bmercier]

@tazman, @sjenkins, I'm currently looking into the issue with Yolink.

Does the YoLinkSetup node work as expected, or you don't see status for that one as well?

I don't have Yolink devices, but I can see the YoLinkSetup node which seems to work as expected.

[sjenkins]

13 minutes ago, bmercier said:

@tazman, @sjenkins, I'm currently looking into the issue with Yolink.

Does the YoLinkSetup node work as expected, or you don't see status for that one as well?

I don't have Yolink devices, but I can see the YoLinkSetup node which seems to work as expected.

Yes the YolinkSetup node works as expected with status as "OnLine" and the details filled in with other details.

All other Yolink nodes show a status of "1" and blank details screen.

see attached images.

 

[tazman]

3 hours ago, bmercier said:

@tazman, @sjenkins, I'm currently looking into the issue with Yolink.

Does the YoLinkSetup node work as expected, or you don't see status for that one as well?

I don't have Yolink devices, but I can see the YoLinkSetup node which seems to work as expected.

I see the same as @sjenkins.

[bmercier]

16 hours ago, sjenkins said:

Yes the YolinkSetup node works as expected with status as "OnLine" and the details filled in with other details.

All other Yolink nodes show a status of "1" and blank details screen.

see attached images.

 

@sjenkins Could you PM me the result of:

/rest/nodes/n006_8b4c010004df7a

/rest/nodes/n006_8b4c010004df7a/profiles?include=nodedefs,editors

[MWoods329]

When I rebooted my eISY, I noticed that eisy-ui did not start on its own.

And since I didn't plan on doing any more testing for a little bit, I didn't manually restart it.

But the bigger issue is that during that week or so when eisy-ui wasn't running I couldn't access my eISY through other interfaces and the eISY couldn't reach the portal.

I thought I was troubleshooting a networking issue or something (Ticket #27059):
- couldn't connect via IoX launcher or I could but it would disconnect and throw errors
-UD Mobile could only connect locally because it said the eISY was not connected to the portal
-could still connect with the eISY through the API and Home Assistant

Once I ran sudo service eisyui restart, all of those issues resolved.

Is the eisy-ui service (or lack of) supposed to be able to cut off all other UI access like that?

[bmercier]

3 minutes ago, MWoods329 said:

Is the eisy-ui service (or lack of) supposed to be able to cut off all other UI access like that?

Yes.

See the explanation here https://forum.universal-devices.com/topic/45210-eisy-ui-040-alpha-release/ under "Portal connection"

[MWoods329]

4 minutes ago, bmercier said:

Yes.

See the explanation here https://forum.universal-devices.com/topic/45210-eisy-ui-040-alpha-release/ under "Portal connection"

Ah, thank you.  I didn't understand that it would be a dependency once installed.  Got it now.

[MWoods329]

One day, I will have an intelligent question to post here.
Maybe that day is today?

Anyway... I'm curious why I can't take a dimmer on a Hue light down to zero?
That means I'd need to have two tiles to handle the dimming on these.
Or is there a better way to make the slider both dim and turn it off? 

I know that's a limitation in the admin console, I guess I just would have expected a more user-friendly UI would handle those types of interactions.