bmercier

No status at all is not normal. Please open a ticket referencing this post, and add your uuid. We have not figured out the cause of the missing status, but we added logging which should help identify the cause. If possible, if you can still reproduce the problem, please open a ticket with both a screenshot of AC and eisy-ui, showing the missing status in eisy-ui, and Chris should be able to take it from there.

> 4) Any single ISY can belong to no more than 3 accounts/subaccount This is a limitation of the Admin Console, not portal. If using eisy-ui to approve/reject accounts, there is no limit. The limit on Admin Console is higher than 3, probably 5 if memory serves well. > 5) You can not delete a user (or account holder either) and add them as a user to a different (sub)account. You need to make a ticket with UD and ask them to delete the user email from the system if you want to move them to a different (sub)account. After they are deleted, you can invite them to be a user on a different (sub)account. Actually you can delete a user, as long as the user is an account admin. If there is only one user left in an account, and he is not an account admin, then you are stuck. If the user is in a subaccount of yours, then you can delete the user and the subaccout.

Hello everyone, We will have a short portal maintenace tomorrow Oct 2nd. Between 4am and 5am PST, your unit will briefly disconnect and reconnect to portal. The purpose of this maintenance is to add a fix to enhance the reliability of the portal connections specifically for eisy-ui. Benoit

Think of it as a dashboard. You see everything you want, organized like you want, no more no less. You don't click on something to get more details - you get it right away. That requires screen real estate, but you can have multiple favorites page.

@woodchip from what I see here, there is a problem with nodedefs. You should open a ticket and include the screenshot. Also please include the output of: /rest/nodes /rest/profiles?include=nodedefs,editors,linkdefs

@chris.com 1. There doesn't seem to be support for Insteon Scenes in the new web ui. That's fine if that's the case; I assume it's coming. Or, is it there and I'm just not seeing it? It's not there yet, this will be eventually added. 2. How do I log in to the eisy via ssh? The old method root/root no longer works and I have been unsuccessful guessing what will work. This has not changed. It should be admin/admin if you did not change the defaults. 3. Check out the attached video clip. Is this how the dimmer slider is supposed to work? When you click on a position the light does seem to go to that percentage, but the slider springs back up. And we have two values, an 8-bit value and a percentage. It gets weirder when you click the up and down arrows next to the 8-bit numerical value. This is not normal. When you click on it, it sends the command to eisy. But it will always move back if the command does not work - it reflects the current state. What is this device exactly? Is it using insteon, ZWave? Or is it from a plugin? The Admin Console is not going away anytime soon. At least, not before eisy-ui is on-par.

Tiles in eisy-ui are not related to UD Mobile. They are 2 different UIs with different capabilities. When you click "Add tile", select one or several node, change the "import as", if available on the node, and Go. If you want to customize tile (Edit an existing tile, Add a custom tile), think of a tile like this: A tile is usually 1 node, with some widgets. But it can also be multiple nodes, and some widgets from one of the tile nodes. This allows things like a sprinkler tile that combines all your sprinkler nodes.

@baabm @woodchip eisy-ui will eventially replace the Admin Console. But for now it's still beta software and missing many things such as the ability to create/edit programs. So, use eisy-ui whenever you want, but continue using the admin console for things that are not yet implemented in eisy-ui.

eisy-ui is still beta software. We are planning to implement themes, which will allow to switch to black on white. But that may take a few months to get there.

Can you PM me your uuid? I believe it was just a matter of timing.

The problem with the Auto-Update has been resolved.

The login with portal credentials is expected. The auto-update, I'm not sure.

Maintenance is now completed.

Hello everyone, We will have a short portal maintenace next Monday Sept 29th. Between 4am and 5am PST, your unit will briefly disconnect and reconnect to portal. The purpose of this maintenance is to add a fix to enhance the reliability of the portal connections. Benoit

Hello, There was a portal outage last night from 4:27 to 6:32 ET (1:27 to 3:32 PT). The incident was triggered by a service outage at Amazon: Amazon echo services. The root cause of the portal outage was a bug in the portal code which mishandled the specific error returned by Amazon when reporting device statuses, creating a continuous loop which made our servers non-responsive. The bug has been fixed, and I can tell the Amazon echo services are also working fine now.

Actually, I'm not fully sure. What I know is that both the property and the parameter on the command has a precision of 1, but the precision on the updated value from the subscription has a precision of 0. So I'm thinking that if the value sent is an integer, then precision would be 0 instead of 1. I don't think there's any work-around for you, except maybe try with a float with something like .01 (which should be rounded to .0), giving the same result as an integer.

@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.