bmercier

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

Hello everyone, We will have a maintenance this Sunday 12-24-2017 at 5:00 AM PDT which will last 1 hour. During this period, your ISY will be offline for a few seconds. Changes - Google Home: Color bulb support. - Google Home: Ability to expose scenes/devices/programs a Google scenes (in addition to light/switch/outlet) - Google Home: Ability to expose devices as Light, Switch or Outlet - Google Home: Preferred ISY is no longer required if there is only one ISY in the account. - Proxy bug fixes and additional logging - Subscription servers bug fixes and additional logging When adding color bulbs, you need to add the zwave color node (ZW999_186) Merry Christmas and Happy Holidays! Benoit

I made a fix on the 13th. I was trying to figure out if the issue started before, or after. If before, then it's good news. Benoit

When did it stop working? Sent from my iPhone using Tapatalk

I'm not seeing any approval request for a UUID ending with :67. I searched for the last 5 days. It looks like the request is not reaching ISY Portal. I would suggest to open a ticket, and please specify your UUID. I'm not sure what it could be. Michel will investigate. Thanks, Benoit

I believe the limit is 5 or so. Michel could confirm. Is your UUID ending with :90? I see 5 successful linkings, but somehow, some are like 3 seconds apart. Benoit

I believe you are hitting a limit on the number of approved accounts (or sub-accounts) in ISY. I investigated logs and reported the case. Benoit

It’s up to you. If they start getting a few support requests on that topic, maybe this will push them to investigate further. Sent from my iPhone using Tapatalk

The ISY Smart home skill V3 Sent from my iPhone using Tapatalk

Hello Everyone, I found a potential cause for this issue and made a fix. This is now in production. I also added additional oAuth logging, should the fix not solve the problem. Please report any other occurrence of this problem. Please PM me: - Your UUID - Specify at what time the problem started, and if possible, when was the last successful request. Feel free to fix it immediately by unlinking and relinking. Thanks for your help, Benoit

The reason for multiple devices is because somehow, Amazon is making a request for a previous skill version. They are doubled because the device unique IDs are generated differently. I have seen cases where Amazon keeps remnants of former skills. Here in the dev environment, whenever I do a discovery, I keep getting requests from Amazon that are from former test oAuth client IDs that belong to test skills that have long been disabled. I had reported that to Amazon, but this seems to be a complex issue. I would try this; Go to www.amazon.com, go to Your Account, and under Other accounts, click Login with Amazon. If using V3, you no longer need a consent for ISY Portal. Alternatively, you can go to ISY Portal, My Profile, and unlink from Amazon. If using V3, you no longer need that. Either way, that will block access for the V1 and V2 skill. FYI, V1 and V2 were using Amazon's oAuth "Login with Amazon". V3 is using our own oAuth server. Benoit

ISY is not aware of an action by Alexa vs other means. This is why I was proposing to use an intermediary (state var or program). However, if we are considering only lights, and you want to differentiate between physical action vs other means, then yes it’s possible. In your program, use ‘control’ instead of ‘status’. Control is triggered only by physically actions on the switch. Benoit Sent from my iPhone using Tapatalk

I would suggest to use state variables, or programs. If you want to use dimming, then use a state variable. You can expose it to Alexa as a light. Then a program can actually turn on/off the light or set the brightness level whenever the state variable changes. If you don't use dimming, then you could directly control a progran (On = then, Off = Else), and do whatever you want in it, including turning your device on or off. Benoit

Hello Everyone, Quick update, I have investigated Condor's log. It seems to point towards an oAuth2 authorization issue. When Condor's request failed at 13:24 EST, there is no request at all made to ISY portal. The last working request is a discovery, which runs every hour or so automatically, and that was at 5:43 EST I will need more time, but at least, I'm on something. Thanks! Benoit

Hi Mike, Can you either PM me or open a ticket and specify your UUID. I will investigate this. The details you posted will help greatly. Thanks, Benoit.