bmercier

That's a bug, and I'm pretty sure I know the cause. First of all, to display programs, the UI needs to load the resources a program may be referring to, such as variables. This calls a rest API that returns the variables. If an IoX never had variables, the API fails with a 404. This is probably what is happening here. So here's a work-around: Go to the admin console, programs, and make sure you have at lease 1 state variable and 1 integer variable. That should clear up the error. You probably can delete them as well, this is likely to still work afterward if you don't want to keep "dummy" variables.

No, that's not possible. And if anyone wrote that on the forum, that would have been incorrect. eisy-ui only works on port 80 or 443, and it only works with your portal credentials. But this does not mean this is "entrenched in the cloud". Except for the first login, eisy-ui can fully function without internet connectivity (Except of course for some plugins or for some features like portal approval). Without connectivity, you can login and use your eisy. Ref: https://wiki.universal-devices.com/Eisy:User_Guide#Using_eisy_without_connectivity

You are correct that it sends your portal creds in clear, but that stays on your network. When eisy-ui's server verify the creds against portal, it always use tls. It's always better to use https even on your network in case something has been compromised on your network.

Please open a ticket referencing this post, and attach the result of those urls in the ticket: http://eisy.local/rest/profiles http://eisy.local/rest/nodes

There's a few things not right. It's missing commands, and it looks like the names for status are not working. First of all, please check the version of eisy-ui (It's displayed at the bottom of the menu). If < 0.7.2, please upgrade packages. If you have the same result after the upgrade, ^please open a ticket and refer to this post (or attach the screenshots to the ticket). Also please include the result of these URLs: http://eisy.local/rest/profiles https://eisy.local/rest/nodes

Click the top-right gear icon to go to edit mode. You will see buttons to delete the page and add tiles. In addition, you can click the top-right question mark to see the documentaiton. Scroll down to the section "How to customize the Home page"

I think the original annoucement was for Nov 1st, but then it was moved to Nov 4th.

In the menu, click Settings | System.

Hello, eisy-ui 0.7.2 is out. Release notes for 0.7.2 General usability enhancements Link to documentation Link to Admin Console Upgrade packages page Home page defaults to Nodes when there are no favorites Disabled remote logging by default Hide node properties that are marked hide=true (Like Admin Console) Here's what the upgrade packages page look like:

What is being removed on November 1st is support for the Amazon Smart Home API V2. This used to be the case for our older "ISY Optimized for Smart Home V2" skill. The "ISY Optimized for Smart Home V3" skill uses the Amazon Smart Home API V3. This is still supported and the only current way to implement a Smart Home skill for Alexa. When using Alexa+, this still works with smart home skills. The new "AI-native SDK for Alexa+" allows to develop custom skills. I guess it could be used to control devices, just like the older Alexa custom skill API could do. But regardless, smart home skills using the V3 API is still the current way to develop smart home skills. Now, I have had many reports of users receiving the warning you mention. I do not know for sure why. I believe this may happen if you used to have the older ISY Optimized for Smart Home V2. Either it's still there (along with the V3 skill), or there's some remnants of the older devices existing in the account. In preparation, make sure the skill you are using is "ISY Optimized for Smart Home V3". On November 1st, if you see some devices are no longer responding, please do this: Login to the Alexa app, test the device there. If you see it is not working, delete it from the Alexa app. Ask "Alexa, discover my devices". This should recreate the device in your Alexa app based on the configuration you have on my.isy.io. If it doesn't, login to my.isy.io, look under Select tool | Connectivity | Alexa. Make sure that your device is there. If it is not, create it. It may be that device was created a long time ago using the V2 skill. With the V3 skill, the device discovery will create a V3 device in your Alexa account.

Make sure the variable comes back to an Off value after being "On". The other thing to be aware when testing is that the variable's value can't change too quick. If for example it becomes on, then off then on again within just a few seconds, it will be seen as a single "On". Think of a motion sensor. When it detects movement, it stays in a motion state detected state for a few seconds then comes back to no motion detected after a set timeout. This works the same way. You can change your variable to On then Off quickly, but you can't turn it on again too quickly as it will be considered the same motion (or the same contact).

I have no clue where the messages comes from, but I doubt it's related to eisy-ui. I'd recommend to open a ticket, and include a sample of the log.

You can upgrade all in one shot. Just make sure to follow the directions for the update to IoX 6.0.0. For the purpose of clarification, the latest IoX version is currently 6.0.0, and the latest eisy-ui version is 0.7.0. These are 2 different things. eisy-ui, regardless of the version, requires IoX 6.x

0.7.1 is also out, which fixes a bug with status display.

@apostolakisl @Lore @rshilliam @Bumbershoot @garybixler I just released 0.7.1 which fixes the status.