bmercier

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.

Hello everyone, After investigation, many errors are referring to non-existent spokens in ISY Portal. This case can happen when a spoken has been added in ISY Portal, then discovered by Echo, then later deleted from ISY Portal. If such a spoken still exists in echo, it will be marked as (offline). You can still try to use it, the request will be sent to ISY Portal, but an error will be sent to Echo. So, if you encounter that issue, please do the following in the echo app: 1 - Go to Settings / History, and look at the request understood by Alexa. Take note of the spoken. 2 - In Smart Home / Devices, lookup your spoken, see if it is marked offline. Please make a search to find out if you have more than one. If you Created a spoken "abc", discover, remove it from ISY portal, then re-create spoken "abc", then discover, you will end up with 2 spokens named "abc". One of them will necessarily be marked offline. If that happens, please forget that device. If you still have issues, please open a ticket and specify your uuid, and the date you tried it. ISY Portal has been updated an hour ago with additional logging to help troubleshoot this issue. If you already have a ticket opened, please reply to the ticket and let us know you still have the issue, and when you tried it. Thanks, Benoit

For now I would suggest to just keep live update disabled Sent from my iPhone using Tapatalk

If you change the mode, then setpoint, then again, that would be several events in a short period of time. Then the fan may come on. That's another event. Benoit

Then I may need to revise that logic. FYI Thermostat events are already debounced. If there are multiple events for the same thermostat within a short period of time (1 second), only one lookup will be done. I may need to increase that delay. Benoit

I can share some insights on this one. When you have both the V3 skill enabled and Live update enabled, then a "permanent" subscription is started. That subscription is the same as when the admin console is started, or when Mobilinc is used. This is used to capture the state of Alexa devices, and send it to Amazon so that it can be displayed on the mobile app. Whenever a light goes on or off for example, an event is sent, it is captured, and sent to Amazon. Now, for thermostat specifically, the logic is this. Whenever a thermostat event is received, a /rest/nodes/<thermostat address> is sent to get all of the thermostat properties. Amazon wants to receive all of the device properties, so this is the reason for this "lookup". Now the question becomes why are there so many requests? A thermostat property should not change that often. Benoit

Ok great, I was not aware of that. Benoit Sent from my iPhone using Tapatalk

To my knowledge, it's not possible to dynamically set the content of a network resource. If someone really wanted that, I guess you could configure 20-30 network resources with each a specific numeric value, 20-30 programs, and use a state var to trigger the corresponding network resource. But that's a lot of network resources and programs for the task. Benoit

I think in most cases, it’s easier to use fixed network resources to increase and decrease volume, and assign them to the volume up/down, and not use network state variables at all. Sent from my iPhone using Tapatalk

Thanks for the report. It’s now fixed in dev. Sent from my iPhone using Tapatalk

The update is complete. Benoit

Humm... Strange. I would try with the iOS or android app then. Benoit

You need to uninstall the V2 skill, and install V3. The V3 skill is available in Canada. Benoit

I have applied for the developer preview. Given the amount of interest, this may be added to the roadmap. Thanks all, Benoit

In order to turn on/off lights based on which echo you speak to: 1. Create an Alexa group (The name does not matter) 2. Add your Alexa device in that group (You need the iOS or Android app to do this - alexa.amazon.com web app does not support that) 3 Add your lighting devices in that group That's it. Now, what it allows you do do is: - Say "Alexa, turn off the lights", which will turn off all lights in the same group as Echo. - Say "Alexa, turn on the lights", which will turn off all lights in the same group as Echo. FAQ: Why does my scene does not turn on/off? A scene is not a lighting device. Only devices identified as a light will turn on/off. In the next update tomorrow to the V3 skill, you will be able to make your scene appear as a lighting device. Can I have 2 devices named the same, like "Alexa, turn off the bedroom light" which targets different devices depending on the echo? No. Alexa device names (or spokens) needs to be unique. Furthermore, when you specify a device name in your command, this is not limited to the group the Echo device is in. Your device could be in another group, or in no group at all, and it will be accessible. I can't add my echo to the group. You need to use the iOS or Android app. The Alexa web app does not support that yet. Benoit

This is currently not in the roadmap. Do you have specific use cases in mind? Benoit

No. What this will allow you to do is: In ISY, you have a scene. In Alexa, that scene will appear like a regular lighting device. What does that mean? It means that: - In Alexa, the scene will appear with a light icon (It has another icon, and shows up under scenes, instead of devices) - If you ask "Alexa, lights off", it will be turned off (scenes are not turned off or on by such a command) - In a Routine, you will be able to add it and choose to turn it off. (scenes can only be activated, not deactivated) Benoit

This is strange. Have you also removed the devices in that second account? I reproduces the problem, and by unlinking the skill and removing devices, SYNC requests then worked. Sent from my iPhone using Tapatalk

You could have an ISY scene that shows up in Alexa as a light. This allows things like implicit targeting; “Alexa, lights off” for example does not work on scenes, but if that scene becomes a lightning device, then it would turn off. Sent from my iPhone using Tapatalk

Unfortunately we have no control over this. Only Amazon could potentially enhance this.