bmercier

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.

eisy-ui 0.5.4 changes Fixed Nodes page folder expansion To install eisy-ui 0.5.4 Download this package to your eisy: eisyui-0.5.4.pkg Install: sudo pkg add -f eisyui-0.5.4.pkg Start the service: sudo service eisyui restart

That's a regression bug. I made many changes that are not visible, and obviously this broke the folder compressed/uncompressed persistence. Will fix this in the next release.

Try refreshing the page. if it still shows as red, then it’s in the list. Use the search bar to find the address.

eisy-ui 0.5.3 changes Fix some of the rest APIs that were not working (such as saving Network Resources) Sidebar - Highlight the current page Nodes page - Added node icons Many UI enhancements To install eisy-ui 0.5.3 Download this package to your eisy: eisyui-0.5.3.pkg Install: sudo pkg add -f eisyui-0.5.3.pkg Start the service: sudo service eisyui restart

You can’t edit the address. You need to remove it from portal and create a new one. Then discover.

eisy-ui 0.5.2 changes Nodes page: Folder expansion state is not persisted Nodes page column menu (pin/hide/filters). Reorganized sidebar menu MQTT communication robustness General bug fixes To install eisy-ui 0.5.2 Download this package to your eisy: eisyui-0.5.2.pkg Install: sudo pkg add -f eisyui-0.5.2.pkg Start the service: sudo service eisyui restart

Please check what the log says when you save. Also, are you sure Set Brightness is the right command?

icon search: This was following this post by @bpwwer: Now you should be getting a lot more results when searching for a keyword. Nodes page: Added folders - (they keep closing ; need memory like AC) Will look into that Fix for Yolink (still blank detail screens) I removed it from the feature list of 0.5.1. It will be permanently fixed with the next IoX release. I removed it from the feature list of 0.5.1. It will be permanently fixed with the next IoX release. It should not have made it to that list.

@apostolakisl Fans are very tricky to support with Alexa. Some may have 3 and others 4 speeds. Plus, when setting the value, each speed have their own thresholds. (Example, 25+ is med, 50+ is med/high, 75+ is high... etc) Regardless, Fan support is implemented in portal, but it may or may not work with your fan. Add the device, and set the Alexa Category to "Fan". If it works for your fan, then it's great. Otherwise variables is the way to go. Insteon fans should work, and at least one ZWave fan that I know of - can't recall the model.

Just so you know, you don't need a variable per speeds. You can have a single variable, but several "spokens" created on UD Portal. You can map multiple spokens to the same variable. The trick is to use a different "Turn on value" for each. This will give you a variable which number represents the speed it is set to.