Mobile Integrated Solutions

+1. This would be a huge feature, would really open up possibilities for the whole ecosystem. It would turn the phone into a much more powerful control device for HA systems, especially as more and more phones are getting NFC with programmable action chips. Also, this would open up more possibilities for IFTTT automation, which the new competitor WeMo device is doing.

I'd like to throw in my vote for this as well. I'd even pay more to have Tasker integration available.

Thanks everyone. Due to the interest we are now looking into this. We'll update this thread with more information as we look into what it will take to integrate with Tasker.

Wes

IFTTT integration PPLLLEEAASEEE!!!

I would give my first child for this.

What are you trying to do with IFTTT and MobiLinc? Seems to me we need/want ISY/IFTTT integration - as well as Tasker/IFTTT. To that end, I've been spending cycles trying to convince IFTTT to implement REST triggers and actions (a 'REST API' channel) - as this (for me) would complete the picture of automation integration. Could get everything talking then. Until then, I've only come up with partial solutions.

It's important t note though that IFTTT is about talking between two web services - MobiLinc on a device does not present such an interface.

Got me thinking though - how about this (Wes) as a feature suggestion. Providing an API to MobiLinc connect and integrating it with IFTTT as a fast trigger and action channel?

Since Connect sees ISY events thru the subscription (device and scene commands, variables, programs etc) and can issue commands to the ISY - it could operate as a fast trigger on IFTTT (the 'If This') as well as an action ('Then That').

I suspect you'll get a lot of people signing up for connect for a feature like this that might not have bothered before because they have the necessary networking knowledge to connect without needing it.

Michael.

Hi Michael,

You are correct, in order to do IFTTT, we'd have to create that interface at the MobiLinc Connect layer and issue a public API that could be used by IFTTT. As you pointed out, I'm not sure if the IFTTT folks have REST capability yet or not to call out to another service like us.

Wes

Well - it would not have to be a 'public' API per-se. A private created-just-for-the-purpose API just for IFTTT to call would work for them I'm sure.

Of course - this takes work on both ends. IFTTT has a page to get in touch to begin the process. https://ifttt.com/platform. I'll take this moment to encourage you to get in touch with them - if you also feel a 'connection' would be valuable.

They DO have an API - but only make it available to partners it seems. I think you have to get in touch with them to begin.

Michael.

Hi Michael,

We've actually already reached out to them and are waiting for feedback.

Wes

Awesome! Thanks for the update.

Michael.