Jump to content

Google Home & Scenes Issue


Recommended Posts

Posted

Hi,

We've been switching over from Alexa to Google Home this weekend and everything has been going well until we got to scenes.  When I add a scene in the ISY portal to google home, it does not show up in the google home app.  If I change the "google home category" in the portal from scene to switch or light, it will show up in the google home app, but does not respond.

What am I missing?

Thanks.

Posted
Hi,

We've been switching over from Alexa to Google Home this weekend and everything has been going well until we got to scenes.  When I add a scene in the ISY portal to google home, it does not show up in the google home app.  If I change the "google home category" in the portal from scene to switch or light, it will show up in the google home app, but does not respond.

What am I missing?

Thanks.

 

 

 

You add the ISY scene as a light in Google home.

 

Sent from my Pixel 3 XL using Tapatalk

 

 

Just know that only on or off is supported. Direct Dim commands are not supported by Insteon scenes (and therefore cannot be called via Google Home or Alexa for that matter)

  • Like 3
  • 2 months later...
Posted
21 minutes ago, Clara Craighead said:

Google Home is my favourite helper!

photo_2020-07-09 16.20.44.jpeg

Did you link Google Home to your ISY ?

Posted

The ISY voice commands, using Google Home or Alexa, are pretty amazing.  Some are working on getting GH or Alexa actually to "speak"  on  ISY events and that would be even more amazing.

Posted

Yes. We use Alexa boxes to control our lights, TVs, Roku sticks, and say things like "Both garage doors are closed", "Garage door one is open", "You have a low battery on a leak/motion detector", "The dryer has stopped". etc..

You will need the ISY Portal to make this easy. It acts like a translations table between ISY and the GH or Alexa devices. I don't define anything as a scene, only switches.

Posted
58 minutes ago, larryllix said:

say things like "Both garage doors are closed", "Garage door one is open", "You have a low battery on a leak/motion detector", "The dryer has stopped". etc..

How do you do that ?

Posted
34 minutes ago, asbril said:

How do you do that ?

  • Define a STATE variable with a nice name like $sSayBothGDoorsClosed,   Save!
  • In an ISY program insert lines $sSayBothGDoorsClosed = 1, Wait 30 seconds, $sSayBothGDoorsClosed = 0
  • In ISY Portal, in define Alexa table,  find that variable $sSayBothGDoorsClosed and define as a Motion detector, make On from value = 1
  • Say "Alexa discover" to make it appear in Alexa app.
  • In Alexa app on a cell phone (Win app does not allow Routine editing) define a Routine using sSayBothGDoorsClosed as a trigger,
     make the output a custom vocal and add "Both garage doors are closed"
  • Routines can take a while to be effective on Amazon sometimes. Also  Amazon may block Routine triggers faster than 30 seconds = don't use on fast changing events.

Asbril...close your eyes, bang your fists, stamp your feet, sip a brandy, and then create a State variable. It will not hurt one bit and you'll like it!! :)
Let me know if you get stuck!
Then we are going to chant "Asbril...Variable King!"   "Asbril...Variable King!"

  • Like 1
Posted
1 hour ago, larryllix said:
  • Define a STATE variable with a nice name like $sSayBothGDoorsClosed,   Save!
  • In an ISY program insert lines $sSayBothGDoorsClosed = 1, Wait 30 seconds, $sSayBothGDoorsClosed = 0
  • In ISY Portal, in define Alexa table,  find that variable $sSayBothGDoorsClosed and define as a Motion detector, make On from value = 1
  • Say "Alexa discover" to make it appear in Alexa app.
  • In Alexa app on a cell phone (Win app does not allow Routine editing) define a Routine using sSayBothGDoorsClosed as a trigger,
     make the output a custom vocal and add "Both garage doors are closed"
  • Routines can take a while to be effective on Amazon sometimes. Also  Amazon may block Routine triggers faster than 30 seconds = don't use on fast changing events.

Asbril...close your eyes, bang your fists, stamp your feet, sip a brandy, and then create a State variable. It will not hurt one bit and you'll like it!! :)
Let me know if you get stuck!
Then we are going to chant "Asbril...Variable King!"   "Asbril...Variable King!"

Now you have given me challenge and potentially a new title :-)

That is my task for this weekend

  • Like 1
Posted
40 minutes ago, asbril said:

Now you have given me challenge and potentially a new title :-)

That is my task for this weekend

Didn't we already have this discussion? You got this

Posted
1 minute ago, lilyoyo1 said:

Didn't we already have this discussion? You got this

You are too kind.... but I have a mental block when it comes to variables.  Larryllix is my personal psychiatrist for this

 

  • Haha 1
Posted
Just now, asbril said:

