bmercier

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:

Thanks for your feedback. After investigation, I found out the problem and just released 0.5.6. Basically, the problem was that you don't have a home page created yet. 0.5.5 should have created one automatically on startup, but due to a build issue, it did not. Could you try by using the AC on port 80 or 443 (eisy-ui's server ports)?

eisy-ui 0.5.6 changes Fixed a build problem introduced in 0.5.5. Due to a very subtle typescript compiler configuration issue, eisy-ui 0.5.5 was actually running the 0.5.4 server with the 0.5.5 UI. To install eisy-ui 0.5.6 Download this package to your eisy: eisyui-0.5.6.pkg Install: sudo pkg add -f eisyui-0.5.6.pkg Start the service: sudo service eisyui restart ** Please do not install - New package will be available Tomorrow **

Yes that’s what I mean by published

It already is. However, the currently published one is 0.5.4. 0.5.5 will be next week.

eisy-ui 0.5.5 changes Favorites pages visual enhancements Tiles are more compact Node status displayed to the right with a visual indicator (green/red/blus background) Many other little changes Although there is a conversion that takes place at startup, the tiles height will likely need adjustments. Nodes context menu on the Nodes page (right-click on the node) Add to Home page Rename node Delete Node) Better handling of authentication errors for Admin Console Fixed "Internal server error" when authenticating with invalid creds Many bug fixes and code enhancements To install eisy-ui 0.5.5 Download this package to your eisy: eisyui-0.5.5.pkg Install: sudo pkg add -f eisyui-0.5.5.pkg Start the service: sudo service eisyui restart ** Please do not install - New package will be available Tomorrow **

I have seen issues with Alexa+ as well.

If you are suddenly having difficulty to login in admin console, please read this. We started to release eisy-ui. You can get a summary of the new features here: One of the goals of eisy-ui is to simplifiy things, and more specifically: Have a single user/password for everything, whether it's for the portal or local access Simplify access by using the standard ports 80 (http) and 443 (https) Once eisy-ui is installed, which will happen after an upgrade packages, you will be able to use the admin console using either: https://eisy.local:8443/desc or http://eisy.local:8080/desc and the local user/password (Just like before - no change here) https://eisy.local/desc or http://eisy.local/desc and the portal user/password (That is new) IoX Finder should detect your eisy on port 80/443. So if you don't pay attention and use your local user/password when connecting to port 80 or 443, that won't work. Eventually, you can expect ports 8080 and 8443 to disappear, but for now, they are still accessible for backward compatibility.

Ring advised me of another upcoming change. I had to make another release of the plugin, version 1.2.6. Please update when you have a chance. For now, 1.2.5 works. However the authentication should start to fail in the next few days if you don't update.

Ring made a change in their API. I updated the Ring plugin accordingly. Please update the plugin and re-authenticate, that should solve it.

The tesla plugin is currently free for a limited time, and we are trying to figure out the pricing model. Your input would be very useful. Using vehicule commands incurs a cost. From what I can see, some users do not issue much commands while others are issueing commands on schedules. Schedules like waking a car every 2 hours continuously incurs a high cost. To keep the plugin affordable, we think we need to implement rate limits on wake ups and vehicle commands. I'm currently thinking of these limits: 10 vehicle commands per day 2 wake ups per day (These are the most expensive API calls) FYI, when a command that requires the car to be waked up is sent, if the car is not awake, the plugin will automatically send a wake_up. Please let me know if these limits sounds good, or are too low.

Thanks for reporting this. Actually, the sort order is not random, it's sorted using the node address, which is not displayed in this column. This will be fixed in the next release.

I have been made aware of an issue with Ring that started recently (probably yesterday?). The symptoms are this: The plugin is online, but the individual nodes appear as Offline. The log shows lines like this: 2025-07-08 00:03:21.890 Thread-124 (pollHandler) udi_interface ERROR oauth:_oAuthTokensRefresh: Failed to refresh oAuth token: 401 Client Error: Unauthorized for url: https://oauth.ring.com/oauth/token Authorizing works, everything will then be normal for 4 hours, but when the access token is expired, attempts to refresh fails with the error above. For now I assume there has been a change at Ring that causes this. I have contacted Ring support for help. If for some reason your plugin works as expected, please let me know. I'm assuming it's down for everyone.