bmercier

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.

eisy-ui 0.5.1 changes Login with no connectivity New Portal Authorization page under Settings icon search with synonyms Nodes page: Added folders Nodes page: Display names in the tree instead of the address Dimmers can now send a DOF when turned to 0 Fix program save in Admin Console To install eisy-ui 0.5.1 Download this package to your eisy: eisyui-0.5.1.pkg Install: sudo pkg add -f eisyui-0.5.1.pkg Start the service: sudo service eisyui restart

@sjenkins, @TJF1960, Thanks for reporting the problem with saving programs. I reproduced it in dev and will release it in the next hour or so. The program save issue is resolved in dev. The other issues you are having are not related to eisy-ui. I would encourage you to open a ticket.

This is still just a beta. Will enhance this. For now, just edit the tile and add a switch widget.

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

@sjenkins Could you PM me the result of: /rest/nodes/n006_8b4c010004df7a /rest/nodes/n006_8b4c010004df7a/profiles?include=nodedefs,editors

@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.

@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.

Ok thanks, will investigate further.

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.

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")

That's what I meant by offline. If it's not connected to portal, it's "offline", and therefore Alexa integration will not work.

Try again. If your unit was offline, that's what you would see.

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".

Can you see the status for Yolink in AC?

> 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?

I just unpinned a few posts. Thanks for the suggestion.

Portal was down from 2am-8:30am eastern / 11pm-5:30am pacific time. Root cause A scheduled job that cleans up database records caused the database to go down. Portal servers were up but could not contact the database. Impact Access to portal services was not working during the outage, including Alexa and Google Home. Attempt to login was returning an HTTP 429 error. Alexa & Google Home may have to be relinked if the access tokens were due for a refresh during that period.

There was a portal outage. Everything should be up now.

Everything should be up now.