bmercier

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.

Hello, I analyzed the log files, and I have questions. First of all, in the Polyglot UI you should see a notice like this: When you click on here, you should get a login page. After logging in, you are prompted to authorize Ring, a page like this: My example is in french, but you get the idea. You need to click on Authorize. After you click on Authorize, you should get a message like this in your Ring nodeserver log: 2020-07-18 18:34:15 info: NS: Received oAuth message { code: '<code>', state: '<state>' } I did not see this in your log. But maybe it's farther down. So, do you get the notice with the link to start the authorization? Can you get to the login page? Can you successfully login to Ring? Do you click on Authorize? Benoit

I'm having trouble finding the request. Would you mind trying it once more, and then reply here. That will give me an indication of the time to search. Benoit

Please pm me your uuid, will check the logs. Benoit

Exactly

Try .../services (without the .wsdl)

Please login to ISY Portal using XXXXXXXX@gmail.com Click on "My Profile" on the top right. You should see your preferred ISY, among other things. On this dialog, make sure that "Amazon Echo and Google Home ISY:" is set to "Use preferred ISY". Repeat the above for xxxxx@suddenlink.net. This setting can also be set to "Use all ISY's in the account". This setting is used for those customers that have 2 ISYs in the same facility and wants to have Alexa devices from both ISYs. I think this may be your problem. Benoit

What's the response body? It's likely to have more information pointing to the problem. Benoit

Do you get the authorization notice with the link? If so, are you able to login with your Ring credentials when authorizing? Benoit

I would suggest to try again, I think there have been issues recently with PGC itself that are now resolved. If you still have a problem after, we need to see what the Ring nodeserver logs are saying.

I added 2nd Ring Outdoor Cam with existing cam and doorbell. The cam motion node is not showing in PGC or obviously ISY. I’ve stopped and started node several times. If delete and add back is required will I need to redo folders ring associated programs? They may have to be edited and re-saved.

The values don't make sense to me. I had a typo in the command to set values. Could you try: http://192.168.0.33:1026/rest/nodes/14%20A0%20A%202/cmd/DON/127 Then: http://192.168.0.33:1026/rest/nodes/14%20A0%20A%202 You should be seeing 127 in the ST property. Benoit

Delete and reinstall the nodeserver.

After clearing and doing a discovery, they are still duplicated? In your spoken mapping (In the Alexa app dialog), if you have multiple "spoken" words per devices, that will create identical devices with a different Alexa name. If that does not solve the issue, could you please open a ticket with your uuid referencing this thread? I will look at the logs.

The easiest way to clean devices is to delete them all, and let the discovery create them. This way, you are sure not to delete the good one and keep the bad ones. Benoit

The spaces are replaced by %20, this is normal. It could be that your ISY is not configured for https. Try http instead: http://192.168.0.33:1026/rest/nodes/14%20A0%20A%202

In your node address, use spaces instead of dots (I know, not intuitive for a url)