bmercier

An email address must be unique. So he must have had removed that email address from his account, so you could use it elsewhere. His account still exists, and still have that ISY in it. Benoit

How did he delete his account? Or did he remove his user profile? What he has/had to do is remove the ISY from his account. The account is most likely still there, and if he deleted his user profile, does he have another one to access the account? If this does not resolve the issue, please have a ticket opened with the uuid and some indication of the account to be removed. This could be the account name, or perhaps the ISY alias used in that account. Benoit

ISY has a limit of 5 accounts it can be tied to. Benoit

Subscriptions should be working fine now.

There is a known problem currently being investigated. This was reported about 30 minutes ago.

When you delete a spoken (an item under Connectvity | Amazon echo) in ISY Portal, you also have to delete the corresponding device in the Alexa app. If you look in the Alexa app, you probably have 2 devices named Gate controller, your old one, and your new one. Also, if I correctly understand what you did, your spokens are all under the sub-account Shop Echo, and the new spoken was created in the main account. To have it work, you must have also linked the skill with your main account. That is not recommended. All your spokens should be in the same account, and the skill linked to that account, which should be "Shop echo" in your case. Otherwise, you will end up with devices in the Alexa app showing as offline. Benoit

Could you have logged in using the wrong account? Benoit

Maintenance completed.

Hello everyone, We will have a maintenance this Sunday 05-02-2021 at 5:00 AM Pacific time which will last a few minutes. During this period, subscriptions may be affected for a few brief moments. Benoit

Access license is required for GH to work. You can see the status of your license under Select Tools | Information | ISY Portal Access License Benoit Sent from my iPhone using Tapatalk

Please open a ticket with your uuid, a specific UTC time when it failed, and a link to this thread, and I can investigate the logs to see what is happening. Benoit

Yesterday, we had an outage of about an hour on one of the proxy servers. This has affected communication to some ISYs. Our servers are hosted on AWS, and this is usually very reliable, but somehow the instance stopped responding and was restarted by AWS automatically an hour later. Benoit

Maintenance has been completed.

Hello everyone, We will have a maintenance this Sunday 03-14-2021 at 5:00 AM Pacific time which will last about 1 hour. During this period, your ISY will disconnect for a few brief moments. The purpose is to Install the most recent security patches on the ISY Portal infrastructure. Benoit

I'm not aware of any changes like that coming.

It's unfortunateky not possible to change the wording of anything, except for the device name, which would not be helpful. There's however a very twisted way I can think of if you really want that. Here's the general idea: 1 - Have a routine, triggered by voice, that will run a program (turn on a device exposing a program) 2 - That ISY program will check if the door is closed or open. If so, it will set a variable to a certain value, else, another value. The program will also run the else statement of itself (so it returns to a false condifion and can be reused again). 3 - The variable we just talked about needs to be exposed as a sensor. It will become closed or open, based on the value assigned. 4 - You will need 2 other routines, which will react to this sensors, one for open and one for closed. It will speak the response you want based on the condition. Benoit

Not elegant, but please try to reboot your ISY. That should work. Benoit

Looks like it's clearly an Amazon bug. Thanks for posting it.

When this happens, could you check in the Alexa app what Alexa is saying exactly? There may be a clue there.

That's an interesting bug. In the Alexa app, can you see the device state? If you see both the device name and the value correctly, I would think Amazon changed something that is causing this. If the gibberish came through ISY Portal, it would have to be in the name, or the value. Other than that, it's coming from Amazon. It would be interesting to see if anyone else is experiencing this. Benoit

There is a button that allows you to export the spoken in a CSV file. But there is no import function, they need to be entered manually. Benoit

There's unfortunately no work around I can think of.

The device name from the admin console is never refreshed, and it does not really matter. The link is made using the device address. The ISY device name shown in the Echo device list is the name at the time it was added and is purely informational. If the new name is significantly different, and you want it to be updated in the Echo device list, then it has to be deleted and recreated. If you go that route, please also delete the device from the Echo app and rediscover the device, even if you keep the same spoken, otherwise you will have a duplicate.

ISY Portal has no limits to the number of sub-accounts. But, ISY has a limit to the number of accounts it can be part of, and I believe it's 5. Benoit

You don't have to remove the nodeserver and such. 1. Make sure the node you want is in the Admin Console and working (you can see the status, and you can control it) 2. Go to ISY Portal, in the ISY Tab, Select Tools | Connectivity | Alexa Make sure the devices you want to control with Alexa are here. If you had them there before and removed them from the admin console and recreated them, they may have a different node address. If you are not sure, then remove them and re-add them. Them, ask Alexa to discover devices. Whenever you discover devices, and the Alexa skill is enabled, the Alexa nodes are picked up from there. You may also want to check "My Profile", at the top right of the screen. Check the "Amazon Echo and Google Home ISY". Either you leave it to "Use all ISYs in the account", or else make sure your preferred ISY has the correct uuid. Benoit