bmercier

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.

Could it be that you have a device with the same name?

I'm not seeing any requests coming in. Not even at the oAuth level. It looks like if the skill is not linked at all. Is it linked? If so, can you unlink and relink it? Benoit

If the only problem is the Alexa app saying "There was a problem", this is a known problem which has been submitted to Amazon. Other than that, are you able to control your devices from your echo? Looking at the logs, I see no oAuth problems as we had during the initial few days of the launch. Benoit

Good to know, I was not aware of this one. Benoit

I see communication errors. It does not seem to be related to the same oAuth issue that was fixed. Can you try again?

That’s also my impression Sent from my iPhone using Tapatalk

@rebirth24, In Alexa, does your ISY scene appear under devices, or under scenes? If it appears under devices, this is the expected behavior. Benoit

Hi Michael, I am not fully sure of when/how the issue happens, but I don't think it's related to the portal upgrade. This error is shown when the google API returns me a "INVALID_ARGUMENT". This is normally due to giving it an invalid agentUserId - This case happens when the account is not linked (Google does not recognize the agentUserId, which is passed when doing the account link). Possible cases: - Google Home not being linked - Having linked with user profile A, then login to ISY portal using profile B. Even if it's in the same account, this error will be shown. - I'm aware of an another case, as asbril mentioned, and that happens when a user has linked more than once to the same ISY Portal account. I looked at the logs, and saw the failure(s). I tried to see which user profile it was linked to the last time that you linked, but the logging server does not keep enough days back in time. I'm under the impression that Google loses that piece of information somehow. I recently fixed an issue with our oAuth server. Perhaps that will help. As for the room, sure that would help a lot. Whenever Google will support it, we will. Benoit

The maintenance is complete. Merry Christmas! Benoit

Ask Alexa: "Alexa, refresh my devices" This will refresh the change from ISY Portal to Echo. Benoit

Yes "Alexa scene" was a typo. I should have called it a Google scene. Google and Echo both have a device type named "scene". I call them an Alexa scene (or a Google scene in this case) to distinguish from an ISY scene. The only advantage, to my knowledge, is the ability to use a wording like "Ok google, activate <name>". Also, if you don't want the ISY scene to have a light, outlet or switch icon, then exposing it as a scene may be a good option. If your scenes are used primarily for lighting, then it's probably best to expose them as light. One of the drawbacks of exposing an ISY scene as a Google scene is that they can't be dimmed. FYI, the Echo skill already has all of that functionality. One of the goal of this update is to bring GH functionality at par with the Echo skill. Benoit