Falcosc
commented
3 years ago No, there isn't any event based api. Just request sensor data in an infinite loop. Only functions like "Tell Locus Map to open the select destination dialog" fire events. (is not implemented because nobody did request to use locus as coordinate selection tool so far)
There is no event-based interface for data or actions triggered by locus. So if I implement the tasker event API, I would need to implement the infinite loop, too.
But there is a problem, if I implement it, it would look like "cool there is an event-based API, lets use it to save battery (CPU cycles)"
You could still say: "if we educate the user about the technical limitation, the tasker events would still useful to reduce the Task complexity because the infinite loop is hidden in the plugin instead of inside the tasker task" But there are more problems: The loop solution is not in real time like you would expect it from an event. You always have to wait until the next loop iteration is executed. And if you don't have the waiting for new data loop inside your task you may forget that this is not an event and wonder why things are delivered after a delay.
Do you still want to have it?
TapioOfTapiola
rplevka
Hello. I'd like to pull sensor data from the app every time a new track point is created (during track recording). Is your app also capable of sending intents if various events happen in Locus Maps? This way, I could create a tasker profile with such intent as a trigger and I wouldn't need to blindly trying to pull the data in the pre-defined intervals.
My goal is to make your app+tasker as a bridge between Locus Maps Track recording and MQTT. I'm mainly interested in data from my ANT+ sensors and Tasker doesn't provide a way of reading data from ANT+ directly.
Thanks and CG to a great addon