Jump to content

Control Google Home device


pikach

Recommended Posts

Posted

Hi, im an old ISY user but new to portal / GH. 

Was just wondering is it possible to control a google home device using ISY.

 

I am trying to arm my alarm.com system using a variable and theres no direct IFTTT or api integration for them, but they do have access to be armed thru GH.

Would this be possible? or the portal only goes 1 way,  GH to trigger ISY commands and not vice versa.

 

Thanks 

Posted
1 hour ago, pikach said:

Hi, im an old ISY user but new to portal / GH. 

Was just wondering is it possible to control a google home device using ISY.

 

I am trying to arm my alarm.com system using a variable and theres no direct IFTTT or api integration for them, but they do have access to be armed thru GH.

Would this be possible? or the portal only goes 1 way,  GH to trigger ISY commands and not vice versa.

 

Thanks 

The ISY Portal is partially bi-directional. I do not have any active GH devices anymore, but many Alexa devices. Here is how it works with Alexa.

Create a State variable for control.
In ISY Portal use that State variable to create a pseudo MS
In ISY Portal define what variable value will be shown as ON and Off
In Alexa mobile app define a Routine using the pseudo MS as a trigger and the resultant as whatever you want it to do, voice output, device on/off etc..

I believe GH also has Routines. I hope this helps.

Posted

I am also more an Alexa user, but do have a single google home device.  As near as I can tell, Google Home routines are triggered exclusively by voice or time.  I do not see a trigger based upon a device or variable.

  • Like 1
Posted
2 hours ago, oberkc said:

I am also more an Alexa user, but do have a single google home device.  As near as I can tell, Google Home routines are triggered exclusively by voice or time.  I do not see a trigger based upon a device or variable.

I have many GH devices but if they do not get an IP address properly,  they create their own WiFi that clobbers my routers on the same channels.

  • 2 weeks later...
Posted

Since a few days I have a weird situation on both my Alexa and Google Home. I CAN control my ISY devices from the Alexa APP and from the Google Home APP on my phone. However,  when I issue a voice command I get a message like "It looks like Universal Devices is not available right now",  or something similar....

Posted
5 hours ago, asbril said:

Since a few days I have a weird situation on both my Alexa and Google Home. I CAN control my ISY devices from the Alexa APP and from the Google Home APP on my phone. However,  when I issue a voice command I get a message like "It looks like Universal Devices is not available right now",  or something similar....

I get that very occasionally on my Alexa units.  I think it meant "I'm sorry, all our agents are busy filling online orders right now. Please try again later".

Do you get it on GH also?

Posted
16 minutes ago, larryllix said:

I get that very occasionally on my Alexa units.  I think it meant "I'm sorry, all our agents are busy filling online orders right now. Please try again later".

Do you get it on GH also?

Yes same on Alexa and Google Home, and I find it very weird as  there is no issue controlling the devices in the alexa and GH Apps on my phone

Posted
50 minutes ago, asbril said:

Yes same on Alexa and Google Home, and I find it very weird as  there is no issue controlling the devices in the alexa and GH Apps on my phone

Perhaps ISY Portal is over busy with handing out signals to connected cloud services. Is there any time of day pattern you can determine?

Posted
4 minutes ago, larryllix said:

Perhaps ISY Portal is over busy with handing out signals to connected cloud services. Is there any time of day pattern you can determine?

It has been constant for a couple of days. I have opened a ticket with UDI.

  • Like 1
Posted
2 hours ago, Michel Kohanim said:

@asbril,

Benoit looked at your logs and his conclusion is: if both Alexa and Google Home apps work and if ISY Portal works, then - and most probably - you are using different accounts.

With kind regards,

Michel

Thanks Michel,

My Portal account is hotmail and I use the same for Alexa. My Google Home is a gmail account. This has been working for a long time and I am not aware of having made any change.

Posted (edited)
1 hour ago, asbril said:

Thanks Michel,

My Portal account is hotmail and I use the same for Alexa. My Google Home is a gmail account. This has been working for a long time and I am not aware of having made any change.

Progress.....  I found out that 2 of my GH devices had gone to  'local device'  in my GH account.  After factory reset and new set up, GH now works.  For Alexa,  I found out that issue is only with my automatic curtains.  All other devices can now again be controlled with voice control.  I saw that, however I set up the automatic curtains in Portal (used to be either "Switch" or "Light") these now revert automatically to "Contact Sensor" and now Alexa either responds nothing on my voice command, or says something like it can not communicate with  "master curtains".

p.s. the curtains are controlled through Mimo Lite devices

Edited by asbril
  • Like 1
Posted
5 hours ago, asbril said:

