bmercier

Hello all, I'm currently looking into exposing state variables as motion sensors. Stay tuned Benoit

No, it has not been implemented. But I know where you are going, and there is a work around. If you have the A10 module, you can create a virtual device which can be used as a sensor, and therefore, a trigger to a routine. In the admin console, click Link Management/New INSTEON/A10/X10 device. From the list choose generic X10. Enter an address, such as "A10", a name, and create the device. Benoit

This will eventually be possible with Alexa notifications. At this time, the Alexa notifications beta program is closed, they are changing the API based on developer feedback. Stay tuned. Benoit

The feature is coming next sunday: You will be able to use take just about any ISY device, such as IOLink, Insteon motion sensor, or even plain switches, and expose them either as a motion sensor or a contact sensor. ELK zones are also supported. Using it in routines allows to do pretty cool stuff. Benoit

Hello everyone, We will have a maintenance next Sunday 30-09-2018 at 5:00 AM PDT which will last for up to 1 hour. During this period, the subscription server will be restarted, which will drop any active subscriptions. If you use Mobilinc, the app will automatically reconnect when it's back online. New feature: Add support for Alexa contact and motion sensors. ISY devices, State variables & ELK Zones can be exposed as Alexa contact sensor or motion sensor. The main benefit is to use them as triggers in Alexa routines. Maintenance: Install OS patches Benoit

Hello everyone, I'm currently looking into implementing contact sensors, but I don't have contact sensors to test. When a contact sensor is open, what is the node status exactly? 0? Or non-zero? Benoit

Don't worry with it. It is not relevant to the issue here. This is used only with earlier versions of the skill (V1 & V2). Benoit

Something is mixed up. We need to check that: Echo A uses Amazon account A, which is linked to ISY Portal user A, which has its preferred ISY set to ISY A. Echo B uses Amazon account B, which is linked to ISY Portal user B, which has its preferred ISY set to ISY B. Please write down for both locations: The Amazon account The ISY Portal user profile The UUID Instructions: Login to ISY Portal using either user profile. Go to "Users". Make sure that each user profile is mapped to the correct location's UUID. For both locations: Login to the echo app (https://alexa.amazon.com) using the location's Amazon account Go to Settings. Make sure that you see the current location's Echo device. Not the other location's echo. Go to Smart Home | Devices, click Forget all (At the bottom right) Go to Skills, find the "ISY Optimized for Smart Home V3". Click Disable, then Enable. When linking with ISY Portal, make sure to use the ISY Portal user profile for that location. When you discover devices, you should be getting the devices from the ISY related to the Portal user profile you just linked to. Tips for testing: In addition to testing with the echo itself, you can test using the Alexa app (iOS version, and possibly Mac as well). Go to Smart Home, find your device, and turn it on/off using the app. Benoit

I don't use a Mac. There must be a logout button in the app somewhere. In the iOS App, it's the "Sign out" button under settings. It might be the same on the Mac. Personally, instead of using the app, I would use the web version: https://alexa.amazon.com. In the web app, when you want to switch amazon account, you can logout by clicking the last option on the left.

Login to ISY portal Click on "users" You will see your 2 user profiles, showing the preferred ISY associated. Edit one of the two, and change the UUID. Alternatively, you can login to ISY Portal with both user profiles one after the other, click on my profile, and edit the preferred ISY there. It has the exact same effect. Benoit

For the benefit of everyone, the initial issue he was having was due to the fact that a single ISY Portal User Profile was used. There has to be 2 ISY Portal User profile. @smokegrub, I just looked at your account. I see that you now have 2 user profiles, which is good. But the problem is that both user profiles are pointing to the same ISY.

Could you also PM me your UUID, I'll take a look at the logs and see if I can find something. Benoit

At the end, when you say "I can't": What devices do you have? Are your devices still there, but showing offline? Have your devices disappeared, and they have been replaced by your wife's? Benoit

Ok, so it's either an issue with variable substition (probably not), or the path length. Either way, we need help from Michel. Benoit

I'm suspecting an issue with the path length. I would try the network resource, but use a fixed value instead of a variable.

@Michel Kohanim , could there be an issue with the path length? Benoit

I understand you expect me to find the problem, but I don't see anything wrong here. Please try if from a browser first.

@apostolakisl, to facilitate troubleshooting, I would suggest the following; Go to ISY Portal, choose the ISY Access. Open up the developer console with F12. Whenever you do something, you can see the URL used in the network tab (If using Chrome). Those are calls to your ISY through ISY Portal. You can cut & paste the URL and try it in a browser directly, then adapt it to the network resource. Benoit

The host name is my.isy.io Other than that, it seems to be correct. I would suggest to try it first from a browser to help troubleshooting. Benoit

In the ISY network resource, if you choose https, you don't have to supply a port number. It's implicitly 443.

You have to: Set the host to my.isy.io Set the protocol to HTTPS (if not already set to HTTPS) Change the URL to include the ISY Key (What you see in the URL to ISY after the host name). The authorization will be different. When going through ISY Portal, you have to use an ISY Portal user and password, not your regular ISY credentials) Not sure this is in the Wiki. Benoit

It's easier than that. Use Select tools | ISY Information, look at the "URL to ISY". Just use this URL, and add regular rest commands to this URL. You need to pass your ISY Portal Credential. Benoit

I'm also using Chrome, and this should work for most browsers. To be more specific, when you have the A/V Dialog open, let's say on the input tab, hovering over "Input 1" should show you a tooltip (A small popup) with a sample wording. Benoit

Quick tip: When you are on the A/V dialog, move you mouse over the field label. It shows a sample wording to invoke the action.

Suggestions: Try "Alexa, change input to <input> on <device>". This one is known to work. Try different input name. game works. Alexa can be picky on the input names, and it has to exactly match one of the inputs. Look at the history. Make sure she understood the input name like you intended. Benoit