Messages

[@lor74cas]

@lor74cas
- show on chart: found and fixed, thanks

in new beta this  option is no more available this is what you mean with fixed?  🤣🤣🤣

Inviato dal mio SM-A520F utilizzando Tapatalk

In version 3.31.0 there is a new possibility to filter points by date. This is very useful but on my Samsung Tab3 active and Samsung S7 it doesn't seem to work..all the points are selected whatever date I try to filter them with... .What do I do wrong?

Confirmed, sorting by date works, filter by date does not work

Inviato dal mio SM-A520F utilizzando Tapatalk

Bug found on Pro version
Tap on a track previously recorded on map
Open options and choose elevation chart.
Crash every time.


Inviato dal mio SM-A520F utilizzando Tapatalk

[@lor74cas]

@lor74cas
nono keep action as "com.asamm.locus.ACTION_TASK".
I was talking about another parameter that may be defined in tasker called "Package". This parameter define, which application should handle this intent.

Found it and it works now with Pro.
If you like it, I'll post the scripts (pro and free) on http://help.locusmap.eu/topic/auto-pause-while-connected-to-my-car-via-bluetooth

Inviato dal mio SM-A520F utilizzando Tapatalk

@lor74cas
Good point. Try to define "package" parameter.
"menion.android.locus" for a free version and "menion.android.locus.pro" for Pro version. Should work.
Sent from my SM-G930F using Tapatalk

menion.android.locus.pro.ACTION_TASK  -> does not work
menion.android.locus.ACTION_TASK  -> I cann't test I have beta and not free installed

Hello,
does intent on pro works wit the same action: com.asamm.locus.ACTION_TASK ?
I have both beta and pro and the intent starts always with beta If I have only a version installed as a normal user that usually has  pro or free how does it works ?

[@lor74cas]

@lor74cas
"stop" intent, in this case, makes sense, but most common scenario will be request without defined "profile". Ok ... solution ... "name" defined = only apply if this profile is active, otherwise stop always.

Support for Live tracking is planned.

Hello, tested intent on last version:
Example:
track rec started with profile geo
intent sent pause geo, paused current geo recording profile OK

track rec started with profile car
intent sent pause geo, paused current car recording profile NOT OK

[@lor74cas]

Thanks for pre-release feedback guys.

@lor74cas
pause intent: and what you expect? . You wants "pause", and it happen. No matter what profile is used. Also in docs, there is no info about supported "profile" for "pause" action.

And LT error ... aa yep, we know about it.

Pause intent has to be directed to a profile.
If I'm not geocaching, as the tasker script is  made for, and I want to track my car trip when bt starts the locus recording stops.
It'd be useful an intent to start and stop just LT. It can work inverse of geocaching tasker script. Every time I start my car trip, the car bt connects and starts LT sending a message to a contact with a link something like " look I'm here follow me"


Inviato dal mio SM-A520F utilizzando Tapatalk

Today on Pro LT error. My usual profile changed on it's settings, all fields value was 90. Changed only user name and worked as usual but it was a strange behaviour.

Inviato dal mio SM-A520F utilizzando Tapatalk

Second I declared a profile to start and stop named geo. But this Locus react in this way to the intent:
If the profile exists in locus than it is started or paused, if it does not exists it starts or pause the default profile (I did not expect this).

Third if there is not any track recording started, the pause intent starts a recording but it starts paused.

This is my 0.0.1 version of the task and needs some improvement but I need some explanation about the 3 points I wrote.


Inviato dal mio SM-A520F utilizzando Tapatalk

With RC version the start intent now works correctly with the specified profile. In case there is no "geo" profile does nothing as expected.

The pause intent pause every running recording and not the specific one "geo".

Happy vacation and stay away from every smartphone



Inviato dal mio SM-A520F utilizzando Tapatalk

[@lor74cas]

@lor74cas
About first point, this is related to how tasker work.

The 1st point it's about the easy of use of the tasker script:
My idea is to make it generic and if a user want's to fire it up only with a specific device, he can configure it in this way.

Btw. is anyone using Tasker application for some automation? I've created quite interesting feature ( https://github.com/asamm/locus-api/wiki/Action-tasks-(Broadcasts) ) a week ago, so I'm curious if someone find it useful .

Following this tutorial:
http://forum.joaoapps.com/index.php?resources/integrate-google-assistant-with-tasker-using-join-ifttt.206/

Now google assistant can start the recording profile "live" that I set up in locus with automatic start of livetracking. No need to touch the phone.
An add on to the profile should be the automatic send to your selected contacts by e-mail/sms/whatsup... of message that they now can follow me on locus or on the site.

