bmercier

Please sign in to alexa.amazon.com. Please note the Amazon email you are using to sign in. Remove all of the existing devices from your Echo Go to Connected Home | Devices, and Click "Forget all". Deactivate and reactivate the skill Go to Connected Home | Skills, and select the skill Deactivate the skill Reactivate the skill. Enter your Amazon email and password if prompted (That would be an Amazon page) At the portal authorization page, enter your ISY Portal email and password for Home B. You should get an Amazon page with a button to Discover Devices. Click on Discover devices. Please verify if you have the correct devices. If you don't have the correct devices, please PM me: The ISY Portal email you used at step 3. The uuid of the ISY at Home B. I will check if your account is properly configured. Alternatively, you can just tell me, for Home A and B: What are the Amazon emails you use to login at both houses What are the ISY Portal emails you use to link the skill What are the ISY uuid Benoit

The email address shown in My profile is the email you used to log in. You can't change that. What you can do though is change the preferred ISY from My Profile, or from any user profile you see under Users. Benoit

A 'portal user profile' is what you use to login to ISY Portal. When you login, click "My prodfile" to see what is the preferred ISY for that user. You can also check other users in your account by going to the Users tab. Benoit

When you link the skill, make sure to link with the portal user profile for the location in question. Also, please verify the preferred ISY on those 2 portal user profiles. Benoit

Ideally, you should create a sub-account, and add their uuid and user profiles in that sub-account. The user in that sub-account will only have access to the sub-account. You on the other hand, being in the root account, will be able to see ISY in the root account AND sub-accounts. Benoit

Please unlink, forget all devices, and remink the skill. I’ve had this reported twice recently. Device discoveries were no longer reaching portal. This will refresh your devices as they are on portal. That will break your routines if you use them. Sent from my iPhone using Tapatalk

I would suggest to unlink and reliable. You may have devices that existed in ISY Portal that are no longer there, or were recreated, which would assign them a different ID. Sent from my iPhone using Tapatalk

Please open a ticket referencing this thread and your uuid. Will check the logs.

This is not usual. Please open a ticket referencing this thread with your uuid. I will check the logs. Benoit Sent from my iPhone using Tapatalk

Feedback to Amazon I guess. I never tried to report/investigate why a specific spoken would not work. Benoti

This must be a temporary Amazon issue. Did you try asking vocally, through the mobile app, or the web app? If vocally, Alexa might have understood something else.

Then there is an error in the URL. You should be getting an XML message coming from ISY, and your program should be running. You should get this working first before trying using the network resource. Also make sure to change your portal password as you just shared it with this post. Sent from my iPhone using Tapatalk

What do you get when trying from a browser? Sent from my iPhone using Tapatalk

To help troubleshoot this, keep an eye on that page. You can refresh using the refresh icon. No need to edit it. Technically, it should never be changed, except when editing if the values are considered invalid. I would suggest to change the spoken and retry. Sometimes, Alexa will understand incorrectly, especially if you have other devices with similar spokens. Try with something simple like "test", "kitchen" or "living room", common names that are easily recognizable.

What is the ISY Category (The "ISY Cat." column) ? After switching it to light and saving, does the Alexa Cat. column still shows it as Light?

Programs do have a status. It’s on, or it’s off, and it depends on if the program last ran the then , or the else. If you want to have a brightness level, then just expose a state variable directly. You can still turn it on or off, which will set the variable to the on value or the off value. You can then have a program that reacts to the on or off values. Benoit Sent from my iPhone using Tapatalk

Not a problem. I'll delay my replies next time Benoit

Yes it does. If the program is constantly restarted every 5 minutes, the 6 minute wait will never complete. The program does not have to be stopped. Restarting it using runThen is enough.

There is no need for an external computer. All that is required is an ISY, and ISY Portal. Benoit

Yes, that's possible. First of all, create a program that you will call via ISY Portal every 5 minutes or so: Heartbeat timer If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $PI_Heartbeat_active = 1 Wait 6 minutes $PI_Heartbeat_active = 0 Else - No Actions - (To add one, press 'Action') And: Heartbeat notification If $PI_Heartbeat_active is not 0 Then Send Notification to 'myself@gmail.com' content 'PI Heartbeat restarted' Else Send Notification to 'myself@gmail.com' content 'PI Heartbeat stopped' Then, you need to create a network resource to trigger that program via ISY Portal. First of all, find the ID of the heartbeat program (The first one above). In the admin console, when you have your list of programs, that will be the rightmost column. It's a 4 hexadecimal digits. To get the correct URL to call this program, go to ISY Portal, on your ISY, use Select tools | ISY information. The "URL to ISY" is the base URL to call rest commands. It will look like this: https://my.isy.io/isy/969f220dfc964cdb9c4cf4ef40275a580f7f8836ed3b7dc12047aa73f7e6f999 To that URL, add /rest/programs/<Program ID>/runThen Replace <Program ID> with your program ID. You can try this URL in a browser to make sure you are getting it right. Now to create the network resource, in the admin console, go to Configuration | Network resources. Click Add. Choose https, GET, host: my.isy.io, Port: 443, Path: Everything after my.isy.io (from the above URL), encode URL: no, use SNI: No In the HTTP headers, click Add, choose Authorization, and enter your portal user ID and password. Calling this network resource should trigger your heartbeat program Now, it's a matter of creating a program that will call this network resource every 5 minutes. If the network connectivity is lost, the heartbeat program will not be fired, and your variable will become 0, which will allow the second program to send a notification, or do whatever you want to do when there is no connectivity. This program would work. If ISY is restarted, the program would start looping at 6AM next day. test If Time is 6:00:00AM Then Resource 'test' Wait 5 minutes Run Program 'test' (Then Path) Else - No Actions - (To add one, press 'Action') Benoit

If you have scenes that you want to brighten/dim, set the Alexa category to light.

Those are responses from the ISY. The calls are getting throught. Now it's a question of having the correct URL to achieve the result that you want. If you try the same URLs with GET and POST directly to the ISY, without portal, you should be getting the exact same result. In the first case, you are getting a 404. I believe the URL is not valid. Try it in a browser. In the second case, I assume it's a post to /service. If I recall correctly, the 715 is an error code related to subscriptions. Benoit

Then I don't know what it is. It may not reach the request at all either. Adding console.log just before would help to find where the issue is. Benoit

Try the URL in a browser. Those are GET requests, so that's an easy way of test them. Benoit

This code is not triggering the request to ISY because the request is not actually called. At line 118, where you have: exports.handler = function (event, context) { You are reassigning a new function to exports.handler (The lambda starting point). You can't do that. It's already assigned at line 183, which is your main lambda function. And since you are just assigning a function to a variable, you are not calling the function at all. So, just remove the line "exports.handler = function (event, context) {", including the closing bracket, and try it again. Benoit