bmercier

@sjenkins thanks for reporting this. It will be fixed in the next release. The problem seems to happen when the precision on the editor is different than the precision on the value. In this case, although the precision on the ST prop is also 1, I think the plugin is setting values with a precision of 0.

@sjenkins, I'm not familiar with the VirtualPlugin. Please let me know how you configured the Virtual plugin so I can reproduce it.

Yes. sudo pkg remove eisyui and also sudo service isy restart But why? That will create problems. Upgrade packages will keep reinstalling it. Plus, starting with the next release, eisy-ui will be expected to be installed. Future versions of UD mobile will start to rely on eisy-ui, and if it is not installed, then UD Mobile won't work. Admin Console will also eventually disappear, in favor of eisy-ui.

Most likely, this is what is happening; 1. You have eisy-ui installed. When installed, eisy-ui service is responsible for the portal connectity. 2. You started AC, and connected using port 8443 or 8080 (Directly to IoX). In that case, IoX no longer has the portal connectivity, It can't give you a portal status, and you can't approve/revoke portal access from an account. The error is expected. When eisy-ui is installed, it's best to connect to port 443 or 80 (same url, just a different port). Then, the portal tab will work as expected. Note that when eisy-ui is installed, you can also use the Web UI to access the same functionnality.

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.

Yes. I understand it was working before. The difference is that you now have eisy-ui installed. Explanation: When eisy-ui is installed, it takes care of the connectivity to portal. IoX no longer does. eisy-ui also takes care of the "portal approval" as it is tied to the portal connectivity. The approval process involves an exchange of tokens with portal through the proxy connection which IoX can no longer do. So, when you are using AC and connect to IoX directly (8080 or 8443), the Portal tab won't work. If you use AC and connect to eisy-ui (no port specified), then the Portal tab will work just like before. Note that you can also manage the portal approval using eisy-ui's web interface. That is not normal. Can you try the URL in a browser? That should give you an xml doc. You may have to accept the self-signed certificate. You should also be able to navigate to https://eisy.local

Is the "other issue" the "Bad Request" on the Portal tab? That is normal if you are using AC over port 8443 or 8080.

This is not a display issue. This just means that IoX is not sending these events through MQTT because they have not changed. Will look into it with Chris.

I located your uuid based on your email address and checked the logs. I see that it's currently online, but there had been an issue (and maybe still there) where there were more than one instance of eisy-ui running. That stems from a bug in an alpha release. A reboot should solve it. Alternatively, you can do this: Stop the service: sudo service eisyui stop Check if you have any eisyui process running, and if so, kill it. You may have it if you installed 0.5.5. Run this: ps aux | grep eisyui Check if you have any process running as eisyui. If so: Take note of the process id (pid) Run this: sudo kill <pid> Restart the service: sudo service eisyui start

If you are referring to my.isy.io, it is up and working, it has redundant connectivity, redundant systems and is monitored. It seems that your unit is probably not connected to portal, and there may be several reasons. Please open a ticket and we we will help you get it to work.

Thank you very much for the feedback. There's no specific timeout set. Will need to investigate further as I have never myself let it up overnight. I suspect the websocket connection dies somehow. Will look into it. Is there a way to get a screenshot? Never seen that happen to me. It might be good to look at the browser console to see what's happening.