bmercier

1. I found and fixed a bug. Please try again. 2. Yes the configuration is moved from one ISY to the other. They disappear from the source ISY and yes this is by design. Using this approach allows to retain the unique ID and keep the devices as is in Alexa, without impacts to Alexa groups or routines. Benoit

FYI, migration instructions here: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY

If you need to migrate to a new ISY, here's a new feature that will make it much easier, especially if you use Amazon Echo, Google Home or IFTTT / Webhooks. This also allows you to migrate your ISY Portal Access license to the new ISY. The option can be found under Select Tools | Migrate to Instructions: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY

When you create spokens, an internal id is created to uniquely identify the spoken. Alexa refers to a device by this ID. Therefore, When you create spokens, although everything may look identical (same uuid, same node), it is using a different id. When migrating, the spoken keeps the same id. From Alexa's perspective, there are no changes at all. This is why a discovery is not necessary. Benoit

It is now available as of last night. Look under Select Tools | maintenance Benoit Sent from my iPhone using Tapatalk

Actually, no. With Alexa, it is not necessary to rediscover. The spokens are migrated, not copied over. They retain their unique id used by Alexa. So as long as the ISY nodes are also « migrated » to the new ISY and has the same address, it should work. Please note that it may be different for GH. It may need a rediscover, I need to test it. Benoit Sent from my iPhone using Tapatalk

@cwitter, there is now a new google home category called "Device with open/close syntax". Please see this post:

Spokens can now be assigned a new Google Home Category: "Device with open/close syntax". This allows to "open" and "close" a device. Those devices can also be "opened to x percent". Programs, scenes, state variables and regular devices are supported. However, programs and scenes obviously can't be set to a specific percentage. Benoit

Hello, I will look into that. Could you PM me the output of: [ISY]/rest/zwave/node/0/def/get?full=true Also, please include the ZWave address of the device. Thanks, Benoit

I don't see why it would double trigger. Alexa will trigger it only once. Benoit

There are no plans to do that. Completion of a program is under normal circumstances quick, and it's what confirms that the action worked. If the program takes too much time, I think it should be triggered by a state variable. Benoit

I suspect the duration of the program too. If this is not complete withing a few seconds, it will timeout and Alexa will give an error message. FYI, there are no retry mecanism. Benoit

This is most likely because you don't have any network resources created in the admin console.

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