bmercier

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)

Then I have no clue what is happening. The voice recognition and Amazon AI sometimes does funny things. I still think it gets confused somehow.

I though about this. I'm thinking you may have an insteon issue. Could you try to control your fan using a browser using these commands: To get the fan status: https://<your isy>/rest/nodes/<your fan address> To control your fan: Set speed: https://<your isy>/rest/nodes/<your fan address>/DON/<level> To stop the fan: https://<your isy>/rest/nodes/<your fan address>/DOF For a fanlinc, levels should be (use the maxSpeed) { value:1, name: 'Low', maxSpeed: 127}, // 1% - 49% { value:2, name: 'Medium', maxSpeed: 253}, // 50% - 99% { value:3, name: 'High', maxSpeed: 255}, // 100% Example: https://<your isy>/rest/nodes/<your fan address>/DON/253 to set it to medium. After changing the speed, get the status of your fan, see what the ST property. It should be set to the value you just set. I think it doesn't. If it goes back to fan speed 1, the value would be between 1 and 127. Benoit

I'm thinking that Alexa might be confusing things. Would you have any spokens with medium or high in it by any chance? Benoit.

Fanlinc has 4 levels when you include off (0 = off). With Fanlinc, high and maximum are the same speed. When it's a zwave device with 4 levels (5 with off), high and maximum are different speeds. Benoit

Following the Fan poll we had, I could see no correlation with the type of device or the region. I however made a change that might help for Fanlinc. If possible, I would need feedback from Fanlinc users: @asbril, @PurdueGuy, @oberkc First of all, make sure to: Delete the device from the echo App. (This is a critical step I found lately with respect to fans especially) Discover devices asbril, yours was already working, please make sure it still does. I reverted the change I made to recognize "medium", so this could have created an issue for this. Here, Medium works. When testing: First try the Alexa app. The icon should be a fan. You should be able to set the slider from 0 to 3, and the fan should change off-low-medium-high Then try vocally to set the speed to 0-1-2-3. "Alexa, set fan to 2" should set the fan to medium Then try vocally to set the speed to off-low-medium-high Please let me know how it goes. Benoit

What fan are you using. Fanlinc?

This is as expected. No issue here.

After flushing the devices in the Alexa app, after the discovery, did the devices reappear? If so, this means skill linking is ok. If not, please disable the skill and reenable it. Are you able to control devices from portal, ISY Web access? If so, that proves the connectivity between the ISY and portal is good. If you still have a problem, please open a ticket with your uuid referencing this thread, I will check the logs. Benoit

Can you pm me your uuid? I'll see if I can find something. Are you using echo or GH? And if so, do they still work?

Login to my.isy.io has not changed, it should be working. Can you reset yout password? Other UDI sites have changed so that it uses my.isy.io credentials (using oAuth).

Good to know. It works because when setting to low, it sets it to 24 (which is below 33), medium sets it to 49 (below 67) and High sets it to 74, which is (above 67).