bmercier

The API used to sync devices has a field for the room, and that field is set with the room configured in ISY Portal. When GH integration was initially implemented, I tested it and it did not work. This, and other documented features, were not working. I think they were planned, but not yet implemented on Google's side. It may very well have been implemented since then. This would need to be retested. Benoit

Can you test the values match the speed? Does setting it to 99 make it run at medium speed? Does setting it to 100 make it run at high speed? I could not test with a real fanlinc, so I relied on this: https://forum.universal-devices.com/topic/12477-fanlinc-rest-api/?do=findComment&comment=102016 Benoit

Which fan are you using? Low/Med/High are using FanLinc max values. Off is 0 Low is 49 Medium is 99 High is 100 Benoit

I have a surprise for you. ISY/GH now supports fans. In ISY Portal, edit the device, and just change the GH type to "Fan". All you need to do is: - Create the device, and chose the GH Category "Fan" (You can also edit your existing fan exposed as a light) - Click Send Spokens to Google Home (Or sync by asking GH) - Tests the vocal requests Turn on <fan> Turn off <fan> Set <fan> to Low|Medium|High What's the speed of <fan> (Should return Off|Low|Medium|High) This should work well with a fanlinc. If you have another sort of fan, your mileage may vary. Benoit

You don't lose the "Home". But you do lose the room assignments, unfortunately. Benoit

It did!

The skill does not know which Echo made the request. That is not possible. However, you may be able to send contextual command with the help of Alexa groups. When you have devices and an echo in the same Alexa group, you can say things such as "Alexa, turn on the light", and it will know that you want to turn on the lights in that group. Perhaps that you could do the same with thermostat, I have not tried it. Ref: https://www.amazon.com/gp/help/customer/display.html?nodeId=201749250 Benoit

Amazon has no specific vernacular to control curtains. It has to be done through: "Alexa, turn on <device>" or "Alexa, turn off <device>" Some users have been able to use "Alexa, close <device>", but this is highly dependant on the naming of the device, and likely to not work. "Alexa, open ...." is normally used to "open" a custom skill, so I doubt you will have success with it. So, I would suggest to first try with turn on/turn off, although it may not be as natural. To find out the device name, look at the devices in the Alexa app. You could also find it in ISY Portal, under Connectivity | Amazon Echo. Benoit

You need to use the mobile app, not web.

Please use the Google App to unlink and relink. Also, in your GH Spokens, if by any chance you only have scenes and or programs, please add a "dummy" device in there, one that changes at least every days. This is to keep the link active. Benoit

No, the update was not backed out. You should see "My Account" besides "ISY" and "Users". You should see "My profile" at the top right of the screen. The new option is shown only in My Profile. Benoit

No, I did not do anything in the background. I'm glad to see it's working. Benoit

To troubleshoot this, first go see the device in the Alexa app (Choose the device that has motion detected when value is 9). Can you see the motion detected/No motion change when the variable changes from 0 to 9? Benoit

Excellent. Mystery solved

Yes, what a coincidence! To renew, login to my.isy.io. On your ISY, click Select Tools | Information | ISY Portal Access License, and click on Renew License. Benoit

Do you say ‘apparently’ because it should not be? Benoit Sent from my iPhone using Tapatalk

Oh, I see. In addition to the mobile app, you can use a regular browser. Go to https://alexa.amazon.com The navigation is virtually the same. Or, you may try to kill the mobile app and retry it there too. Benoit

Yes, and I recommended to use another browser, or clear the browser cache.

You need to disable and re-enable the skill. Benoit

Can you try with another browser, or clear the browser cache? This is what helped aweber1nj Benoit

Please try it again. Should be working now. This was NOT due to this morning's update. It's something that Amazon changed recently. I reviewed the API, and by trial and error, I was able to figure out the problem. Technically, I expose the PowerController controller for thermostats, which allows to say Alexa, turn off <thermostat>, which sets the mode to off. When returning the thermostat state, we need to return the power state on/off, which previously was not a requirement. Benoit

I can reproduce the issue in the test environment. Alexa app does not show the device status, Echo show shows the ambient temps and setpoint, and allows to change it. This morning's update did not have changes in the area of thermostat handling. This looks to me as a breaking change in the Alexa app. Do you remember when was the last time you used it on the Alexa app? Benoit

So the password issue is with the Amazon account. You may want to try to reset that password. Benoit

Please PM me your UUID, will check the logs. Benoit

Ok then it's because it's already disabled. You can click on Enable to enable the skill. Benoit