Author Topic: ifttt-trigger-event-check  (Read 3816 times)

ScottM

  • Newbie
  • *
  • Posts: 41
ifttt-trigger-event-check
« on: October 23, 2016, 06:50:11 pm »
I'm experimenting with IFTTT recipes. One thing I don't really need is to keep seeing "ifttt-trigger-event-check" events in the Particle log screen. Is there a way to filter these messages out?

PeterF

  • Hero Member
  • *****
  • Posts: 881
Re: ifttt-trigger-event-check
« Reply #1 on: October 23, 2016, 09:34:07 pm »
Not that I know of Scott. It is an information event that they added to show how quickly and reliably the IFTTT integration was working. It gets annoying for us when you look at the raw logs, as it pops up when you're just looking for messages from your Oak. Best I suggest on that front is to see if you can sweet-talk kh to adding a filter for that to OakTerm, as it has toggles to show-hide other events... so it should be too hard to add?

ScottM

  • Newbie
  • *
  • Posts: 41
Re: ifttt-trigger-event-check
« Reply #2 on: October 24, 2016, 05:09:17 am »
Hi Peter,

First, I appreciate your commitment to helping others through these forums. I still have a lot to learn about using my OAK boards. I haven't used OakTerm much yet. I don't really know much about it. Now that i just ran it, I was surprised to see the icons at the top, especially reboot and config mode. I had been forcing config mode by physically grounding P1, but that can be a real pain when your Oak is installed in some hard to reach place. If I press the config mode button in OakTerm, will it do the same thing as grounding P1?

As for filtering out the IFTTT messages, that would be a nice addition. The attached image shows how they can really clutter the screen. These particular messages are from Oak-7. Yesterday I completed a small shield to interface Oak to my old home alarm system. The sensors from various doors already go there, so it makes it a great place to insert an Oak. I had to stop using the alarm system when I switched to a VOIP home phone. If you look at the log, you'll see that I opened and closed the front door, side door and then garage door. What you don't see is that after I opened the garage door, I activated both car doors and that's where Oak-6 will report them being opened. If OakTerm is going to be useful, it would have to report on more than one oak at a time. Can it do that?

exeng

  • Sr. Member
  • ****
  • Posts: 454
Re: ifttt-trigger-event-check
« Reply #3 on: October 24, 2016, 09:18:08 am »
Scott, I have an older alarm system also and thought abort tapping in using the Oak. Haven't done anything yet or researched it as to what may be possible. Just curious, how did you tap into the system? Are you looking at all the door switch connections with the Oak or are you somehow interfaced to the alarm system directly?

PeterF

  • Hero Member
  • *****
  • Posts: 881
Re: ifttt-trigger-event-check
« Reply #4 on: October 25, 2016, 01:52:52 am »
No problem Scott, more the merrier in the learning journey... xD

Yup, the icons at the top let you send an event to your Oak, reboot it, reboot it into config mode, or reboot it back into the user program. Assuming the Oak is still responding to wifi commands, of course! ;)

They to indeed get annoying... especially when you are in the testing stage, and are triggering the event repeatedly... it was getting very annoying when i was working on the NRF bridge thingy, as I was using IFTTT to send particle data to a google docs spreadsheet, and was triggering it every 4 seconds in the initial testing stages... so get two of those event messages every 4 seconds! :-/

I'll add a issue / request on the github page (done: linky be here), and wait to see what the grand master thinks! ;)

Oh, btw @exeng, I think Scott is using reed/magnetic switches and magnets mounted on the doors, but I'll let him enjoy explaining it to you (and in case I'm remembering that wrong :-O)
« Last Edit: October 25, 2016, 03:20:46 am by PeterF »

kh

  • Jr. Member
  • **
  • Posts: 64
  • OakTerm developer
Re: ifttt-trigger-event-check
« Reply #5 on: October 25, 2016, 04:29:06 pm »
I'll add a issue / request on the github page (done: linky be here), and wait to see what the grand master thinks! ;)

Should be fairly easy to do, just have to find the time. There's more work in extending the UI to set a filter than there is in the actual filtering.

I'll put it on my todo list!

If OakTerm is going to be useful, it would have to report on more than one oak at a time. Can it do that?

Not at the moment. We discussed that feature, but it would have made the "send" features complicated (e.g. which Oak does data and commands get sent to?). You can however run multiple instances of OakTerm in separate browser tabs or windows, one for each of your Oaks.

ScottM

  • Newbie
  • *
  • Posts: 41
Re: ifttt-trigger-event-check
« Reply #6 on: October 25, 2016, 04:29:28 pm »
@exeng, I will start a new post with details about how I hacked into my old alarm system. I think that is better than diverting this topic.


ScottM

  • Newbie
  • *
  • Posts: 41
Re: ifttt-trigger-event-check
« Reply #7 on: October 25, 2016, 04:39:08 pm »
@kh, thanks for putting the filter on your list. IFTTT is a nice service, even if it is a bit of a pain to create multiple recipes. It's too bad they limit us to only 100 SMS messages per month. I'm using IFTTT to send me messages when one of my alarm system triggers goes off, ex. door opening.

I don't have much experience using OakTerm yet, but I see your point. If you are sending commands, you have to define which Oak to send them to, like how I use OakCLI to select an Oak before Arduino IDE uploads code. I get that. It's just that to create a home monitoring system using Oaks, I'll need to use several of them, so I'd like one place to go to see the system as a whole.