WatchApp: GIFTTT Alpha (Garmin device IFTTT trigger)

https://apps.garmin.com/en-US/apps/04890351-a25c-40ad-afae-f3c6907fe05f

GIFTTT is a simple application that allows Garmin devices to trigger IFTTT events via the IFTTT Maker channel (http://ifttt.com/maker). This may not sound all that interesting, but here are a few things it can allow you to do.

Open or close your garage door
Turn on or turn off a fan or other device
Control a programmable thermostat
Change the ambient lighting, open/close blinds
Text your wife a pre-written message

Anything you could control with IFTTT, you can control with GIFTTT. For actions may require purchase of additional hardware (to control ambient lighting, you'll need lights that are controllable similar to the Phillips Hue system, or to turn on/off a switch you might need to buy something like a Belkin Wemo Switch).

Instructions:

To use this app, you'll need to configure an IFTTT account, and activate the Maker channel (http://ifttt.com).
Once you've done this, you'll have to get into the application settings for GIFTTT and set the secret key you were given.
You will then need to create an IFTTT recipe to connect the services that you wish to use. For instance, if you wish to send your wife a pre-written text message, you would configure the Maker channel as the 'this' portion of the recipe, and iOS/Android Notification as the 'that'.
Now that you have a IFTTT recipe in place, you will need to configure one of the tasks in GIFTTT with the name and values you want to feed to the IFTTT recipe. You can do this from the GIFTTT menu for the task you want to modify.
To submit an action, you just have to pull it up on screen it and press enter.

Notes:

I don't currently have any logic in place to verify your key is correct and I don't check that you've entered one at all. I plan to fix this in the future.
The app currently does nothing to tell you that your device is not connected Garmin Connect Mobile. You will get errors when trying to submit requests, not before. I'd like to fix this so users see a not connected page.
The app currently displays a 404 error code. This does not mean that the send didn't work, it just means that the IFTTT server responded with data that couldn't be parsed by the devices JSON parser. I need to figure out how to tell IFTTT to send back JSON data.
There is currently no support for adding/deleting actions. You can rename and configure the existing ones, but you can't add or delete them. This will be addressed soon.
This is currently a watch-app, but I'd like it to be a widget. As soon as I can figure out how to get the widget to let me use the up/down arrows, I'll switch over. I'm considering adding a widget that has only one action (similar to the existing IFTTT Do channel).
The user interface is a little clunky. I'll work to refine it in the future.
I'd like to be able to send data from the device in place of the hard-coded value strings. For instance, you could send your current position and speed data to IFTTT.
If you have ideas on how to improve this app, please feel free to make requests.

Release History:

0.0.2
* Remove my secret key from the default settings.

0.0.1
* Initial Revision
* Supports 920XT with 4.20 firmware (ConnectIQ 1.1.2)

Former Member over 9 years ago

Awesome Guide! I'm Not sure if i exited the app 1st. But with your latest release it seems to be working great for me now. It would be nice if there was a way to have a preview of the secret key once its been entered? For example - when you exit the screen after you enter the Key and and want to make sure you've entered it correctly you can't see it again. When i go back into the secret key screen i get a blank screen and i must renter the key.

travis.vitek over 9 years ago

When i go back into the secret key screen i get a blank screen and i must renter the key.

If that is the case, something is wrong. Maybe you pressed the back button after entering the secret key? The current value of the secret key is shown when you return return to the Secret Key menu (the previous key is used as the initial value). I've just verified this (again) on my fr920xt.

Now that I think about it, I should change this. I don't ever want to make the secret key visible after it has been properly entered (to help ensure it remains a secret). It seems that the flow should be...

If the secret key has not been set, jump to step 5.
Prompt to replace the existing secret key.
If the user selects OK, jump to step 5.
If the user selects Cancel, return to the menu.
Prompt for the secret key with an initially empty text input.
If the user presses Back, no change is made to the secret key.
When the user selects OK, a confirmation appears which shows the key that was entered.
If the user selects OK, the key is saved never to be seen again.
If the user selects Cancel, they are returned to the text input with the previously entered value already there.

The end result is that you'd always see a blank value if you enter the Secret Key menu. The advantage of this is that it is more difficult for someone to get your secret key and open your garage door (or whatever your recipe does). What do you think?

Travis

dezent over 9 years ago

THANKS!!!!!!!!!

Works fine with Fenix3 Software Version 3.8
I had some problems with the Menu (didn't accept the "input" to jump into the input for the key-value)
Restartet the watch once after installation - now my recipe works perfectly!

Best APP ever!

Thank you!

@all
all the keys and names are absolutely CASE SENSITIV!

bwd1 over 9 years ago

I'm likely doing something dumb, but my secret key has 43 char and I can only enter 31 of them.

Former Member over 9 years ago

If the secret key has not been set, jump to step 5.
Prompt to replace the existing secret key.
If the user selects OK, jump to step 5.
If the user selects Cancel, return to the menu.
Prompt for the secret key with an initially empty text input.
If the user presses Back, no change is made to the secret key.
When the user selects OK, a confirmation appears which shows the key that was entered.
If the user selects OK, the key is saved never to be seen again.
If the user selects Cancel, they are returned to the text input with the previously entered value already there.

The end result is that you'd always see a blank value if you enter the Secret Key menu. The advantage of this is that it is more difficult for someone to get your secret key and open your garage door (or whatever your recipe does). What do you think?

Travis

That would be great. It would be nice to know in some way that your key has been saved. But the app has been working great so far!

Former Member over 9 years ago

Here is what it looks like after i fire off a command.

But seems to be working great

bwd1 over 9 years ago

920xt and the key seems to be 43 characters long. I just signed up on https://ifttt.com/maker if that made a difference.

travis.vitek over 9 years ago

I'm likely doing something dumb, but my secret key has 43 char and I can only enter 31 of them.

I've generated about 5 secret keys (by clicking the Reconnect Channel button on this page) and every time the resulting key is exactly 22 characters long.

If you go to https://ifttt.com/maker, you should see a page that looks like this...

Your secret key should be shown right in the middle of the page. You can see my old key in the screenshot above, just below the text that says Your secret key is and next to the little lock icon. Are you looking at that secret key, or some other secret key? If you confirm, my next step is to contact the folks at IFTTT.

Here is what it looks like after i fire off a command.

I've fixed this and uploaded a new time-bombed version. I've also made the proposed change to confirm that the user wants to overwrite the old key and to confirm that the key they entered is correct.

I already know that the second confirmation isn't great. On the fr920xt the 22 character key wraps around the screen. I'm guessing it will look worse on the fenix3. I'll probably have to write a custom view so that it doesn't look so horrible.

dezent over 9 years ago

Fenix 3 Software: 3.80
Status: works

Bug found: i can't delete the values when i create new Events. I can delete the "value1", "value2", "value3" strings in the value field, but then i can not save. As soon as i type one letter i can save.
As soon as the entire string is deletet, the "hocklet" to save is dark gray and inactive.

Bug found: Name (Event) can not handle SPACE "navMytown" works fine. "Nav Mytown" doesn't. Maybe thats a ifttt problem and not a bug.

i love this APP! It finally makes my Fenix3 to a kind of smartwatch.
Please think about publishing your source Code on GitHub when you published it ConnectIQ Store.

bwd1 over 9 years ago

I've generated about 5 secret keys (by clicking the Reconnect Channel button on this page) and every time the resulting key is exactly 22 characters long. If you go to https://ifttt.com/maker, you should see a page that looks like this...

Yes, same page, and my key is 43 char long. I sent you a PM with a screen capture. Disconnect/reconnect give me the same length key.