rvandersteen Posted August 30, 2017 Posted August 30, 2017 I'm considering purchasing a Google Home and when I read up on how to get it connected, it looks like I need to purchase and install the ISY Portal. I currently do not use this, nor Mobilinc Connect. Instead, I have everything forwarded through my router. I do use Mobilinc on my phone. I just have the app pointed directly at the ISY. 1. If I purchase the Google Home, is my only option to purchase the ISY Portal to get it integrated with my ISY? 2. Do I still need to leave my port forwarding set up in place so that I can connect my mobilinc app to my ISY or is there some way to run this through the ISY Portal. Thanks in advance, Rob Quote
rvandersteen Posted August 30, 2017 Author Posted August 30, 2017 (edited) Looks like the answer to #2 is No. Mobilinc can be set up with the ISY portal. I would still like a confirmation on #1. Edited August 30, 2017 by rvandersteen Quote
asbril Posted August 30, 2017 Posted August 30, 2017 I am not sure to fully understand your question but to the best of my knowledge you DO need ISY Portal to communicate with Google Home, Alexa and IFTTT. I use all three with ISY Portal and I also use Mobilinc on my Iphone, being it with different settings to connect to ISY. BTW the GH commands to ISY work 80 pct of the time. Quote
apostolakisl Posted August 31, 2017 Posted August 31, 2017 (edited) No, you do not. IFTTT can be used for google home and alexa. Edited August 31, 2017 by apostolakisl Quote
KeviNH Posted September 1, 2017 Posted September 1, 2017 No, you do not. IFTTT can be used for google home and alexa. Is there a thread showing how to use IFTTT with ISY994 without ISY Portal? Quote
MWareman Posted September 1, 2017 Posted September 1, 2017 (edited) Is there a thread showing how to use IFTTT with ISY994 without ISY Portal?You may need to locate separate threads... there are several steps involved and it's not for the non-technical amongst us... From the top of my head.... You need a router capable of registering a dynamic dns name to your home IP address. You need a domain name with a cname record pointing to your ddns name. You need a trusted SSL certificate using the cname correctly installed onto your ISY. (It's rare to find certificate authorities that will issue certificates to ddns names, and the cname trick works around this) You need to port forward tcp port 443 to your ISY. You need to NOT be using an ISP that uses cgnat. Then, you can configure webhooks on IFTTT that can trigger scenes, programs and devices (refer to the API documentation n the wiki). You will need to trust IFTTT with the password to your ISY. Michael. Edited September 1, 2017 by MWareman Quote
apostolakisl Posted September 1, 2017 Posted September 1, 2017 For me: 1) I have a dynamic dns already set up through no-ip. 2) I have about 10 devices in my house that will update my dynamic dns. I'm using my foscam cameras since they natively support no-ip. My Elk also natively supports no-ip, my router supports others, but not no-ip. 3) I have a self-signed security certificate on my ISY. The wiki has instructions on installing that. Even if you choose to get portal, there is a good chance you want dynamic dns to get into your home network for cameras, or computer access, or whatever. You could forgo the dynamic dns if your ISP never changes your IP number. Many never do unless you get a new gateway/modem. But then you need to remember that number. It's easier to remember a name of your choosing. Like http://joe-blow.no-ip.biz The above 3 I have had for a long time since this is how I was able to access my ISY long before portal existed. At that point, it is just a matter of setting up webhooks on IFTTT. You need to go to the wiki on REST commands and cut and paste in whatever commands you want. Quote
MWareman Posted September 1, 2017 Posted September 1, 2017 IFTTT cannot call an API with a self signed certificate. It *must* be a paid, trusted certificate (no, cacert or letsencrypt will not work - I've tried them). Quote
apostolakisl Posted September 1, 2017 Posted September 1, 2017 (edited) IFTTT cannot call an API with a self signed certificate. It *must* be a paid, trusted certificate (no, cacert or letsencrypt will not work - I've tried them). Hmmm. My experience is not consistent with that. I do not have a paid SSL and I have both google home and echo doing webhooks no prob. EDIT: In fact, I have 2 ISY's both using IFTTT over https: using self-signed certs. example of a webhook below. https://admin:*********@*****.no-ip.biz/rest/nodes/43 9E 4 1/cmd/DOF Edited September 1, 2017 by apostolakisl Quote
MWareman Posted September 1, 2017 Posted September 1, 2017 Hmmm. My experience is not consistent with that. I do not have a paid SSL and I have both google home and echo doing webhooks no prob. EDIT: In fact, I have 2 ISY's both using IFTTT over https: using self-signed certs. Interesting. Maybe something changed - it's been quite a while since I first tested this.... they used to r next SSL connections ey were not able to establish trust to. I guess that probably changed... Quote
apostolakisl Posted September 1, 2017 Posted September 1, 2017 Interesting. Maybe something changed - it's been quite a while since I first tested this.... they used to r next SSL connections ey were not able to establish trust to. I guess that probably changed... Not sure when you tried. But I purchased my first echo in Dec 2016 and set up my first IFTTT webhook shortly after arrival. It worked then and has continued to work since. 2 Quote
MWareman Posted September 2, 2017 Posted September 2, 2017 Definitely before then. It was right when the Maker channel first showed up on IFTTT. 2014-ish I think... Quote
lilyoyo1 Posted September 3, 2017 Posted September 3, 2017 Either way, 50 bucks for 2 years access is well worth the time and effort to make it work. That's less than the cost of dinner out 3 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.