MWareman

Nope - won't send formatted rest calls. Michael. Sent from my iPad using Tapatalk

If Echo acts as a 'trigger' with IFTTT - then you can add the CAO tag manager 'action' channel and have the tag manager on your lan issue the http REST calls to ISY. I have this working with text messages to IFTTT to control a fan and misc stuff. See http://forum.universal-devices.com/topic/8818-cao-sensors-support/?p=114779for the recipe. You'll need a tag manager to do this though (http://wirelesstag.net/) and contact their support for the private IFTTT channel.

That's an unusual error - Chrome is reporting things are blocked because the host uses HSTS. Except that ISY doesn't. Odd indeed 4.2.30 has been *very* stable for me.

Wow - you are a braver man than I! Nice job. I've never really played with Yahoo Pipes - you've given me a whole lot to look into. Truthfully, I've been avoiding Zapier because of the limitations. Looking at the pipes code you've put out there it's no mean feat. I have some learning to do!

We are told that work is afoot in 5.x to 'drastically' increase SSL speed. That will almost certainly help. On a side note, I never was able to get a network resource to call the MyQ api to open or close the door. I went the route of my Elk wired to a remote - but would love to find what I was doing wrong. Finally, IFTTT calling the ISY REST interface? Say it isn't so.... Directly? Or thru a proxy?

......Or build something with either Tasker or iRule. I've mostly given up on MobiLinc Android and pit together scenes on Tasker for home control via the REST api. I posted the basics on the wiki.

Pushover can send a url. That can be useful for 'sending' an image. Pushbullet can send files that will download - not what I wanted. Notifymyandroid let's you send html - so that may help as well.

Did you just wire the relay coil in parallel to the bell? If so, what rating was your coil so it does not prevent the bell from operating?

Need to figure this one out myself (not with this camera though) Kids in my neighborhood like to play 'ding-dong-ditch' and then claim it wasn't them. Initially, trying to figure out the best way to drive an iolinc from the doorbell push (spst), but have the actual bell still operate (24v AC).

It does work if you upgrade to the latest version - UDI made TLS the default for non-pro which solved this issue.

I suspect the reverse could be done with the substitution in network rules - so perhaps asking to be able to make a network rule a responder in a scene may be better. Just a thought...

Michel, Will they work the other way as well? For example. I define a virtual node to represent a url (a mostly complete GET request to Auto remote, with a single parameter to be replaced with the level, say 1-255). I then put that node into a scene (as a responder), with an 'on' level to match the other nodes in the scene. Now, as the scene is called, Auto remote receives the messages with the on level. Bright and dim commands send the new level to the node etc etc...... Thanks, Michael.

With the latest ISY version, there should be no issue. The higher encryption though makes it a little sluggish to connect.

Depends on the version of your ISY (99 vs 994, PRO vs non-PRO and the specific firmware version).

Sweet! Looks like! variable enhancements may be in an early drop after all!

Wow. I'm up to 460 programs, 53 integer variables, 132 state variables and 279 network resources. I *really* hope I will be able to eliminate over 200 network resources soon (when substitution comes in 5.x)

VPN can be as insecure as 'port forwarding', and 'port forwarding' can be as secure as VPN. The devil is in the details and the implementation.

And if you don't want that behavior, just split it into two programs: Program1 IF condition 1 AND condition 2 THEN Program2 RunThen Program2 (disabled!) IF THEN wait 5 minutes turn on device

The Android version does not though. Been 'coming soon' for two renewals now. I've decided I'll wait for these features without spending more, then assess my situation (if) MobiLinc ever brings feature parity where the platform supports the feature.

I've set my Connect subscription to not renew. If MobiLinc gets Elk and variable support I'll probably resubscribe. So far, I've given up waiting and am working on my own Tasker solution.

Just added one on my phone. Trigger your profile on 'Event' and NotifyMyAndroid is under '3rd party events'. There you can set your filters to trigger on.

Pushbullet needs either the ISY network module, or you need to add IFTTT as a middle tier. Pushbullet do not operate an email to push gateway. Pushover does operate an email to push interface - but its not free. Notify my android also operates an email to push interface, and a Tasker trigger. Might want to look at that one as well. Most of us doing this use the network module - its generally much faster and more reliable. However, network module does not support variable substitution. That will be fixed sometime in the 5.x timeframe....

There is a trick with Pushbullet, but I've not found it very reliable. Pushbullet can automatically set the device clipboard to the content of the message, then Tasker can read the clipboard.

Yep. Install pushover on device. Set Tasker task to play sound when certain pushover message is received. Send email to Pushover email interface and done. Personally, I use Autoremote and the network interface and find it fairly instant. Email can have delays.

You could look at services that accept email and talk to Tasker. Pushover comes to mind, but I have not spent much time on the Pushover=>Tasker interface.