eisy-ui Alpha release - Feedback

[sjenkins]

4 hours ago, bmercier said:

Could you try by using the AC on port 80 or 443 (eisy-ui's server ports)?

@bmercier , sorry I wasn't clear.

When I log in the AC on port 80/443 with portal credentials the developer local nodes do not update & stay mostly blank ; same on the browser eisy-ui.

Log in the AC with port 8443 with local credentials and they update.

This is just for nodes on locally hosted plugins I am developing, no issue if I run it beta.

 

[bmercier]

4 minutes ago, sjenkins said:

@bmercier , sorry I wasn't clear.

When I log in the AC on port 80/443 with portal credentials the developer local nodes do not update & stay mostly blank ; same on the browser eisy-ui.

Log in the AC with port 8443 with local credentials and they update.

This is just for nodes on locally hosted plugins I am developing, no issue if I run it beta.

 

Ok that's very strange. I don't think it relates to the store being used. IoX does not know that.

[sjenkins]

2 minutes ago, bmercier said:

Ok that's very strange. I don't think it relates to the store being used. IoX does not know that.

Its my HunterDouglas plugin.  The shade updates are not showing up in the local version of my plugin.

It sits in my home directory under a folder with admin/admin privileges, while I see the cert/key files have admin/polyglot ownership.  I am seeing a couple of the nodes which have had 'action' go true in your status column (which is nothing to do with the details of the nodes status, that is all blank).  AC looks the same unless I log in local.  Yes it is strange.

[photogeek54]

I'm just bringing up eisy-ui for the first time and can't get it to show up in Iox finder or start it. I've read this entire topic's posts and believe the update packages and reboot I did yesterday should install and enable it right? I've cleared java and browser caches. running sudo service eisyui restart gives

eisyui does not exist in /etc/rc.d or the local startup
directories (/usr/local/etc/rc.d), or is not executable
 

adding https://10.10.1.171:443/desc to iox finder says "not found"

Should I try installing the eisy-ui package manually via ssh? If so what is the current package name and how can I see the version I am currently running?

Do I need to manually install the latest iox? If so what is the latest package name and how do I find the exact version I am currently running? AC's help only shows 5.9.1 and not the latest version number.

 

Thanks

[bmercier]

2 minutes ago, photogeek54 said:

I'm just bringing up eisy-ui for the first time and can't get it to show up in Iox finder or start it. I've read this entire topic's posts and believe the update packages and reboot I did yesterday should install and enable it right? I've cleared java and browser caches. running sudo service eisyui restart gives

eisyui does not exist in /etc/rc.d or the local startup
directories (/usr/local/etc/rc.d), or is not executable
 

adding https://10.10.1.171:443/desc to iox finder says "not found"

Should I try installing the eisy-ui package manually via ssh? If so what is the current package name and how can I see the version I am currently running?

Do I need to manually install the latest iox? If so what is the latest package name and how do I find the exact version I am currently running? AC's help only shows 5.9.1 and not the latest version number.

 

Thanks

It's definitely not installed.

Please install version 0.5.6 using ssh.

sudo pkg info eisyui will give you the current version installed, but for sure, it's not installed on your unit.

[bmercier]

2 hours ago, sjenkins said:

Its my HunterDouglas plugin.  The shade updates are not showing up in the local version of my plugin.

It sits in my home directory under a folder with admin/admin privileges, while I see the cert/key files have admin/polyglot ownership.  I am seeing a couple of the nodes which have had 'action' go true in your status column (which is nothing to do with the details of the nodes status, that is all blank).  AC looks the same unless I log in local.  Yes it is strange.

Can you check the start time of the Mosquitto service and the isy service? I bet Mosquitto restarted after isy.

isy:
ps -o lstart -p $(pgrep isy)
 

Mosquitto:
ps -o lstart -p $(pgrep -u isy mosquitto)
 

[photogeek54]

58 minutes ago, bmercier said:

It's definitely not installed.

Please install version 0.5.6 using ssh.

sudo pkg info eisyui will give you the current version installed, but for sure, it's not installed on your unit.

Great , I can see the process running now. I cleared edge browser cache and browsed to :

https://10.10.1.171/desc

and http://10.10.1.171/desc but I get an xml error

 

[bmercier]

There is a problem with 0.5.5 and 0.5.6. Please don't install the for now. Will have a new release tomorrow.

It's working only due to cache.

 

[bmercier]

10 minutes ago, photogeek54 said:

Great , I can see the process running now. I cleared edge browser cache and browsed to :

https://10.10.1.171/desc

and http://10.10.1.171/desc but I get an xml error

 

I don't seee any xml error. If you are referring to the "Not Secure", this is due to the self signed cert.

[sjenkins]

3 hours ago, bmercier said:

Can you check the start time of the Mosquitto service and the isy service? I bet Mosquitto restarted after isy.

isy:
ps -o lstart -p $(pgrep isy)
 

Mosquitto:
ps -o lstart -p $(pgrep -u isy mosquitto)
 

 

@bmercier you are correct (of course)!  But you gotta share how you came to that conclusion.

 

[bmercier]

16 hours ago, sjenkins said:

@bmercier you are correct (of course)!  But you gotta share how you came to that conclusion.

 

Actually, just a difference of 1 second is not what I expected. My theory falls apart.

Still searching for the cause.

I just released 0.5.8. Please do upgrade to 0.5.8, especially if you installed 0.5.5 or 0.5.6.

[photogeek54]

On 7/21/2025 at 2:09 PM, photogeek54 said:

Great , I can see the process running now. I cleared edge browser cache and browsed to :

https://10.10.1.171/desc

and http://10.10.1.171/desc but I get an xml error

 

I installed 0.5.8 but still get the same XML file error, see image.

Update: if I use http://10.10.1.171:8080 without the /desc I can get in to the AC, but

I have to login with my previous AC userid and password not those of the portal.

 

Edited Wednesday at 01:48 AM by photogeek54

[sjenkins]

Installed 0.5.8

All looks good.  Couldn't tell from the version notes what I need to specifically test.

My issue with the local plugin is very odd.  A few fields are updating on some of the nodes, but only a few and not real-time.  I get this is much lower priority, let me know if it gets to the top ten list.

[bmercier]

On 7/18/2025 at 8:31 PM, paulbates said:

Is there a rough estimate for when eisy-us alpha/beta will be available as an update, not an SSH download? That's when I'll start joining the testing

0.5.8 is now released. It can be installed using Upgrade packages.

[bmercier]

13 hours ago, photogeek54 said:

I installed 0.5.8 but still get the same XML file error, see image.

Update: if I use http://10.10.1.171:8080 without the /desc I can get in to the AC, but

I have to login with my previous AC userid and password not those of the portal.

 

The screen shot output is as expected.

To login in the admin console, regardless of the port use, it needs the /desc at the end. And yes, on port 8080 you need to use the IoX user and password.

[bmercier]

13 hours ago, sjenkins said:

Installed 0.5.8

All looks good.  Couldn't tell from the version notes what I need to specifically test.

My issue with the local plugin is very odd.  A few fields are updating on some of the nodes, but only a few and not real-time.  I get this is much lower priority, let me know if it gets to the top ten list.

With the prior version, when pointing your browser to http://eisy.local, you could get a "Not Found" error instead of the UI. It worked only if your browser had the UI in cache. If you would have tried in another browser, it would not have loaded. 0.5.8 fixed that.

The problem with the status has to do with how the plugin sends the status and/or if the node was queried. So if you had a status change since the last reboot, eisy-ui and AC should be getting them. If a status has not changed since the last startup, this is when you may not be getting them. In the plugin, when setDriver is called, you can force sending the update. Your plugin probably doesn't.

Let me share some more info on how things works.

When a client (AC, UDM...) requests a subscription, it also sends a request to get the latest states. IoX then sends the latest nodes properties, which the client uses to display them.

In eisy-ui, it's a bit different. When a client connects to eisy-ui to get a subscription, the protocol is essentially the same as when connecting to IoX directly. What's different is how eisy-ui gets events from IoX. When a subscription is requested (either internally or from a client), it starts a mqtt subscription to an events channel. events are sent from IoX on MQTT topics that eisy-ui reads. Those events have the "retain" flag set. This means that the MQTT server keeps the latest copy of those events, and whenever a client connects, it sends them along. 

So technically, the results should be the same, but obviously, it's not in your case. Your tests tells me that somehow, IoX is aware of past events, but those same events are not stored with the retain flag in the MQTT server.

In your case, the problem is only with your plugin in dev. But that does not really matter, IoX does not know about whether a plugin is in dev or beta or prod.

So bottom line, those properties that have a status must be because the status changed since the last startup. What I don't understand yet is how can IoX know about a propety, and not MQTT...

FYI, we now have some doc on eisy-ui:
https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui

[photogeek54]

I must be missing something very basic.

I was thinking based on some previous forum posts that maybe browsing in Edge to 10.10.1.171/desc would get me to the admin console, looks like that's not the case so I'm trying to use finder.

The iox finder now comes up with only 2 options:
clicking http://10.10.1.171:8080 in finder lets me choose Admin Console (LAN) or Admin Console (Cloud).
Admin console (LAN) locks up and I have to close the finder.
Admin Console (Cloud) works with iox username and password so that's what I use but My solaredge plugin in the non production store is now having issues.

clicking http://10.10.1.171/desc in finder does nothing

How do I start admin console with the portal user name and password

[bmercier]

2 minutes ago, photogeek54 said:

I must be missing something very basic.

I was thinking based on some previous forum posts that maybe browsing in Edge to 10.10.1.171/desc would get me to the admin console, looks like that's not the case so I'm trying to use finder.

The iox finder now comes up with only 2 options:
clicking http://10.10.1.171:8080 in finder lets me choose Admin Console (LAN) or Admin Console (Cloud).
Admin console (LAN) locks up and I have to close the finder.
Admin Console (Cloud) works with iox username and password so that's what I use but My solaredge plugin in the non production store is now having issues.

clicking http://10.10.1.171/desc in finder does nothing

How do I start admin console with the portal user name and password

The only way to open up the admin console is by using the IoX finder.

> clicking http://10.10.1.171/desc in finder does nothing

> clicking http://10.10.1.171:8080 in finder lets me choose Admin Console (LAN) or Admin Console (Cloud).

That does not sound normal. You need to have /desc at the end.

> Admin console (LAN) locks up and I have to close the finder.

That's not normal either. This loads the admin console from your eisy (from IoX more specifically - port 8080 is IoX's http port)

> Admin Console (Cloud) works with iox username and password so that's what I use

That is normal. IoX (port 8080) requires your iox username and password.

> clicking http://10.10.1.171/desc in finder does nothing

That's not normal either. Adding this url to IoX finder should show you the IoX version. When you try it in a browser, it gives you something right? That's the screenshot you sent. So that tells me that eisy-ui is indeed installed. Not sure why AC would not work. 

If you are using a link on your desktop, could you try instead to load it from https://www.universal-devices.com/? Click on My ISY to the right.

 

[photogeek54]

loading start.jnlp from https://www.universal-devices.com/ gives me the same results as Admin Console (Cloud) in finder.

I think I need to get back to a working system like I had a few days ago where my plugin still works. How can I do that. Should I enter a ticket for this or keep replying in the forum?

 

[bmercier]

1 minute ago, photogeek54 said:

loading start.jnlp from https://www.universal-devices.com/ gives me the same results as Admin Console (Cloud) in finder.

I think I need to get back to a working system like I had a few days ago where my plugin still works. How can I do that. Should I enter a ticket for this or keep replying in the forum?

 

Yes, ticket please as I have no clue what problem you are getting with your plugin, and that is probably not related to eisy-ui, and thus, not relevant to this thread.

[bmercier]

FYI I opened a new forum dedicated to eisy-ui: 
https://forum.universal-devices.com/forum/455-eisy-ui/ 

That would be the place to ask any eisy-ui related questions.

[sjenkins]

11 hours ago, bmercier said:

The problem with the status has to do with how the plugin sends the status and/or if the node was queried. So if you had a status change since the last reboot, eisy-ui and AC should be getting them. If a status has not changed since the last startup, this is when you may not be getting them. In the plugin, when setDriver is called, you can force sending the update. Your plugin probably doesn't.

@bmercier first, thank you for taking the time to explain the plumbing a bit.  Not only helpful but very interesting.

Second, you are right I was not forcing when sending my updates, I had left the defaults.  Changed that and all of a sudden I am updating just fine in the local dev mode to the eisy-ui.  Not sure if there is any penalty for this beyond a bit more traffic and time; but I cannot observe any side-effects.

self.setDriver('GV6', self.shadedata["batteryStatus"],report=True, force=True)

(the report=True is already default)

I will go with this method for now.  Thanks again.

I will move to the new forum, but thought I should close this out here.

 

Edited yesterday at 02:50 AM by sjenkins

[photogeek54]

0.5.9 has solved my eisyui/finder issues. A restart of my solaredge plugin also solved its problems