Progress.....  I found out that 2 of my GH devices had gone to  'local device'  in my GH account.  After factory reset and new set up, GH now works.  For Alexa,  I found out that issue is only with my automatic curtains.  All other devices can now again be controlled with voice control.  I saw that, however I set up the automatic curtains in Portal (used to be either "Switch" or "Light") these now revert automatically to "Contact Sensor" and now Alexa either responds nothing on my voice command, or says something like it can not communicate with  "master curtains".

p.s. the curtains are controlled through Mimo Lite devices

I resolved both Alexa and GH issues.

Google Home :

Why two of my GH devices  left  "Home"  in my GH account and became "Local", I have no idea. But when I did a factory reset and added both back to "Home", the issue was resolved.

Alexa :

I also still don't know why my automatic curtains (I have 2 of these) stopped working with Alexa voice command. 

Trying to resolve the issue I had deleted both curtains (in fact Mimo Lites) from Alexa Connectivity in ISY Portal and added them again. But the voice command "Open Curtains 1"  still did not work. Then it just occurred to me to try "Turn OFF curtains 1"  and when that did work, I realized that the Alexa Routine that I had created originally ( "Open Curtains 1" =. "Turn Curtains 1 OFF" )  stopped working when I deleted the curtains from Alexa Connectivity in ISY Portal. I re-did the Alexa Routines and voila, the voice commands work again.

Both the GH and Alexa issues were in fact simple to resolve, but what probably confused me is that the unrelated Alexa and GH issues happened (at least in my mind) at the same time and therefore put me on the wrong path.

Posted (edited)
8 minutes ago, Michel Kohanim said:

@asbril,

Do you still have to use Routines even though you can use Raise Lower category?

With kind regards,
Michel

Michel,  I tried this even though the curtains open/close side ways. But the issue is that whatever option I choose and save (light, switch, outlet, etc) after discover in Alexa, the category defaults back to contact sensor. The routine works perfectly, so no longer any issue for me.

Edited by asbril
Posted
20 minutes ago, asbril said:

Michel,  I tried this even though the curtains open/close side ways. But the issue is that whatever option I choose and save (light, switch, outlet, etc) after discover in Alexa, the category defaults back to contact sensor. The routine works perfectly, so no longer any issue for me.

When you change your device to set/lower/raise and save, Does the spoken still appear as set/lower/raise in ISY Portal?

When you say "after discovery", does it show as a contact sensor in Alexa, or in ISY Portal?

The discovery does not change what you have on ISY Portal, so not sure what is happening here.

Posted
3 minutes ago, bmercier said:

When you change your device to set/lower/raise and save, Does the spoken still appear as set/lower/raise in ISY Portal?

When you say "after discovery", does it show as a contact sensor in Alexa, or in ISY Portal?

The discovery does not change what you have on ISY Portal, so not sure what is happening here.

I tried again,  in Portal-Connectitivity-Alexa I changed the curtains to the open-close syntax and saved. I opened again and it still showed the open-close syntax. This time I logged out from Portal and logged in again, and the curtains had reverted back to contact sensor. As such it is indeed not because of discover in Alexa but something in Portal.

I hope this is helpful

Posted
34 minutes ago, asbril said:

I tried again,  in Portal-Connectitivity-Alexa I changed the curtains to the open-close syntax and saved. I opened again and it still showed the open-close syntax. This time I logged out from Portal and logged in again, and the curtains had reverted back to contact sensor. As such it is indeed not because of discover in Alexa but something in Portal.

I hope this is helpful

Which browser are you using?

Could you try the same with Chrome as a test?

Benoit

Posted
2 minutes ago, bmercier said:

Which browser are you using?

Could you try the same with Chrome as a test?

Benoit

Benoit,

I was using Chrome and just tried with Safari. Same result.

Posted
1 hour ago, asbril said:

Benoit,

I was using Chrome and just tried with Safari. Same result.

Chrome on iOS, Mac or Windows?

Can you try on Windows?

Benoit

Posted
23 minutes ago, bmercier said:

Chrome on iOS, Mac or Windows?

Can you try on Windows?

Benoit

I had already used Chrome on both my Windows 10 and on my Mac. Same result. Just now I tried on Windows 10 with Edge browser and same result.

Posted
2 hours ago, asbril said:

Benoit

ci-joint la video

 

The video is a bit shaking but it shows my steps.

IMG_3469.MOV

Thanks for the video. 

I could not believe it.

Now I can reproduce it. It happens only if you edit and save without changing the Alexa category. Will fix that.

Benoit

  • Like 1
Guest
This topic is now closed to further replies.

×
×
  • Create New...