DaveStLou Posted October 5, 2018 Posted October 5, 2018 (edited) On 10/4/2018 at 10:39 AM, south said: I can "play routine" and that works. But when I manually change the variable everything works but the vocal response is not heard. I am at a loss as what to do now. Thanks. I glad to know I'm not the only one having this issue. I have other routines that I've initiated by voice for some time so working with them is not new to me. I can get the routines to work on schedule but not triggered by variable or motion detector through the portal. It doesn't matter if I try to get Alexa to speak or just turn off another device, it doesn't trigger. Oddly, I can pull up the "motion sensor" device in Smart Home in the Alexa app and it will show the correct status. But does not trigger the routine. Edited October 5, 2018 by DaveStLou Forgot to include some informaiton
bmercier Posted October 6, 2018 Author Posted October 6, 2018 58 minutes ago, DaveStLou said: I glad to know I'm not the only one having this issue. I have other routines that I've initiated by voice for some time so working with them is not new to me. I can get the routines to work on schedule but not triggered by variable or motion detector through the portal. It doesn't matter if I try to get Alexa to speak or just turn off another device, it doesn't trigger. Oddly, I can pull up the "motion sensor" device in Smart Home in the Alexa app and it will show the correct status. But does not trigger the routine. 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
DaveStLou Posted October 6, 2018 Posted October 6, 2018 1 hour ago, bmercier said: 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 Followed your steps. It seems to be working now. Thanks!
brians Posted October 6, 2018 Posted October 6, 2018 (edited) I don't see the ability to make a routine in Alexa app like mentioned. I only see When this happens by Voice or Schedule. I am in Canada... maybe it is not updated here? Edit.... Found another thread where people who live in the UK cannot get working either. Believe this is US only for now. Edited October 6, 2018 by brians 1
lgilsenberg Posted October 6, 2018 Posted October 6, 2018 (edited) I'm hoping for a little guidance. I am having trouble using a variable to trigger a routine. Here is what I've done: 1 - Created a state variable in the ISY 2 - Added Variable in ISY Portal (Live Update is turned on) 3 - Changed Alexa Category of Variable to Motion Detector 4 - Discovered devices in Amazon Alexa 5 - Create routine in Alexa Mobile App 6 - Select "When this happens" 7 - Select Device 8 - I select the device I set up in ISY Portal I get an error saying "This device is not currently supported" I tried disabling the skill and re-enabling I tried forgetting the devices and re-discovering I'm not sure what to try now, any suggestions? Edited October 6, 2018 by lgilsenberg Clarified steps
bmercier Posted October 6, 2018 Author Posted October 6, 2018 1 hour ago, lgilsenberg said: I'm hoping for a little guidance. I am having trouble using a variable to trigger a routine. Here is what I've done: 1 - Created a state variable in the ISY 2 - Added Variable in ISY Portal (Live Update is turned on) 3 - Changed Alexa Category of Variable to Motion Detector 4 - Discovered devices in Amazon Alexa 5 - Create routine in Alexa Mobile App 6 - Select "When this happens" 7 - Select Device 8 - I select the device I set up in ISY Portal I get an error saying "This device is not currently supported" I tried disabling the skill and re-enabling I tried forgetting the devices and re-discovering I'm not sure what to try now, any suggestions? The error is shown when the chosen device is not a motion sensor or a contact sensor. This list of devices currently includes devices that are not yet supported, such as doorlocks. Choosing a doorlock would give you that message. Please double check that you are adding the correct device to your routine. If you just created or changed the type and rediscovered, refresh the Alexa list of devices by swiping down. Another troubleshooting tip, first go to Alexa Devices, locate the device, and make sure that you can see the motion sensor being detected/not detected, or contact sensor open/close. Benoit
TexMike Posted October 6, 2018 Posted October 6, 2018 Any chance for similar functionality with Google Home?
lgilsenberg Posted October 6, 2018 Posted October 6, 2018 29 minutes ago, bmercier said: The error is shown when the chosen device is not a motion sensor or a contact sensor. This list of devices currently includes devices that are not yet supported, such as doorlocks. Choosing a doorlock would give you that message. Please double check that you are adding the correct device to your routine. If you just created or changed the type and rediscovered, refresh the Alexa list of devices by swiping down. Another troubleshooting tip, first go to Alexa Devices, locate the device, and make sure that you can see the motion sensor being detected/not detected, or contact sensor open/close. Benoit I thought I could use a state variable as a sensor. I change the value of the variable and I can see the status of the detector changes in the alexa app. After changing the variable value, I can now use it in a routine. I don't know if that's a requirement before adding it to a routine or just my technology gremlins. Either way, thank you for the quick response.
Bumbershoot Posted October 6, 2018 Posted October 6, 2018 16 minutes ago, TexMike said: Any chance for similar functionality with Google Home? See this post in the Google Home forum.
RRoyceus Posted October 6, 2018 Posted October 6, 2018 On 10/3/2018 at 7:37 PM, bgrubb1 said: I can’t for the life of me get this to work. I have a state variable called alexa_test that I change via a hidden door sensor (also tried node status from my dsc panel) I watch the state of the variable and it changes correctly. I have a amazon routine set up multiple ways including seeing the device change in the Alexa app. It is enabled. Telling the app to play the spoken works correctly, but opening the door and seeing the state variable change does not result in Alexa saying the spoken. Am I missing a step ?. Any suggestions ? ...Barry I am trying to do the same thing, but I cannot get the hidden door sensor to change a state variable, only an integer variable. What are the steps you took to change the state variable?
bmercier Posted October 6, 2018 Author Posted October 6, 2018 2 minutes ago, lgilsenberg said: I thought I could use a state variable as a sensor. I change the value of the variable and I can see the status of the detector changes in the alexa app. After changing the variable value, I can now use it in a routine. I don't know if that's a requirement before adding it to a routine or just my technology gremlins. Either way, thank you for the quick response. No it's not a requirement to set the variable value. I guess this were the gremlins.
randyth Posted October 6, 2018 Posted October 6, 2018 This is an absolutely fantastic new feature. I got it working first try. Kudos to Benoit and UDI for making it all work so well. Very cool. -Randy 1
johnjces Posted October 6, 2018 Posted October 6, 2018 (edited) Excellent as I feel this is pretty cool and can be useful! I have a 2450 IOLink version .41 as a garage door controller... Magnetic reed switch to sense open and close and also use the IOLink relay to open and close the door via Agave. Works well. In my ISY Portal I only see the Relay. In my instance it is named 'Garage Door - Relay'. The sensor or magnetic reed switch is named in my ISY as 'Garage Door - Sensor' and I cannot see/find the sensor part in my portal. Just the relay portion. In setting up Alexa and the ISY Portal, I made the relay a sensor, since the sensor isn't shown, and set up the Alexa App Routines. Alexa announces very nicely the state of the relay when I use Agave or the console etc to open/close the door. When I use the garage door button which does not use the IOLink relay, she is quite mute. Why am I not able to see/use the sensor aspect of my IOLink in the ISY Portal and Alexa Routines? I did set a State Variable via a simple program and have it working like a charm. Still wondering why the IOLink Sensor does not show.. Thanks! John Edited October 6, 2018 by johnjces Continuing with trials and results
bmercier Posted October 6, 2018 Author Posted October 6, 2018 7 hours ago, johnjces said: Excellent as I feel this is pretty cool and can be useful! I have a 2450 IOLink version .41 as a garage door controller... Magnetic reed switch to sense open and close and also use the IOLink relay to open and close the door via Agave. Works well. In my ISY Portal I only see the Relay. In my instance it is named 'Garage Door - Relay'. The sensor or magnetic reed switch is named in my ISY as 'Garage Door - Sensor' and I cannot see/find the sensor part in my portal. Just the relay portion. In setting up Alexa and the ISY Portal, I made the relay a sensor, since the sensor isn't shown, and set up the Alexa App Routines. Alexa announces very nicely the state of the relay when I use Agave or the console etc to open/close the door. When I use the garage door button which does not use the IOLink relay, she is quite mute. Why am I not able to see/use the sensor aspect of my IOLink in the ISY Portal and Alexa Routines? Am I doing something wrong? OR, do I need to set a variable for the sensor? EDIT.. I tried this under variables as I had a state variable already set for the magnetic reed switchand the only option was a sensor in the ISY Portal. I selected that and then in Alexa App, when I selected the variable Alexa stated Device Not supported. Ugh.. Thanks! John Some sensors currently do not appear in the list of devices. This will be fixed tomorrow morning. I just tested with IOLinc sensors in dev. As for the variable, were you able to make it work? Other users have reported this error as well. What I have observed is that this message is shown when you select a device which is NOT an Alexa motion sensor or contact Sensor. If you chose a doorlock, you would see that message. I'm wondering if there is a bug somewhere. I have not seen this happening when done this way: Adding variable Setting the Alexa category to motion sensor Initiating a device discovery In the Alexa app, refreshing the devices (Swipe down) Creating the routine using this new motion sensor. If you change the Alexa category of a device, make sure to: Redo a device discovery In the Alexa app, refresh the devices (swipe down) When switching the alexa category say from light to motion sensor, the icon changes. But if you change from motion sensor to contact sensor, it's not as obvious because the icon is the same. Benoit
johnjces Posted October 6, 2018 Posted October 6, 2018 I did get it working just fine using a variable! And did so doing the steps you outlined.
markv58 Posted October 7, 2018 Posted October 7, 2018 Insteon hidden door open close sensors show doors open when closed in the Alexa app, can this be flipped?
bmercier Posted October 7, 2018 Author Posted October 7, 2018 9 minutes ago, markv58 said: Insteon hidden door open close sensors show doors open when closed in the Alexa app, can this be flipped? Hello, Could you check the output of: http://<your isy>/rest/nodes/<sensor address> ? What is the ST status when open? What is the ST status when close? Benoit
markv58 Posted October 7, 2018 Posted October 7, 2018 7 minutes ago, bmercier said: Hello, Could you check the output of: http://<your isy>/rest/nodes/<sensor address> ? What is the ST status when open? What is the ST status when close? Benoit 255 - open 0 - closed
Athlon Posted October 7, 2018 Posted October 7, 2018 This sounds fantastic, however I can't seem to figure it out. I go to Portal/Connectivity/Amazon Echo. Then I click 'Device'and choose one of my lights. When I change the Alexa Category to Contact Sensor and type 'the toaster light is on' in the Spoken field, I get 'This item already has a spoken' as an error. Where have I gone wrong?
RRoyceus Posted October 7, 2018 Posted October 7, 2018 I have my hidden door sensor working. When the state is changed, Alexa tells me the state. I would like to be able to ask Alexa the status of the sensor. I found an old post where you said you had to use the (old) skill, “Alexa, tell izzy to get the status of <door>“. With the skill being obsolete, is there any way to do it?
bmercier Posted October 7, 2018 Author Posted October 7, 2018 1 hour ago, Athlon said: This sounds fantastic, however I can't seem to figure it out. I go to Portal/Connectivity/Amazon Echo. Then I click 'Device'and choose one of my lights. When I change the Alexa Category to Contact Sensor and type 'the toaster light is on' in the Spoken field, I get 'This item already has a spoken' as an error. Where have I gone wrong? This means the ISY device you are adding has already been added. Once an ISY device has been added, it cannot be re-added under another spoken. Use the search at the top-right to search for your ISY device (Descrioption or address). Benoit
bmercier Posted October 7, 2018 Author Posted October 7, 2018 2 hours ago, markv58 said: 255 - open 0 - closed This is opposite of most contact sensor. I can propose the following work-arounds: Expose them as motion sensor: 255 (open) would be shown as detected (think of it as detected it is open). You can reverse the logic by using a program and state variable. If sensor==0, set state variable to 1, else 0. Expose that state variable as a contact sensor, with a Contact closed value=1. Benoit
bmercier Posted October 7, 2018 Author Posted October 7, 2018 45 minutes ago, RRoyceus said: I have my hidden door sensor working. When the state is changed, Alexa tells me the state. I would like to be able to ask Alexa the status of the sensor. I found an old post where you said you had to use the (old) skill, “Alexa, tell izzy to get the status of <door>“. With the skill being obsolete, is there any way to do it? Yes, if the device is a contact sensor. It can be queried this way: Alexa, is <contact sensor spoken> open? Alexa, is <contact sensor spoken> close? Some spokens are not easily recognized by Alexa. If you see she has trouble understanding that, try changing the spoken. Benoit
RRoyceus Posted October 7, 2018 Posted October 7, 2018 I have set up both a device and a state variable as an device \ contact. My variable spoken is “back door”. When I ask “Alexa is back door open”, she replies “back door does not support that”. The device has two spokens, Back Door Lock and back door status. Alexa replies that it does not support that
bmercier Posted October 7, 2018 Author Posted October 7, 2018 I have set up both a device and a state variable as an device \ contact. My variable spoken is “back door”. When I ask “Alexa is back door open”, she replies “back door does not support that”. The device has two spokens, Back Door Lock and back door status. Alexa replies that it does not support that Please try a different a different naming. Alexa is a bit picky.Benoit Sent from my iPhone using Tapatalk
Recommended Posts