IFTTT feature: add support for realtime API #275
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nce of IFTTT integration. Signed-off-by: Maury Quijada <maury.quijada@gmail.com>
|
Thanks so much for the contribution! I was actually chatting with @kaikreuzer about this API call and the fact we are not using it, but should be. As soon as i modify how we store our events i will look at your changes so we can incorporate them. Just to be clear, our primary load issue is not IFTTT polling (well, at least not the main load problem) , the big issue is the Item and Event updates coming from peoples openHABs (whether they use IFTTT or not). I have a change to how these are stored that i hope will alleviate much of the issue, but I need to run it through some tests first. |
|
@digitaldan Same as before, or is IFTTT back ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Lately, it seems like myopenHAB has been struggling with IFTTT polling overload. I looked into this, and according to IFTTT API documentation, this could be improved by the realtime API. This also has the benefit of making IFTTT updates more realtime. Also, there's been a 2 year old issue about this here: #116