bmercier

Please try this, it this is not too much trouble: Disable the skill, then re-enable the skill. Delete the routine and re-create the routine. If that does not work, please PM me your UUID for further investigation on the server side. Benoit

Thanks for the suggestion. This will be implemented. Benoit

So we know that: Your spoken is correctly set. It has been discovered by Alexa. You are changing your state variable to the correct values. Now, the issue could be: Live update not enabled (But you already checked that it is enabled) So, what's left is the routine itself. Please delete and re-create the routine. Make sure the action works by doing a "play routine". Benoit

It may. As per Amazon specs, state changes are debounced. They can't be more often than every 30 seconds. So, if there was no activity in the last 30 seconds, the change should be fairly immediate. If it went detected, it won't go to non-detected state until 30 (or more). Benoit

Is "Live update" is enabled? Can you find the device in the Alexa app, and check the status? Can you set it to detected/not-detected based on the variable value?

Here's some troubleshooting tips: In the Alexa spoken window, make sure "Live update" is enabled. Make sure in your routine action that it speaks to the correct echo (A common mistake, at least for me, is to have the wrong echo) On the routine, use the menu | Play routine. Make sure it does what you expect. Try deleting the routine and recreate it. If for example you created a routine triggered by a variable exposed as an contact sensor, then you change it to a motion sensor in ISY Portal. The routine will no longer work. If nothing works, find the device in the Alexa app, and check the status. It is refreshed every 2 seconds or so. This should always work.

This is an issue that happens once in a while. @apostolakisl, this will sound weird, but please try this. In your list of spokens, please add one or two devices, even if you don't use them. Please use devices that regularly changes state, once a day or more. It would be long to explain, but it seems the issue is that google loses track of the "agentUserId" which uniquely identifies the user sending. When requesting to send spokens, this makes a request using your agentUserId. In addition, when devices changes states, the same authentication mecanism is used. I think that making regular requests such as sending devices states helps. In your case, all you have are scenes and programs, which don't have states. Adding devices that sends states could help. In parallel I will also reopen an older ticked with Google. Thanks, Benoit

Variables can only be exposed by as motion sensors, and this is by design. I figured that the only use case would be to trigger routines, so this was sufficient. But I understand that querying if the garage door is open is an interesting one. The list of devices shown has not changed. There are devices that are excluded, such as Remotelinc nodes, range extenders, energy nodes. If you have a node missing that you would like to see there, such as your zwave tilt sensor, please PM me the output of the ZWave node. /rest/nodes/<your node> Benoit

Not that I know of. If you can get the humidity to a state variable, and expose the variable as a light, the brightness level could be queried. But I don't know if there is a vernacular for this. I did not find it when V3 was released, but perhaps Amazon added it. Not sure. Benoit

Let me share with you some of the inner workings. At the API level, Alexa can query the status of motion sensor or contact sensor. Whenever you use the Alexa app to see the status of a sensor, this uses the API. Now, in the case of a contact sensor, I know you can ask "Alexa, is <sensor> closed?". Same for open. I'm not aware what is/if there is a vernacular to query a motion sensor. If there is one and you can figure out what it is, I can tell you the API to actually query the sensor is implemented and will work. Benoit

The maintenance should not have affected licences. Please open a ticket with your UUID referencing this thread. Will check it out promptly. Benoit

Instructions below. This will be on the wiki soon. Using Alexa Routines Alexa has for a while allowed you to create Alexa Routines to automate voice-related tasks. This capability is found in the Alexa mobile app, under Routines. Amazon has enhanced this by releasing new smart home capabilities to support motion sensors and contact sensors. The main benefit of this is to use them as triggers to an Alexa routine. ISY Portal now supports these new motions sensors & contact sensors capabilities. In ISY Portal, under the Connectivity | Amazon Echo dialog, You can choose any ISY device, and expose it to Alexa as a motion sensor or a contact sensor. That can be a real motion or contact sensor, but that could also be an IOLinc or a plain regular light. To configure a device as a sensor, just set the Alexa category to Motion sensor or Contact sensor. If you are the owner of an ELM M1 Alarm system, and have it integrated with your ISY, you can use it too! You can expose any of the zones as a motion or contact sensor. In addition to ISY nodes and ELK zones, you can also expose a state variable as a motion sensor. When configuring this, you need to specify a "Motion detected value". Whenever the state variable will be set to that value, the motion sensor status will be set to "Detected". Any other value will set the motion sensor to "Not detected". But why would someone want to expose a state variable as a motion sensor? The whole purpose is to trigger Alexa routines programmatically. One of the simple but nice feature of an Alexa routine is to say something you decide, whenever the routine is triggered. Therefore, using variables exposed as motion sensors allows you to create programs that tells Alexa to say something. Now your ISY can talk! What Alexa says is configured within the routine, and therefore static. But you can create as many routines as you want, and you can do so using a single variable. When you create the spoken in ISY Portal, you can reuse multiple times the same variable, expose it as a sensor, but use a different "Motion detected value". This allows you to have Alexa say something when value=1, something else if it value = 2, etc... Troubleshooting tips: Whenever you make changes to your spokens, please remember to have Alexa discover the devices. You can just ask "Alexa, discover my devices". If you delete or rename spokens, remember to go to the Alexa app and delete those obsolete devices. Otherwise, they will just stay there as "offline", but it will still be recognized by Alexa and give you an error message. If you change the type of a device, let's say from motion sensor to contact sensor, and you have used it in a routine, you will have to remove it from the routine, and re-add it. For more informations on Alexa Routines: https://www.amazon.com/gp/help/customer/display.html?nodeId=G202200080

This morning's update is completed. Benoit

This is not currently in the roadmap. So far, the intent was for IFTTT, and renaming things were a small change. For sure, it's a best practice to use different keys for different services, but how many users would use 2+ services with this? Benoit

Thanks for the suggestion. I made the changes in dev, this will be in production Sunday. Benoit

You may want to consider adding a ZWave repeater, close to the deadbolt itself. I guess this may vary from one deadbolt to another, but my experience is that the ZWave range is really short. So I would position a ZWave repeater close to the deadbolt itself. Here's one: https://aeotec.com/z-wave-repeater Yes, you can have a program that locks after a certain amount of time. Benoit

Where do you see a duplication? It has nothing to do with IFTTT. I used IFTTT as an analogy to explain how an Alexa routine works. The portal does not "know about triggers". What I explained is that portal bridges the gap between an ISY Variable and an Alexa routine. It allows an ISY Variable to be seen by Alexa as a motion sensor, and an Alexa motion sensors can be used to trigger an Alexa routine. Benoit

You are absolutely correct. But if we rename it to something more generic, then someone looking to do IFTTT would not find it or think about IFTTT. Benoit

This has to do with Alexa Routines. Alexa routines allows you to automate things based on certain events. An Alexa routine is similar to IFTTT. If <event> then do <action>. The event can be a Smart Home motion sensor detecting movement. The action can be Alexa giving you the weather, or simply Alexa saying something. So far, this functionnality allows you to have an ISY device, such as a motion sensor, to trigger Alexa to say something. Now comes the variable. ISY Portal will allow you to have an ISY State variable exposed as an Alexa Motion Sensor. Whenever the variable will be set to a certain value, the motion sensor will be "ON". So, in short, you can have a variable that, when set to a certain value, will have Alexa say something. This new functionnality will be available starting Sunday. Benoit

FYI, the only devices currently supported which can trigger a routine are motion sensors and contact sensors. Yes, exposing a state variable as a motion sensor allows to trigger any routine. I made it in such a way that a single variable can be used to trigger multiple routines based on the variable value. Benoit

This is now implemented in dev. This will be live Sunday. Benoit

Hello all, I'm currently looking into exposing state variables as motion sensors. Stay tuned Benoit

No, it has not been implemented. But I know where you are going, and there is a work around. If you have the A10 module, you can create a virtual device which can be used as a sensor, and therefore, a trigger to a routine. In the admin console, click Link Management/New INSTEON/A10/X10 device. From the list choose generic X10. Enter an address, such as "A10", a name, and create the device. Benoit

This will eventually be possible with Alexa notifications. At this time, the Alexa notifications beta program is closed, they are changing the API based on developer feedback. Stay tuned. Benoit

The feature is coming next sunday: You will be able to use take just about any ISY device, such as IOLink, Insteon motion sensor, or even plain switches, and expose them either as a motion sensor or a contact sensor. ELK zones are also supported. Using it in routines allows to do pretty cool stuff. Benoit