bmercier

For this to work, you also need to run the program then/else whenever the status of the scene changes; you could monitor the kpl button or any other device in the scene.

Let me share some technical details. Device statuses are sent to Amazon either: - Proactively (proactivelyReported=true) - Retrieved by Amazon on request. (retrievable=true) These are properties of a device returned during discovery. When looking at a device in the echo app, there is a status request sent to ISY Portal and to your ISY about every 2 seconds. That's if retrievable=true. The error message in the Alexa app is a bug. Whenever the retrievable=false, the error message appears, even if proactivelyReported=true. It should not, this is a known problem at Amazon. Now, in the case of a scene, there are no status available. Both proactivelyReported and retrievable must be set to false. That will not help you. You could use a work-around though. It's tedious, but what you could do is use a program to turn on/off your scenes, and expose your program to Alexa, instead of the actual scenes. Programs do have a status. If you need dimming for your scenes, there's no easy way. You could use a state variable to hold the dimming level, but then, you can't really set the dim level of a scene. Benoit

I see 2 possible reasons: - A discovery has not run yet (A discovery is required, and Amazon runs that automatically every 1-2 hours) - The device is a scene (Scenes exposed as a device will still have that error message). Benoit

Thanks for the suggestion. I'll see with Michel if/how we can do this.

The maintenance is complete. Benoit

If you look at your devices under Smart Home/Devices, if there is nothing, this is good. Step 3 is completed. The "Forget all" button will not appear if there are no devices. Just proceed to find and enable the V3 skill. You are almost done. Benoit

Hello everyone, We will have a small maintenance on Sunday 01-21-2018 at 5:00 AM PDT which will last a few minutes. No downtime is planned. Enhancements: - Amazon Echo V3 usage through the mobile app will work better; The device status will be shown, and there will no longer be "There was a problem". This will work for all device types, except for scenes due to the status which can't be retrieved. With kind regards, Benoit

@Ebrune, forget it, I found and fixed the problem. The issue was specific to the Auto mode, when using F. Benoit

@EBrune, I investigated further, and the query works as expected. Contrary to what I said above, it's normal that temperatures are passes in celsius at the API level. I contacted Google Home support. Please try this; Open your GH app, click on the upper left icon, and go to More settings/My Day/Weather Set it to Fahrenheit. Please let me know if that helps. Benoit

Ok thanks for the feedback. I took another look at the logs, and the setpoints are still passed in celsius. I noticed something strange though - When GH queries the thermostat, the temperatures returned are in the celsius range. There's no reasons for this, unless the thermostat is working in celsius. I'm lacking the time for further investigation as I'm leaving on vacation early tomorrow morning. I will look into this in about a week. Benoit

It is not, it's like this on purpose. Alexa does not have a concept of device nicknames. Therefore, if we want multiple spokens, then extra alexa devices needs to be created. Benoit

At the API level, I confirm that it passes the temperature in Celsius. Then, to get to the bottom of it, I would suggest to unlink and relink. Benoit.

Somehow, google is sending setpoints in celsius. Perhaps they changed something and it now uses a preference somewhere? Could you try "Ok google, change temperature to Fahrenheit" Normally, that should only affect things like weather services. The UOM for a thermostat is normally sent when synching (and yours is definitely set to F, I double checked the payload). Benoit

The steps are outlined here: http://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3 Benoit

I looked at the logs, and I see the sync with the correct uom set to Fahrenheit. Yet, whenever you make a request, Google sends degrees in celsius (there is no uom, but the values are in the celsius range, like these: 18.88888931274414 to 24.4444446563). I'm sure you did not say those numbers I think there is a bug at google where the uom is not updated. I would suggest to: - Remove the thermostat from ISY Portal - Sync, and make sure the thermostat disappears from the GH device list - Add the thermostat to ISY Portal - Sync again You could also try to unlink and relink, but you will have to redo the room assignments. Benoit

Please try this; ask "Ok google, sync my devices", then try again to control your thermostat. I have investigated and here's what I saw; - In ISY Portal, your thermostat is correctly detected as using Fahrenheit (The spoken records states that the thermostat works in F). - Google Home requests are coming in with values in the Celsius range Here's what I think happened: - A long time ago, there was a bug where thermostat added to ISY Portal GH spokens had a UOM incorrectly detected. - When you sync with GH, that UOM is passed to Google - When requests come in, they come in in that UOM. - I believe you removed and re-added your thermostat, which made it detect correctly the UOM as F, but then did not re-sync with GH. This would explain why requests that you speak in F are passed as C. Benoit

FYI, Even if an ISY scene is exposed as a GH light, it can't be dimmed.

To diagnose this one, I would need a copy of /rest/nodes/<your thermostat address> Please PM me that, along with your uuid. I may need to look at the logs as well. Thanks, Benoit

I don't think it will be possible.

This is normal. Google Home devices can have nicknames, so the alternate spokens are the devices nicknames. You can turn on/off devices using their nicknames. Benoit

The dimming problem is fixed. You will have to re-SYNC, as the issue was in the SYNC process. You can push it from ISY Portal, or just ask "Ok google, sync my devices" This is a problem that was introduced in the last update, in relation to color bulb support. Benoit

I believe you uncovered a bug. I'm currently working on a fix. Benoit

I think this may happen if you delete Programs on ISY then create new programs. You may end up with new programs reusing the same address as an older program. If you had that old programs in ISY Portal, and had not deleted it there as well, then when you try to add the new program, you end up with a duplicate.

This means that the item (the program you are trying to add) is already in the list. Each program have an address. Use the search box to find the existing program using it's address. The program address has 4 characters, and you can see it in the program selector, it is in parenthesis. Benoit

Yes it is expected, and it was he same in V2.