bmercier

That can be any of those, except perhaps the device with open/close syntax, this one I'm not sure. A sensor won't work for sure as it can't be controlled. I would be cautious about "light" though. I think you can ask Alexa to turn off all the lights, and if it is categorized as a light, then Alexa would include it in the devices to turn off. But strictly from a routine perspective, it makes no differences.

If you want it to be managed through ISY, and see it does not work, yes. Benoit

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

Click the red x besides the spoken Sent from my iPhone using Tapatalk

Let me clarify what ISY Portal does. First of all, the previous value of the variable does not matter at all. Portal never keeps the previous value anyway. The logic is this; When receiving a variable value in the subscription: If the new value = the configured value for motion: An event is sent to Amazon telling that motion is detected. If the new value is not equal to the configured value for motion: An event is sent to Amazon telling that motion is NOT detected. This means that if the value is changed to various values outside the configured motion value, the not detected event may be sent multiple times. How does Alexa reacts to that? I'm not fully sure. If the state is the same as the previous state, I think it should be doing nothing. If a routine is configured to be triggered when there is no motion, then perhaps it could be triggered multiple times. Another case I need to mention: Whenever a request to "get a system status" is sent to ISY, the values of the nodes and variables are sent to all the subscribers... such as ISY Portal. This means that it's entirely possible to receive a variable value = the configured value, and later receive it again without actually changing the variable. This means the motion detected event could be sent twice. How does Alexa reacts to that? Same as above, not sure. Benoit

Oh, so your motion sensors are variables. This is the URL to get your state variable status: /rest/vars/get/2 From what I see, If your variable is set to 1, motion should be detected, else, no movement. Benoit

There has been no changes to motion sensors for several months. There are 2 things that may have changed which would reverse the logic. 1. Check your Portal echo config, and double check your device is categorized as a motion sensor (and not contact sensor). A contact sensor works in the opposite direction of a motion sensor. If it was a contact sensor, it would report the opposite. 2. Did you change firmware versions recently? There might be a bug. Check the output of /rest/nodes/<your isy device>. When there is no motion, the value of the ST property should be 0. If all looks good, I would encourage you to report to Amazon. Benoit

If you need to block access from ISY Portal: 1. Review your ISY Portal account users on the users tab. Remove those not needed, and change the passwords for those users you want to keep. This will block any access through the UI or APIs using "basic auth". 2. If you gave access to an Echo skill, Google Home and/or Polyglot, a change of password is not enough. If you want to block any access, including those you gave access, do this: a) Create a NEW user profile with admin rights b) Login with the new profile c) Delete the old one. Any oAuth access and refresh tokens issued to third party apps using the old profile will no longer work. Benoit

Yes it should.

Looks like you configured everything correctly. What is it exactly that is not working? What does it do when you try to open or close? Here's some general recommentations: Try with a simpler spoken, such as "test". Sometimes, the choice of spoken makes it hard for Alexa to recognize. Delete the Alexa device and re-discover. Sometimes, this type of device is picky, especially if you make a change of Alexa category in ISY Portal. It is best to delete the device in the Alexa and restart with a fresh one. Benoit

Check in the Alexa app what Alexa understands.

Maintenance is completed. Benoit

Hello everyone, We will have a maintenance this Sunday 08-23-2020 at 5:00 AM Pacific time which will last about 1 hour. During this period, subscriptions will be reset for brief moments. The purpose is to fix a bug related to subscriptions. Benoit

Which browser are you using? It's confirmed to work with Chrome. The help button only shows tips. The goal is not to talk about all the fields, but only about more tricky details. Benoit

Just added it to the Wiki. The easiest though is this: For each parameters, there is a tooltip that shows how to use it. For example, in the screen shot you attached, move your mouse over "Input 1". This will tell you how to use it with Alexa.

You seem to be confusing the "Input Select" with "Set channel to". If you want to change channels, go to the Basic tab, and set the "Set Channel To" to "State Variable", and choose the state variable that will receive the channel number. If you want to change the input, use: "Alexas, change input to <input name> on <device> Benoit

Just a quick note to let you know the maintenance is completed. Benoit

Unfortunately I have no clue. I wonder if this issye is widespread or not... I'm sure that's something Amazon could improve.

This maintenance should not have any impacts on Alexa Routines. ISY Portal won't be "disconnected from the Alexa Interface". In fact, it won't be noticed at all by Alexa, unless you happen to make a voice request at exactly the same time as your ISY gets disconnected from the Proxy, and this takes just a few seconds. Benoit

Hello everyone, We will have a maintenance this Sunday 07-26-2020 at 8: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. Benoit

To my knowledge, humidity is not supported, and temperature is not supported unless we expose the device as a temperature sensor, which currently is not implemented on ISY Portal, except for thermostats.

I would add that any notification is sent on the spot. So it may take a few seconds to reach it's destination, noting more. Benoit

I'm glad Chrome works. I'm thinking it might be a cookie issue. Perhaps Firefox would have worked in incognito mode. Unfortunately, it's hard to diagnose further without the HAR file from Firefox. It's really the call to the callback that is important, and to go further, we would need the details of that call. Benoit

If I understand correctly, after logging in to Ring and clicked on Authorize, the browser redirects you to Polyglot, and it shows a "Waiting for oAuth" message with a sort of circle in the center indicating it is waiting for something. Correct? If so, this looks like a PGC problem. In order to troubleshoot this further, I will ask that you perform these specific steps: Please use Chrome on a PC for all of this. 1. Login to PGC, and stop, then delete the nodeserver 2. Install the nodeserver 3. When you get the message, click on here, which brings you to the Ring login page. 4. Press F12 to open the Developer console. - In the developer console, click on the Network Tab - Client the checkbox "Preserve log" - Leave the developer console open 5. On the Ring login page, enter your credentials 6. In the authorization page, click on "Authorize". This should bring you to the Polyglot page where it says "Waiting for oAuth" 7. In the Developer Console, there is a "Down arrow" that allows you to "Export Har". Please click on it and save the file. That will allow us to investigate further what is happening. 8. Please open a ticket referencing this thread, and attach the HAR file. Thanks, Benoit

Good idea, but that would be surprising. When clicking the Authorize button, this simply does a browser redirect to Polyglot. Benoit.