bmercier

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.

@sjenkins, do you still have a problem with statuses not showing? Is it for all status? If so, please take a look a the eisy-ui log after a startup. Look for errors related to MQTT.

@TJF1960, @GTench, @sjenkins or anyone with the XML Parse error, when starting AC, please leave the Java console open. Can you see an error message appearing in the console at the same time as the popup in AC? UPDATE: I'm now able to reproduce it. Will be working on a fix.

There is no scenes support at this time. I do have a Hue bulb using zigbee, and I see the Move to temperature. However, the input box does not allow to change the value directly, only allows to go up and down. Will fix that. You should find the Move To Temperature on the same node as in AC.

Can you check what the admin console shows for this property?

Make sure to login with your portal credentials. Everything on port 443 requires portal creds, not IoX creds. To get back to the regular IoX, I'm pretty sure an upgrade packages would do it. But I don't think that would fix statuses though.

Is this before logging in or after? That's weird. Were you seing statuses in the previous release? Please check the eisy-ui log for errors soon after startup. Statuses are obtained on a mqtt connection, so I'm wondering if the connection succeeds or not.

No that’s not normal. Is the problem only with Insteon nodes? Can you have the same problem in admin console? If this works in admin console but not eisy-ui, there may be errors showing in the server log or browser console. But that would be a first to me, this should work well.