Module as Tasker Plugin #1205

Open
opened 3 years ago by dakhnod · 15 comments
dakhnod commented 3 years ago

i am working on a Fossil Q hybrid interface, which i temporarily deleted for legal reasons.
My idea is to make my module available as a tasker plugin.
Basically, the user gets the possibility to connect tasker events to events with the watch, like vibrations, hand notifications etc.

Would that be okay? Or should i exclude the plugin part before a pull request?

i am working on a Fossil Q hybrid interface, which i temporarily deleted for legal reasons. My idea is to make my module available as a tasker plugin. Basically, the user gets the possibility to connect tasker events to events with the watch, like vibrations, hand notifications etc. Would that be okay? Or should i exclude the plugin part before a pull request?
Owner

I don't quite understand what you mean. How would Gadgetbridge be involved with the Tasker plugin? Would Gadgetbridge communicate with the watch or would the Tasker plugin do that? Can you elaborate a bit?

I don't quite understand what you mean. How would Gadgetbridge be involved with the Tasker plugin? Would Gadgetbridge communicate with the watch or would the Tasker plugin do that? Can you elaborate a bit?
Poster

sure.
The Q watch can output notifications by vibrating and setting the hands for a few seconds according to the configuration for the package.
If, for instance, whatsapp is bound to 90 degrees, whenever i get a whatsapp message the watch vibrates and sets both hands to 90 degrees.

I want to give the user the possibility to talk to the watch not only through notifications, but also through tasker.
For instance, my aim is to make a tasker profile which gets some data from my bitcoin wallet and displays the current value of my wallet on my watch every hour.
Thus, tasker would call my module plugin and give it some variables, which my module would then show on the watch.

sure. The Q watch can output notifications by vibrating and setting the hands for a few seconds according to the configuration for the package. If, for instance, whatsapp is bound to 90 degrees, whenever i get a whatsapp message the watch vibrates and sets both hands to 90 degrees. I want to give the user the possibility to talk to the watch not only through notifications, but also through tasker. For instance, my aim is to make a tasker profile which gets some data from my bitcoin wallet and displays the current value of my wallet on my watch every hour. Thus, tasker would call my module plugin and give it some variables, which my module would then show on the watch.
Poster

I just finished my Bitcoin project.
Now, every hour, the watch vibrates in a certain way, sets the hour hand to 120° (4 o'clock), and sets the minute hand to represent the profit/loss of my wallet.
That is just an example, of course tasker opens endless possibilities, when even the vibration may be set by tasker as a variable.

I just finished my Bitcoin project. Now, every hour, the watch vibrates in a certain way, sets the hour hand to 120° (4 o'clock), and sets the minute hand to represent the profit/loss of my wallet. That is just an example, of course tasker opens endless possibilities, when even the vibration may be set by tasker as a variable.
Collaborator

I'd love that – if you don't restrict it to the Q. The Pebble can vibrate and show notifications as well. Sure one could simply have Tasker send a notification – but other options would be opened as well. E.g. on the Pebble, apart from notifications, things could be pushed to the timeline (causing a "lower third screen only" notification. And who knows what other ideas come up and get possible that way …

I'd love that – if you don't restrict it to the Q. The Pebble can vibrate and show notifications as well. Sure one could simply have Tasker send a notification – but other options would be opened as well. E.g. on the Pebble, apart from notifications, things could be pushed to the timeline (causing a "lower third screen only" notification. And who knows what other ideas come up and get possible that way …
Poster

Of course there is no reason to restrict it to a certain device.
Yet, IMO every device should have its own module, since devices vary in functionality.
I just opened this discussion because such a module requires a change to a gradle script, thus impacting the base application.

Of course there is no reason to restrict it to a certain device. Yet, IMO every device should have its own module, since devices vary in functionality. I just opened this discussion because such a module requires a change to a gradle script, thus impacting the base application.
Owner

I see, interesting project :-)

Why does every device need its own module? (Forgive me, I'm not using Tasker). I would've thought, that tasker would send some kind of event (intent?) and Gadgetbridge would somehow reacto to it.

So one would need a mapping from the Tasker event to some kind of notification profile. So one could have a list of notification profiles, that may have device specific configurations. For the Fossil watches, one could configure vibration and the hands, for Mi Bands, Bips and Pebbles one could configure icon, text and vibration, etc.

That way, we would not need extra device specific modules.

What do you think?

I see, interesting project :-) Why does every device need its own module? (Forgive me, I'm not using Tasker). I would've thought, that tasker would send some kind of event (intent?) and Gadgetbridge would somehow reacto to it. So one would need a mapping from the Tasker event to some kind of notification profile. So one could have a list of notification profiles, that may have device specific configurations. For the Fossil watches, one could configure vibration and the hands, for Mi Bands, Bips and Pebbles one could configure icon, text and vibration, etc. That way, we would not need extra device specific modules. What do you think?
Collaborator

@cpfeiffer I don't think each device needs its own module. If Tasker integration is done at the core, GB knows what device(s) is/are configured and "fill the form" accordingly. If there are multiple devices, the first step would be device selection (if only one device is configured, its ID can be assumed automatically). After that, only functionality available for that specific device is "enabled".

You know I'm no Android dev, so for the technical/implementation part someone else must fill in 😉

What I can think of as well is starting a certain app on the device, triggered by Tasker. And IIRC there was one device where data transfer needs to be triggered from GB to happen. As Tasker also offers several GUI things (e.g. shortcuts on the homescreen to trigger tasks, or scenes (I've never played with those, but imagine they are like widgets), this opens a whole arena of possibilities.

What a pity Tasker isn't FOSS. The same interface would work for Locale (also not FOSS) – and I vaguely remember there was a third app able to use them. Macrodroid it seems. Hm, also not on F-Droid 😞

@cpfeiffer I don't think each device needs its own module. If Tasker integration is done at the core, GB knows what device(s) is/are configured and "fill the form" accordingly. If there are multiple devices, the first step would be device selection (if only one device is configured, its ID can be assumed automatically). After that, only functionality available for that specific device is "enabled". You know I'm no Android dev, so for the technical/implementation part someone else must fill in :wink: What I can think of as well is starting a certain app on the device, triggered by Tasker. And IIRC there was one device where data transfer needs to be triggered from GB to happen. As Tasker also offers several GUI things (e.g. shortcuts on the homescreen to trigger tasks, or scenes (I've never played with those, but imagine they are like widgets), this opens a whole arena of possibilities. What a pity Tasker isn't FOSS. The same interface would work for Locale (also not FOSS) – and I vaguely remember there was a third app able to use them. [Macrodroid](https://community.unifiedremote.com/topic/586/macrodroid-support-via-tasker-plugin) it seems. Hm, also not on F-Droid :disappointed:
Poster

i am glad i sparked this discussion heh

Am Sa., 11. Aug. 2018 um 23:07 Uhr schrieb Izzy notifications@github.com:

@cpfeiffer https://github.com/cpfeiffer I don't think each device needs
its own module. If Tasker integration is done at the core, GB knows what
device(s) is/are configured and "fill the form" accordingly. If there are
multiple devices, the first step would be device selection (if only one
device is configured, its ID can be assumed automatically). After that,
only functionality available for that specific device is "enabled".

You know I'm no Android dev, so for the technical/implementation part
someone else must fill in 😉

What I can think of as well is starting a certain app on the device,
triggered by Tasker. And IIRC there was one device where data transfer
needs to be triggered from GB to happen. As Tasker also offers several GUI
things (e.g. shortcuts on the homescreen to trigger tasks, or scenes (I've
never played with those, but imagine they are like widgets), this opens a
whole arena of possibilities.

What a pity Tasker isn't FOSS. The same interface would work for Locale
(also not FOSS) – and I vaguely remember there was a third app able to use
them. Macrodroid
https://community.unifiedremote.com/topic/586/macrodroid-support-via-tasker-plugin
it seems. Hm, also not on F-Droid 😞


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Freeyourgadget/Gadgetbridge/issues/1205#issuecomment-412301655,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY7qF7iceZzclyScBKjVg9TGtwiBbrRSks5uP0efgaJpZM4V5Kg8
.

i am glad i sparked this discussion heh Am Sa., 11. Aug. 2018 um 23:07 Uhr schrieb Izzy <notifications@github.com>: > @cpfeiffer <https://github.com/cpfeiffer> I don't think each device needs > its own module. If Tasker integration is done at the core, GB knows what > device(s) is/are configured and "fill the form" accordingly. If there are > multiple devices, the first step would be device selection (if only one > device is configured, its ID can be assumed automatically). After that, > only functionality available for that specific device is "enabled". > > You know I'm no Android dev, so for the technical/implementation part > someone else must fill in 😉 > > What I can think of as well is starting a certain app on the device, > triggered by Tasker. And IIRC there was one device where data transfer > needs to be triggered from GB to happen. As Tasker also offers several GUI > things (e.g. shortcuts on the homescreen to trigger tasks, or scenes (I've > never played with those, but imagine they are like widgets), this opens a > whole arena of possibilities. > > What a pity Tasker isn't FOSS. The same interface would work for Locale > (also not FOSS) – and I vaguely remember there was a third app able to use > them. Macrodroid > <https://community.unifiedremote.com/topic/586/macrodroid-support-via-tasker-plugin> > it seems. Hm, also not on F-Droid 😞 > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/Freeyourgadget/Gadgetbridge/issues/1205#issuecomment-412301655>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AY7qF7iceZzclyScBKjVg9TGtwiBbrRSks5uP0efgaJpZM4V5Kg8> > . >
Owner

What about Easer? (available in f-droid): https://renyuneyun.github.io/Easer/en/

I should really have a closer look at those tools to get a better understanding :-)

What about Easer? (available in f-droid): https://renyuneyun.github.io/Easer/en/ I should really have a closer look at those tools to get a better understanding :-)
Collaborator

Sure, why not? Necessary steps are described in their HOWTO. I'm not using it, but it sounds good – and it's FOSS 😉

Sure, why not? Necessary steps are [described in their HOWTO](https://renyuneyun.github.io/Easer/en/HOWTO). I'm not using it, but it sounds good – and it's FOSS :wink:
Poster

So...no Tasker?

So...no Tasker?
Owner

No, it was not meant that way. AFAIU, Gadgetbridge would mostly be a consumer of a tasker event. So the user should be able to choose the event. If that would come from tasker, easer or something else should not matter.

No, it was not meant that way. AFAIU, Gadgetbridge would mostly be a consumer of a tasker event. So the user should be able to choose the event. If that would come from tasker, easer or something else should not matter.
LuccoJ commented 3 years ago (Migrated from github.com)
Owner

@cpfeiffer if it worked that way, it would be nice. For what is worth, I'd personally feel quite uneasy with an explicit integration with specifically Tasker, which is nonfree and not on F-Droid and all that.

@cpfeiffer if it worked that way, it would be nice. For what is worth, I'd personally feel quite uneasy with an *explicit* integration with *specifically* Tasker, which is nonfree and not on F-Droid and all that.
Collaborator

@LuccoJ "specifically" Tasker is not true. The same interface is used by multiple apps (as I pointed out above). I'm a happy Tasker user though, so I'd love to see that functionality provided.

@LuccoJ "specifically" Tasker is not true. The same interface is used by multiple apps (as I pointed out above). I'm a happy Tasker user though, so I'd love to see that functionality provided.
Owner

If tasker (like other apps) sends out plain intents, we would need a way to receive and display them to the user. The user would then select one and map it to a notification in Gadgetbridge.

Advanced: provide a set of filter operators by certain intent data.

If tasker (like other apps) sends out plain intents, we would need a way to receive and display them to the user. The user would then select one and map it to a notification in Gadgetbridge. Advanced: provide a set of filter operators by certain intent data.
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.