bmercier

Thanks for the suggestion. We now use the first controller, if available, otherwise the first node (controller or not). It's in production.

No

The logic is quite simple: If the device is non-zero, the scene is considered on (Regardless of the On level configured in the scene) If the device is 0, the scene is considered off. Not perfect, but better than systematically returning off as the initial state. Benoit

When you control a scene, GH remembers that the scene was turned on, or turned off. If you then change the state of the scene members, GH has no way to know you did this. The change I implemented is only for the initial query of the device. Note that in the Assistant, if you quit the device and get back in, it should query the device state.

Please pm me your uuid Another test you could do: http://<your isy>/rest/nodes/<your scene>?members=true Check if the members sections has link tags. For further analysis, I would need your uuid and/or the output of the above rest command. Benoit

You may want to check your scene, just make sure it has members. I made a fix to adress the case where a scene has no members, please try again. Benoit

Please PM me you uuid, I will check the logs

The query of ISY scenes has been enhanced, please see the edit at the bottom:

I think this may be due to the spoken used. It might be similar to another one you have, and Alexa is asking you if this is the correct device. Can you try changing the spoken?

There has been no changes to the skill. Must be an Amazon change.

If discovery is not recognized, then it's not specific to the skill. I would guess it's a transient error at Amazon and is likely to come back soon. Or perhaps it could be a local networking issue?

Thanks for the quick feedback. The "Device with Open/Close syntax" is something totally different. I understand that intuitively one would expect to get an Open/Close status. The thing is that to achieve this open/close syntax, we need to use one of the "controllers" that supports it, one of them being the "ToggleController". Then, to also support turning it on/off, we need to combine it with the Power Controller. All this results in the UI that you can see. I think it would be possible to show open/close instead, if we got rid of the PowerController, but that would mean those devices would not longer be able to be controlled with turn on/off. Only with Open/Close. Benoit

Hello, I made a fix to address this case. Would you mind testing again? Please test by looking at the Alexa app, but also using a routine. Thanks, Benoit

To answer your first question, I don't think passing the isyKey in a header would help, you would still have a POST reuse in the response. I checked your payload, and I noticed a few differences with the one the admin console uses. Use this soapaction header (Notice the ", I believe this is the cause of the problem): Soapaction "urn:udi-com:service:X_Insteon_Lighting_Service:1#Subscribe" And here's a body you should use (I noticed you have a malformed /reportURL tag : <s:Envelope><s:Body><u:Subscribe xmlns:u="urn:udi-com:service:X_Insteon_Lighting_Service:1"><reportURL>REUSE_SOCKET</reportURL><duration>infinite</duration><send>F</send></u:Subscribe></s:Body></s:Envelope> Benoit

If all you want to do is change the email address used for your Amazon account, I found this: https://www.businessinsider.com/how-to-change-email-on-amazon Benoit

The instructions were intended for smokegrub. Home A refers to one of his homes, not a setting somewhere, and instructions were for a browser. In the Alexa app, the options are not located at the same place, but the general logic remains the same. Unfortunately, there does not seem to be a "Forget all devices" in the Alexa app. I personnally find it easier to do the configuration on a computer, in a browser. For the purpose of clarification, the email address used with Alexa vs with ISY Portal don't have to be the same at all. When you are linking the skill, what matters is which ISY profile you are linking with. If during discovery devices are not discovered, do this: Login to ISY Portal with the SAME ISY Portal user profile you are using for linking. Make sure you see at least one ISY under the ISY tab. Click "My Profile" at the top right. If you have multiple ISYs in your account, and you want to discover all the devices: Under Amazon Echo and Google Home ISY, choose: "Use all ISYs in account" If you have multiple ISYs in your account, and you want to discover the devices of a single ISY: Under Amazon Echo and Google Home ISY, choose: "Use preferred ISY" Under My Preferred ISY, select the ISY you want to use If you have a single ISY, you don't need to do anything, it will use your ISY Make sure you have spokens for your ISY(s) Beside the relevant ISY, Go to Select tools | Connectivity | Amazon Echo If you have multiple properties, with each one ISY, you should have one ISY Portal user profile for each, and they should be configured to use the preferred ISY, and the preferred ISY should map to the relevant ISY. Benoit

Problem is now resolved. There was a misconfiguration on one of the proxy servers. When ISYs reconnected, they were directed to the less busy proxy server... which happened to be the one with the issue. Benoit

Make sure that you have an email address A for Home A. When you use email address A, Your spoken under Connectivity | Amazon Echo must be the spokens for Home A. Same goes for email address B and Home B. If you have that setup correctly, all you have to do is this:

Just a clarification about the ISY Portal email address. It does not matter what email system you use, or if it has MFA activated or not. There is no integration with the email system whatsoever. The only thing that matters is that it has to match an email address that exists and you can access. And the only time where this is relevant is to receive Portal notifications, or when you forget your email address and need to reset your password. If for some reason you lose access to your emails, ISY Portal will still function, you will still be able to login. It's just that you will be missing your notifications, and you won't be able to reset your password if you lose it.

Here's how to unlink/relink: Go to Alexa.amazon.com Make sure you are logged in with the Account for Home A. The last option in the menu allows you to disconnect Make sure to remove all devices Click on connected home | Devices Scroll to the botton and click Forget All. In the menu, Click skills Search for "ISY V3" Click on ISY Optimized for Smart Home V3 If the skill is enabled, you can click on "DISABLE SKILL" Click ENABLE to relink Enter the ISY Portal user and password for Home A. You should get a message to the effect that it's successfully linked. Close the window. Click on "Discover devices". This will retrieve the devices accessible by the user A (Home A). Repeat the same steps for Home B. Benoit

Hello everyone, We will have a maintenance this Sunday 04-12-2020 at 5:00 AM PDT which will last for up to 1 hour. During this period, your ISY will disconnect for a few brief moments. New feature: Hint Editor: Under Connectivity there will be a new option which allows to manually edit the "Hint" of a Nodeserver node. Maintenance: Install OS patches Benoit

Do you have an error message when linking? Or is it that you get no devices when doing a discovery? Benoit

I tested it and can't reproduce this problem. Are you sure you are using the URL to ISY as taken from the ISY information dialog? Are you using the admin console, or something else? Please provide more information on the SOAP call you are trying. Just an FYI, you can do SOAP request WITHOUT having the ISY code in the URL. In this case, it will use the preferred ISY. If the preferred ISY is not set, it would indeed give you such an error message. But if the ISY code is in the URL, this is what will be used to identify the destination ISY.

In the dialog box, click on the question mark to get help.

In ISY Portal, under Connectivity | IFTTT / Webhooks, you can enter devices there and have them be triggered from an external source. This is triggered using a simple HTTP GET. To get the URL, click on the icon besides the X. You could control this using IFTTT or anything that can trigger call urls. This could be as simple as a few URLs in an email for your installer. This is relatively safe as only the devices entered there can be triggered. However, if you have other webhooks for different purposes, then this gives away the key. I would change the key after the installer has passed. Benoit