Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request: tasker integration #156

Open
wokawoka opened this issue Nov 11, 2021 · 6 comments
Open

feature request: tasker integration #156

wokawoka opened this issue Nov 11, 2021 · 6 comments

Comments

@wokawoka
Copy link

Being able to push the prices of the coin that I monitor to my watch via tasker would be just great.
It would also open up many other integration possibility.
Could it be by chance a feature that you might be interested to implement?

By the way, I love your app and I use it daily.
Thank you so much for the great work you are doing!

@aneonex
Copy link
Owner

aneonex commented Nov 11, 2021

Unfortunately, I do not use a watch, so it is difficult to implement the related features.
What do you mean by the "tasker". Is it android watch technology or a third-party app or something else?

@wokawoka
Copy link
Author

Thank you for replying.
Tasker is an automation software for android , see https://tasker.joaoapps.com and https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm .
As a matter of fact along the years it has become a kind of a standard on android and hundreds of apps support it, so that it's possible to interlink them and to create nice automations.

Being able to expose bitcoin checker's prices to tasker would allow to push that data into other apps that support it.
It's already possible to instruct tasker itself to talk with coinmarketcap's or coingecko's api to pull coin prices, but since bitcoin checker is already pulling the same data on the phone it would be much more efficient to use it instead of requesting it twice.
It would be very cool and useful.

@tomoeuehara
Copy link

I believe this Issue can be done if aneonex decided to add a 'write to file' feature.
About which format to choose, there are several options:

  1. Plain text file
  2. Sql (or sqlite)
  3. JSON

Now let's see one by one, a plain txt file is probably the easiest way to let end user read values dumped by Bitcoin Checker app, but it seems so unprofessional even if the data saved inside the txt file was a csv formatted.

Second the sql(lite), sqlite is natively available in Android, but usually it requires root access to operate with it, and we don't want this.

Lastly if Bitcoin Checker app could dump (1-10 latest values) into a JSON file, it will be sufficient for any user to do whatever they want with the dumped data.
But it means Bitcoin Checker app would need a write permission...

@wokawoka
Copy link
Author

@tomoeuehara I realized that someone replied to the issue only now after nearly one month
yes, great idea, logging the prices would work perfectly.
I just don´t know if, in case one would do it with many different coins, if the increase of the write cycles on the flash would be a problem for the phone. I really don't know that, it's just my guess. But great suggestion

@tomoeuehara
Copy link

@wokawoka How many coins would you like to fetch?
Actually streaming on Youtube (or other streaming app/site) will still do write cycle on your phone, so don't worry about it.
If Aneonex doesn't implement this suggestion, then it's better for you to write a Tasker script for fetching the price instead (it's quite easy to do), and close this Issue.
Yes it's redundant for both app to fetch the same data, but it's up to you though... :)

@wokawoka
Copy link
Author

@tomoeuehara at the moment I'm monitoring 5 coins.
Yes, I know I can fetch the data from tasker, I was just trying to find a way to get the data from bitcoinchecker. Let's see how the issue will develop. I like a lot and I find bitcoin checker extremely useful anyway

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants