bmercier

Thank you very much for the feedback. There's no specific timeout set. Will need to investigate further as I have never myself let it up overnight. I suspect the websocket connection dies somehow. Will look into it. Is there a way to get a screenshot? Never seen that happen to me. It might be good to look at the browser console to see what's happening.

That could be explained this way: If IoX is having intermittent troubles, that would kill the subscription, and thus, force you to restart AC. But getting the subscription from eisy-ui, this means eisy-ui has been up all the time without errors. It gets the events from MQTT. Even if IoX restarted, or even if MQTT restarted, eisy-ui reconnects in the background and continues to feed the active subscriptions. No, what @apostolakisl describes is a design choice to hace all folders expanded by default. The only change coming regarding this will be buttons to collapse all/expand all.

This means that IoX is somehow having trouble. That is not related to eisy-ui. The "loading nodes" error you see in eisy-ui means that it is requesting /rest/nodes from IoX, and it is not responding. Are you still having trouble? If so, you need to open a ticket. If you were able to load the admin console, that tells me that IoX is actually working (even if you connected through port 80 or 443).

Just to be more specific; When logging in: If uuid is not in the account, eisy-ui will offer you to add it to the accunt. Also, if uuid is in the account but not "approved" in the admin console, it will auto-approve. There was however a bug related to that logic, and it is now fixed. It is intended to be both a user interface (The home page), and an admin interface (the other stuff). Next big piece under development is Programs. One of the goals is to get rid of the admin console.

Some will prefer "All Expanded" to start with. Eventually I will add Expand All/Collapse All buttons at the top. In addition, I would say that instead of drilling down your folders, the search function is probably best to quickly get to the node you want.

This would be a good start eisy-ui documentation: https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui

My apologies, I'm pretty sure the update is not going through due to a missing dependency. We are releasing a major upgrade next week which includes an upgrade to the OS. That will fix the installation of eisy-ui using "Upgrade Packages". In the mean time, if you are familiar with ssh, you can upgrade this way: sudo pkg install eisyui sudo service isy restart After the above, you may have to manually start eisy-ui if the install did not start it automatically: sudo service eisyui start

> I assume that I don’t try to backup these node servers and install on the eisy. Correct. That can't be restored on PG3. > Once ISY is migrated, I then install new PG3 node servers (Plug-Ins?) on the eisy? Correct > When installing new Node Server/Plug-In, do I use the slot I used for PG2 previously shown in my ISY? If same plugin, yes. > Will I have to re-point my network resources in my eisy programs for the newly installed Notification node server on PG3? I'm personnally not that familiar with the Notifications plugin, but my understanding is that you are using an older way of doing notifications. I would look into doing it using the current notifications plugin.

No, not possible. It has to be a portal username, and that has to be an email address.

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.

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.

eisy-ui is now officially released. This is still beta software, but it is now included when you "Upgrade packages". eisy-ui is a service that runs on your eisy that provides our next-gen web interface. To launch eisy-ui, point your browser to http://eisy.local and login using your portal username and password. Please note that once eisy-ui is installed, the admin console may need your portal username and password. In IoX finder, a URL with no port will require you to login using your portal username/password. If you see a url with port 8080/8443, this will require your IoX username/password. More informations here: https://wiki.universal-devices.com/Eisy:User_Guide#Admin_Console eisy-ui documentation: https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui *** UPDATE *** We are releasing a major upgrade next week which includes an upgrade to the OS. Whenever it becomes available, eisy-ui will be installed automatically by the "Upgrade Packages". In the mean time, if you are familiar with ssh, you can upgrade this way: sudo pkg install eisyui sudo service isy restart After the above, you may have to manually start eisy-ui if the install did not start it automatically: sudo service eisyui start

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.

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

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.

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

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.

eisy-ui 0.5.8 changes Fixed issues with path resolution for UI files coming from a very subtle typescript compiler configuration issue. To install eisy-ui 0.5.8 Stop the service: sudo service eisyui stop Check if you have any eisyui process running, and if so, kill it. You may have it if you installed 0.5.5. Run this: ps aux | grep eisyui Check if you have any process running as eisyui. If so: Take note of the process id (pid) Run this: sudo kill <pid> Download this package to your eisy: eisyui-0.5.8.pkg Install: sudo pkg add -f eisyui-0.5.8.pkg Start the service: sudo service eisyui restart

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

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.

FYI the login box of AC will be more obvious with regards to which creds to use.

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)

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.

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

Make sure to login using your portal creds. Ref: