bmercier

ISY Scenes can be brightened and dimmed, but can't be set to an absolute brightness level. In the V2 skill, we could give a scene the capability to be brightened and dimmed, without the capability to be set to an absolute level. In the V3 skill, which uses the Smart Home V3 API, the brightness capabilities are combined. To retain the ability to brighten/dim a scene, we had to give it the "brightnessController" capability, which allows to brighten/dim a scene, but also set it to an absolute level. Of course, ISY scenes don't support absolute levels, so whenever we receive a request to set a scene to an absolute level, the scene will be turned on or off if the brightness level >=50% (on) or <50% (off). With V3, the side effect in routines is that a scene looks like a dimmer which can be set to ab absolute level. Long story short, to turn on the scene in a routine, set the percentage >=50% to turn it on, and <50% to turn it off. Benoit

This is not currently planned. I will discuss with Michel. Thanks, Benoit

Thanks for the feedback. I'm glad to see everyone is up and running. Benoit

I investigated the logs for Cap, elliot and Bipto. For elliott and Bibto, things look normal. Do you experience duplicate spokens like cap does? Just wondering if there may be a different issue or not. If you have duplicate spokens, you may want to unlink, delete spokens and relink. For Cap, I see lots of device discoveries starting about 3 hours ago. Amazon does regular device discoveries on schedule. I can't differentiate between a manual request you would have made, and a scheduled one. I see 14 discovery within 3 hours, and this does not look normal to me. I even see some of them milliseconds apart, which are clearly not a manual request. That may explain duplicate spokens that you see in the Alexa app as well. My recommendation would have been to unlink, remove spokens and relink, but you already did that. I would then suggest the following. 1. Unlink the skill 2. Delete spokens in the Alexa app 3. Go to Amazon.com, click Accounts & Lists. Under Other accounts, click Login with Amazon. If you see anything related to UDI, remove it. 4. Relink Benoit

@elliot & @cap, please PM me your uuid, I'll see if I can find something. I confirm there has been no changes on ISY Portal for a while. Benoit

If you can control through the app, this means that it is properly configured. You don't need to send spokens as they are already there. Can you try using the Google Assistant app? Click on the mic icon and try to control. I think it may be because Google Home is configured with a different Google Account than the one you are using with the GH app.. Benoit

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

I would try to recreate the routine. There are cases where it may help. Benoit

Thanks for the update.

Is the ISY online on ISY Portal? Can you use the ISY Portal Web access? When unlinking/relinking GH, does it work? Do you see your device appearing in the GH App? Can you query the status of devices in the GH App? Benoit

Can you check in ISY Portal if your ISY is indeed offline? Benoit

Alexa. Smart Home skills cannot do this at this time. But this might be something Amazon adds eventually. The APIs are already there to query, which the mobile app uses.

In addition to querying thermostat, you can also query locks; Alexa, is front door locked? Regular devices, which includes variables, can't be queried by voice. However, they can be queried using the Alexa app. Benoit

Either this lock has been added in the past in ISY Portal and then removed, or it may be that you had alternate spokens on the device which are no longer there. Benoit

The fan can't be controlled via the mobile app. It can only be controlled by voice. If the device has the fan icon, you are good to go. You can ask the following: Turn on <spoken> Turn off <spoken> Set <spoken> to <Low|Medium|High> What's the speed of <spoken> Benoit

Exit the Amazon Echo dialog and get back in. The state variables shown are refreshed from ISY only when opening the Amazon Echo dialog. You could also try in your browser the following URL: http://<your isy ip>/rest/vars/definitions/2 This should get you your list of state variables. Benoit

That was fast!!

@Jimbo, the values have been adjusted. Can you try it again?

Checking

It's an easy change, but I'm wondering if this may be firmware dependant. Which version are you using? 5.x? Benoit

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&amp;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