ahwman

Hey guys, I think I may have made some progress with IFTTT and the Maker channel, however I need someone smarter than myself to confirm. If I try using the ISY portal link base URL (Non-URL Encoded) along with the rest command in a browser window, i.e. "https://email:password@my.isy.io/ISYURL/rest/programs/00A7/run, it simply loads a blank page and the request fails. I'm certain this is because of the "@" in our ISY user name. Now if I simply replace the "@" in the ISY username email address with "%40", it works perfectly in every browser I've tried. I'm still getting an error when attempting this on the Maker channel, however it's not an authentication error but rather a timeout error which perhaps is due to my configuration being wrong. Would someone else be willing to play around with this to see if we can get any farther? Thanks, Chuck

Michel has suggested to me to purchase a certificate which doesn't use intermediaries. Do you think this would work as a temporary work around with IFTTT/Maker channel until UDI supports the correct implementation? If so, where does one buy such a certificate? Chuck

I got a confirmation email back from Michel that the ISY doesn't support intermediate certificates so we have our answer. That said, it looks like I wasted my money on an SSL certificate as I have no use for it outside of IFTTT/Maker channel. The only option I see is to use a proxy server as some are doing, however that just creates a whole new level of complication, so I guess I'll just have to wait until the ISY skill is released and hope that UDI will soon support IFTTT natively... Chuck

I came across this post from Michel from UDI and unless something has changed since this post, it seems we have our answer for now. The link to this thread is located at: http://forum.universal-devices.com/topic/14033-importing-certificate/ "Hi Steven, Unfortunately not. At the moment, intermediate certificates must be installed in the browser. With kind regards, Michel"

Thanks, I have a Mac and PC but at this point I think I'll just wait until we hear back from UDI on this issue...

Thanks for all of your diligent efforts Michael. That said, this is somewhat new to me so I'm learning as I go. Where did you issue the commands to create the .pem file as the directions I followed suggest that you could simply paste each of the certs into one text file which I tried and renamed .pem but when I tried to import it using the Import Cert. it fails. So I ended up just pasting it using the Recieve Cert. button. Is the .pem creation done on your web server or a PC/Mac? Also, what option did you use to import it into the ISY? Thanks, I'll direct support to this link and hopefully we'll get a response...

Thanks for the reply, I've tried as you suggest by combining the root, intermediate and signed cert into a text file, then copying and pasting it into the ISY which it accepts. However, I'm still getting an error when using the Maker channel in IFTTT "Action skipped - Unable to make web request: Error: unable to verify the first certificate". Chuck

Hello, I purchased an SSL certificate from Alpha SSL and was able to copy and paste the SSL certificate into my ISY994, however the directions state that I must also install an intermediate certificate and don't know how to do so. Can anyone help? Thanks!

I believe you're talking about profiles within the MobiLinc app itself. I was referring to the ISY, as the MobiLinc Connect portal and ISY portal cannot coexist. It's currently a one or the other proposition...

Gottcha. I guess there's no perfect solution. MobiLinc connect is very fast and reliable, unfortunately it can't be used alongside the ISY portal. Maybe that will change in the future...

I understand that, however I don't understand the need to have a local connection profile as well as a remote connection profile. In other words, why not use only the SSL connection scheme both locally and remotely?

Strange, I would think that once it makes a connection it should work as normal. Maybe this would be a good question to ask Wes. The only reason I would like to get this working is because I'm having connection issues with MobiLinc since v4.5 and sometimes my geofence doesn't trigger correctly. Also, I don't know why you would have to create a local and away profile, as I would think this would work both in and outside of your LAN. Chuck

Thanks Michael, I was able to get MobiLinc to connect using the ISY portal, unfortunately it gets stuck updating at "Parsing Address: 22253 Details". Any idea why it's hanging up? Thanks again, Chuck

Xathros, I would also like to use the ISY portal login with MobiLinc as I've been having connection issues with SSL in the newest version of MobiLinc but can't figure it out. Would you be so kind as to provide the connection settings for MobiLinc in conjunction with the ISY portal? Thanks so much! Chuck

Thanks so much. Is it possible to use the ISY portal login for MobiLinc as I've been having connection issues over SSL with the latest version of MobiLinc and would like to test the ISY portal as an alternate method... Thanks, Chuck

Michel, I just purchased the ISY portal a few minutes ago and this exact thing happened to me as well. Upon rebooting my ISY, the MobiLinc portal is now gone. I'm not currently using MobiLinc Connect though I still use MobiLinc via direct IP. Should I send you my UUID as well? Also, where are the directions to configure the portal? Thanks, Chuck

Thanks so much for the explanation as that makes perfect sense. I already have a domain name, however purchasing a trusted SSL certificate probably doesn't make sense as I'll be purchasing the ISY portal once the Echo skill is approved. That said, is it possible to use the ISY portal right now with Maker? Thanks again

Just playing around to learn and kill some time...

So Maker will not send standard http requests? That seems a bit odd to me but would explain the reason it's not working. I don't see any errors in the recipe logs...

Correct, I'm just waiting until the new Echo skill is approved before purchasing...

I'm not sure I understand the question, however using the following link works both inside/outside my network. http://username:password@rest/programs/00A6/run

That's a bummer. Was hoping to at least play around until the portal is available. That's strange that it wouldn't work using http from the Maker app as it works fine outside of my LAN using http. That said, I don't see any errors in the Maker log files for this recipe... Thanks, Chuck

Would someone please help? I've set up a test trigger using IFTTT and then Maker channel. I know that the URL is working correctly as I've tested it several times outside of my network and triggers perfectly each time, however it doesn't seem to be working when triggered from the maker channel. I have attached a screenshot of my configuration (changed user/password of course) and I assume I'm missing something. I appreciate any help! Chuck

That's wonderful when companies take an active interest in their customers and partners which is how it should be. FYI, I just received my two Echo's yesterday and I have to say I am absolutely stunned by how well this product works. Every element of the Echo has exceeded my expectations. After years of working with HA, I believe this will be a major game changer especially when incorporated with the power of the ISY. On a side note, I installed some skills just to play around and get better aquatinted with how they work. That said, I noticed that you can actually open an app and once inside simply issue commands without invoking the skill (i.e. "Alexa, open the Bible app" followed by "Alexa read the scripture of the day") until leaving the app. Will the ISY skill function this way? As I was thinking, it sure would be nice and more natural to be able to say, "Pause DVR" instead of "Alexa, tell Izzy to run Pause DVR"... So excited for final approval of the ISY skill! Chuck

Thanks for the update Michel. It sounds like it's a pretty lengthy and thorough approval process. Hopefully soon we'll be commanding our homes just like the scifi dreams of our childhood... Chuck