bmercier

Here's a few tips regarding Alexa. When troubleshooting, always use the Alexa app, instead of voice commands. This way, you are sure about what device is being controlled. When controlling via voice, Alexa may be confused with a device or room using a similar name. If you find you have duplicates, you need to delete them from the Alexa app. You may be tempted to start fresh and delete your mappings on portal, but there is no need to do that. The only case where it may be useful is if you are mapping an ISY node that no longer exists on your ISY (or eisy/polisy). When using V3, when adding/editing/removing a mapping, it should be updated directly in the Alexa app. There is no need for a device discovery. That's if the skill is linked. If you change your mapping while the skill is not linked, then when linking it will get discovered. I don't think the problem you are having is the alternate spoken. Alternate spokens are treated exactly the same way as the primary name you gave. Using alternate spoken just creates additional Alexa devices mapped to the same ISY node. One thing to watch for are Alexa scenes, especially if you had some when using V2. Alexa scenes are kind of hidden. So if you have an Alexa devices with the same or similar name as an Alexa scene, then Alexa will see multiple device with the same name. That's why it's important to first test controlling devices directly with the Alexa app - you know which one you are controlling.

There is a major update coming, which includes an update to the OS. It was to be announced at the same time, but it got delayed.

FYI, you can also navigate with the cursor keys, and use the spacebar to select the the node and see the details. This is a bit quicker to navigate as it does not have to load the details page until you need it.

This skill is definitely outdated. Please use "ISY Optimized for Smart Home V3".

Please open a ticket, and I will do a remote session with you. Something's not right. The Network Error suggests that the UI is not able to contact the eisyui service, but you say it's started, so I don't get it.

That should return an xml like in the screenshot. Finder uses that info.

This looks good now. So entering this url in the IoX finder should work.

What's the result of http://eisy.local/desc If you see a web page, and not XML data, please use Chrome, and us Shift + Click reload button. This will reload the page without using the cache.

Regarding the disconnection, you should upgrade eisy-ui. sudo pkg install eisyui Regarding the UI... what is the error?

Are you using eisy-ui? If so, and if the eisyui service is stopped, that may explain it. To see if you have it installed and started: sudo service eisyui status To start it if you have it and it is stopped: sudo service eisyui start

The web ui responds on the root. /desc should return you the the same as :8443/desc Can you please update eisy-ui, based on the logs, I can tell you are using a previous version of eisy-ui. sudo pkg install eisyui You may have to restart it: sudo service eisyui restart

No it has not been released yet.

That is very strange. Since when are you having this problem? There has been no new versions of eisy-ui published for a while now.

Approval won't work if ISY is not online, that will give you "Bad Request". You may want to try to reboot your ISY. It should normally connect to portal. If it does not, it may be caused by a problem with dns resolution, parental control on your router, or local network routing issues.

The line showing https://eisy.local/desc should show the type and version. The fact that it does not tells me there is a problem. Can you try the url in a browser? Does it respond at all? Could you also try https://192.168.0.106/desc in admin console and browser? It it works, but https://eisy.local/desc does not, it could be explained by a dns resolution problem.