You are too kind.... but I have a mental block when it comes to variables.  Larryllix is my personal psychiatrist for this

 

Asbril, I'm up to 58 integer and 63 state variables.  Timers, counters, averages, program triggers, etc., all based on the help and examples from the folks on this forum (thank you all).

 If I can do it you can do it....!

  • Like 2
Posted (edited)
1 hour ago, asbril said:

Now you have given me challenge and potentially a new title :-)

That is my task for this weekend

After you create the variable and create the link in ISY Portal you can see it in the Alexa app also. That should give you the confidence to keep going and you are almost done.

It must be done in order from the ISY end, variable==> ISY Portal ==> Alexa App ==> Alexa app Routine ==> pick a speaker or All speakers.

I was using All speakers for a while but the echo sound can make it unintelligible. Now I use a few key speakers only.

Edited by larryllix
Posted

I did the setup but I have to wait till I have the home for myself as my wife has no patience for me trying out my gadgets. I only have 2 Alexa speakers and the rest is Google Home.

Posted (edited)
13 minutes ago, asbril said:

I did the setup but I have to wait till I have the home for myself as my wife has no patience for me trying out my gadgets. I only have 2 Alexa speakers and the rest is Google Home.

There won't be any mechanical gadgets or lights going on and off. It will be one speaker you test it on making sounds. Keep it close and the volume down.

I would think GH would have the equivalent of Alexa Routines, but I can't confirm. My 3-4 units are all shut down now.

Remember in any good computer programming, your device, variable and other thing naming is your documentation you may need two years from now. Use text name length generously. I like "camel case" style eg: $sSayGarageDoorsClosed. When you use it again a year from now there is no doubt what it does.

Edited by larryllix
  • Thanks 1
Posted
2 hours ago, larryllix said:

There won't be any mechanical gadgets or lights going on and off. It will be one speaker you test it on making sounds. Keep it close and the volume down.

I would think GH would have the equivalent of Alexa Routines, but I can't confirm. My 3-4 units are all shut down now.

Remember in any good computer programming, your device, variable and other thing naming is your documentation you may need two years from now. Use text name length generously. I like "camel case" style eg: $sSayGarageDoorsClosed. When you use it again a year from now there is no doubt what it does.

The good news......... It works perfectly. Thanks Dr. Larry.

The bad news......... Even with using a variable in this setup, I still don't get it. My current thinking is that variables are actually very simple and I may be trying to understand something more complicated. Maybe I am just too smart for this world.

  • Haha 1
Posted
2 hours ago, asbril said:

The good news......... It works perfectly. Thanks Dr. Larry.

The bad news......... Even with using a variable in this setup, I still don't get it. My current thinking is that variables are actually very simple and I may be trying to understand something more complicated. Maybe I am just too smart for this world.

Excellent. Just think of the memory on your calculator with a some sneaky mouse inside that watches for a piece of cheese. When you feed it, it squeaks out the phrase you taught it!!!

ISY Forever!

ASBRIL! VARIABLE KING!! 

ASBRIL! VARIABLE KING!! 

ASBRIL! VARIABLE KING!! 

  • Like 1
Posted (edited)
19 hours ago, larryllix said:
  • Define a STATE variable with a nice name like $sSayBothGDoorsClosed,   Save!
  • In an ISY program insert lines $sSayBothGDoorsClosed = 1, Wait 30 seconds, $sSayBothGDoorsClosed = 0
  • In ISY Portal, in define Alexa table,  find that variable $sSayBothGDoorsClosed and define as a Motion detector, make On from value = 1
  • Say "Alexa discover" to make it appear in Alexa app.
  • In Alexa app on a cell phone (Win app does not allow Routine editing) define a Routine using sSayBothGDoorsClosed as a trigger,
     make the output a custom vocal and add "Both garage doors are closed"
  • Routines can take a while to be effective on Amazon sometimes. Also  Amazon may block Routine triggers faster than 30 seconds = don't use on fast changing events.

Asbril...close your eyes, bang your fists, stamp your feet, sip a brandy, and then create a State variable. It will not hurt one bit and you'll like it!! :)
Let me know if you get stuck!
Then we are going to chant "Asbril...Variable King!"   "Asbril...Variable King!"

The device added to alexa must not necessarily be a variable.  I trigger alexa voice routines from those things that I add to alexa as a alexa category "device/sensor".   In my case, I have added several of the insteon door sensors and IOLinc sensors to alexa and use those to trigger voice announcements.  I don't know the limits of the devices that can be added as "sensors", however.

Edited by oberkc
Posted
4 hours ago, oberkc said:

The device added to alexa must not necessarily be a variable

oberkc, you must have been reading my mind as I was just thinking about this earlier this morning. I will experiment later today. Larryllix is smart so there must be a reason to use a variable, but I'd like to understand.