<TaskerData sr="" dvi="1" tv="5.1m">
   <Profile sr="prof17" ve="2">
      <cdate>1526833426177</cdate>
      <clp>true</clp>
      <edate>1526834042115</edate>
      <id>17</id>
      <mid0>16</mid0>
      <mid1>19</mid1>
      <nme>Bt On Off Locus</nme>
      <State sr="con0" ve="2">
         <code>3</code>
         <Str sr="arg0" ve="3">mydevice</Str>
         <Str sr="arg1" ve="3"/>
      </State>
   </Profile>
   <Task sr="task16">
      <cdate>1526221014713</cdate>
      <edate>1526834008723</edate>
      <id>16</id>
      <nme>Locus Paused</nme>
      <pri>100</pri>
      <Action sr="act0" ve="7">
         <code>559</code>
         <Str sr="arg0" ve="3">Locus paused</Str>
         <Str sr="arg1" ve="3">default:default</Str>
         <Int sr="arg2" val="3"/>
         <Int sr="arg3" val="5"/>
         <Int sr="arg4" val="5"/>
         <Int sr="arg5" val="1"/>
         <Int sr="arg6" val="0"/>
         <Int sr="arg7" val="0"/>
      </Action>
      <Action sr="act1" ve="7">
         <code>548</code>
         <Str sr="arg0" ve="3">Locus paused</Str>
         <Int sr="arg1" val="1"/>
      </Action>
      <Action sr="act2" ve="7">
         <code>877</code>
         <Str sr="arg0" ve="3">com.asamm.locus.ACTION_TASK</Str>
         <Int sr="arg1" val="0"/>
         <Str sr="arg2" ve="3"/>
         <Str sr="arg3" ve="3"/>
         <Str sr="arg4" ve="3">tasks: { track_record: { action: "pause", name: "geo" } }</Str>
         <Str sr="arg5" ve="3"/>
         <Str sr="arg6" ve="3"/>
         <Str sr="arg7" ve="3"/>
         <Str sr="arg8" ve="3"/>
         <Int sr="arg9" val="0"/>
      </Action>
   </Task>
   <Task sr="task19">
      <cdate>1526221014713</cdate>
      <edate>1526833994740</edate>
      <id>19</id>
      <nme>Locus Started</nme>
      <pri>100</pri>
      <Action sr="act0" ve="7">
         <code>559</code>
         <Str sr="arg0" ve="3">Locus started</Str>
         <Str sr="arg1" ve="3">default:default</Str>
         <Int sr="arg2" val="3"/>
         <Int sr="arg3" val="5"/>
         <Int sr="arg4" val="5"/>
         <Int sr="arg5" val="1"/>
         <Int sr="arg6" val="0"/>
         <Int sr="arg7" val="0"/>
      </Action>
      <Action sr="act1" ve="7">
         <code>548</code>
         <Str sr="arg0" ve="3">Locus started</Str>
         <Int sr="arg1" val="1"/>
      </Action>
      <Action sr="act2" ve="7">
         <code>877</code>
         <Str sr="arg0" ve="3">com.asamm.locus.ACTION_TASK</Str>
         <Int sr="arg1" val="0"/>
         <Str sr="arg2" ve="3"/>
         <Str sr="arg3" ve="3"/>
         <Str sr="arg4" ve="3">tasks: { track_record: { action: "start", name: "geo" } }</Str>
         <Str sr="arg5" ve="3"/>
         <Str sr="arg6" ve="3"/>
         <Str sr="arg7" ve="3"/>
         <Str sr="arg8" ve="3"/>
         <Int sr="arg9" val="0"/>
      </Action>
   </Task>
</TaskerData>

It works but has a some strange behaviour.

First of all each one has to configure his device that triggers the tasker action.
If left blank every BT connected will active the tasker trigger. I usually wear a Garmin forerunner sometimes I share data with bt to my wife phone so I want that the action triggers only when my bt car device connects.

Second I declared a profile to start and stop named geo. But this Locus react in this way to the intent:
If the profile exists in locus than it is started or paused, if it does not exists it starts or pause the default profile (I did not expect this).

Third if there is not any track recording started, the pause intent starts a recording but it starts paused.

This is my 0.0.1 version of the task and needs some improvement but I need some explanation about the 3 points I wrote.


Inviato dal mio SM-A520F utilizzando Tapatalk

Today locus activated just for live tracking 4% of battery in 2 hours.
Not too much sorry the track rec was not active maybe this weekend I'll try.


Inviato dal mio SM-A520F utilizzando Tapatalk

[@Leeds Tyke]

Thanks for a feedback guys.
Idea behind chat is definitely not to replace some bigger apps like Whatsup or similar. The idea here is to bring instant communication solution between more people where big advantage will be with a connection to Locus Map app.
So first what comes to mind is to send to others some location/point that will immediately appear on the map like the regular point. We were today think also about an option to share some more complicated content like full geocache or for example definition of area. So generally it should be really simple chat were the location (my, my friends, shared place) will play an important role.

And of course, I know that more != better. Anyway, I'm sure that see someone on the map and be able to quickly communicate with him are very connected features.

@Leeds Tyke
thanks! I'll look at it.

With your explanation the proposal of the chat feature has a new point of view.
My first impression was focused only on "chat".

Inviato dal mio SM-A520F utilizzando Tapatalk

Just thinking about Chat and my personal opinion.
Does this feature have real use and relevance?
Today there are free calls, SMS free, a million social networks and text communicators.

Personally, this option probably never use.
Is this really what we need in Locus?

P.S. I do not want this in any way offend Locus team :-)



I have ideas for an automatic life saving feature. (notification and emergency rescue) It may be a separate application or addon. The advantage is that Locus is mostly run on "risky" activities and already connected to the device's sensors.
If this topic is interesting ... I can write more privately.

+1
Even the organization of a trail running race would not rely on an online chat to contact the participants.
It's safer to use text messages, they have everyone's phone number.

In the case of a small group, for example family members who follow you with the LT, they would not use the chat, but whatsapp or a phone call.

Not always more is better. Too many features make applications bigger and sometimes make them more complicated for users and developers (and bet testers  )
For example, who does not care about the chat can make the icon that covers the map disappear?