bmercier

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.

Everything should be back up now. Will write an outage summary.

Portal is currently down. Working on getting it back up.

eisy-ui 0.4.3 changes Fix for status not updating in some cases At login, allow email verification using pin if email needs to be verified At login, allow adding uuid to account if not already in account At login, auto-approve uuid in account (if not approved) Fix Portal approval from Admin Console / UDM Add tooltip on tile headers Fix for some missing profile editors Fix admin console XMLParseError Fix input of parameters values To install eisy-ui 0.4.3 Download this package to your eisy: eisyui-0.4.3.pkg Install: sudo pkg install -f eisyui-0.4.3.pkg Start the service: sudo service eisyui restart

This is the IoX Finder, not the Java console. But regardless, it's no longer required. The XML Parse error has been fixed in dev and will be included in the next release.

This is not related to eisy-ui. 8080 is the HTTP port for IoX. Are you sure you did not make a typo when adding 8080? http://eisy.local:8080/desc (make sure you did not enter https)

Please PM me the result of /rest/profiles?family=14&include=nodedefs,editors In the admin console?

With eisy-ui installed and running, the IoX finder is expected to find it, that is normal. This means that the only but to fix here is the parse error. I'm on it.

I'm now able to reproduce the parse error. Will work on a fix. What's not working with 8080? There has been no changes, 8080 is the http port for IoX. If it's a login problem, use yout IoX creds.