Posted
52 minutes ago, asbril said:

oberkc, you must have been reading my mind as I was just thinking about this earlier this morning. I will experiment later today. Larryllix is smart so there must be a reason to use a variable, but I'd like to understand.

@oberkc IIRC, we were originally told we had to only use a State variable to accomplish this. However maybe the emphasis was on "State" and not "variable".

I cannot think of one application where I would want a raw sensing device to produce a spoken response, though. These inputs to Alexa routines are sensitive. If you do not observe the 30 second rule they will just ignore your requests. Programs and devices may not obey those rules nicely, and cause amazon to avoid talking.

eg. If I created a routine using the status of my SynchroLinc on my dryer, it would attempt to say "The dryer has finished" every time my wife opened the dryer door. When loading the dryer with the door open, that would be a false statement.

eg. When one garage door opens I report which door has opened. When one garage door is closed I report nothing unless they are both closed. That takes ISY logic, but I could use an additional program to trigger a vocal Routine, I suppose.

Another thing that should be noted: Many times when amazon or ISY Portal makes an upgrade the connection between ISY Portal and amazon/GH can be broken. When you disable the account connection and re-enable the connection to re-synch devices, all your Alexa Routines will be forgotten as the trigger events did not exist for those few fleeting seconds. You must start from the beginning, rebuilding them again.

 

Posted
1 hour ago, larryllix said:

These inputs to Alexa routines are sensitive. If you do not observe the 30 second rule they will just ignore your requests.

Can you explain  in simple terms why the 30 seconds are necessary and same for (in Program) changing variable back to 0 ?

Posted (edited)
3 hours ago, larryllix said:

@oberkc IIRC, we were originally told we had to only use a State variable to accomplish this. However maybe the emphasis was on "State" and not "variable".

I cannot think of one application where I would want a raw sensing device to produce a spoken response, though. These inputs to Alexa routines are sensitive. If you do not observe the 30 second rule they will just ignore your requests. Programs and devices may not obey those rules nicely, and cause amazon to avoid talking.

eg. If I created a routine using the status of my SynchroLinc on my dryer, it would attempt to say "The dryer has finished" every time my wife opened the dryer door. When loading the dryer with the door open, that would be a false statement.

eg. When one garage door opens I report which door has opened. When one garage door is closed I report nothing unless they are both closed. That takes ISY logic, but I could use an additional program to trigger a vocal Routine, I suppose.

Another thing that should be noted: Many times when amazon or ISY Portal makes an upgrade the connection between ISY Portal and amazon/GH can be broken. When you disable the account connection and re-enable the connection to re-synch devices, all your Alexa Routines will be forgotten as the trigger events did not exist for those few fleeting seconds. You must start from the beginning, rebuilding them again.

 

I don't know anything about 30-second rules or inputs to alexa being sensitive or broken connections (yet, but hopefully never).  All I can say is that I wanted alexa to announce when doors were being opened and I used the appropriate door sensors as a trigger for verbal announcements.  Works like a champ.  Has not broken anything yet.  And....no variables (for those allergic to them).  I do not announce when doors are closed...the alexa trigger on the routine is sufficient enough to limit those occurrences.  I trigger the routine only when the sensor is "open".  I would have to create a second routine to announce when doors are closed.

 

Edited by oberkc
  • Like 1
Posted (edited)

Alexa debounces sensor values over the course of 30 seconds. In other words, once Alexa sees the first sensor value change, it ignores all changes to the same sensor until 30 seconds have elapsed. "Sensor" here is anything that can be used as a trigger in an Alexa routine.

For example, let's say you have two routines for your mailbox.  The sensor is an Elk zone dry contact that is closed when the mailbox door is closed.

  1.  When mailbox sensor opens, say "Mailbox opened"
  2. When mailbox sensor closes, say "Mailbox closed"
  • Mail carrier opens the mailbox, drops the mail, and closes the mailbox after 15 seconds. You'll hear Alexa announcing "Mailbox opened", and after 30 seconds you'll hear "Mailbox closed".
  • Mail carrier opens the mailbox, drops the mail, and closes the mailbox after 45 seconds. You'll hear Alexa announcing "Mailbox opened", and after 45 seconds you'll hear "Mailbox closed".
  • Mail carrier opens the mailbox, drops the mail, and closes the mailbox after 10 seconds. Then the carrier opens the mailbox again after 5 seconds for 10 seconds. You'll hear Alexa announcing "Mailbox opened", and after 30 seconds you'll hear "Mailbox closed". The second set of opening and closing is not triggering the routines.
Edited by jfai
Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Who's Online (See full list)

  • Forum Statistics

    • Total Topics
      37k
    • Total Posts
      371.3k
×
×
  • Create New...