Add Custom WayPoints

[apppdevv2015]

Hi Team,

Is there any way to add Custom waypoints or regions in Mobile app? I can see there is option to importWayPoints in mobile app... Please let me know what will be the format. I tried xml and json for importing the waypoints.

[jpmens]

you tried xml and json? what data formats did you try? are you guessing?

waypoints can be added in the UI.

[apppdevv2015]

Yes, i have a requirements to add custom waypoints from the database.. Can you please let me know how it can be done?

Here is the example:

{
"waypoints": [
{
"latitude": 37.7749,
"longitude": -122.4194,
"name": "San Francisco",
"description": "City in California"
},
{
"latitude": 34.0522,
"longitude": -118.2437,
"name": "Los Angeles",
"description": "City in California"
}
]
}

[jpmens]

This is documented in the Booklet

[apppdevv2015]

Thank you. Will it work for both IOS and Mobile app? Is there any way to send data through MQTT and show on Mobile app?

[jpmens]

This method works for iOS and Android.

What data do you want to show on the apps?

[apppdevv2015]

I have requirements to create a regions in web application and show them in Mobile app through private server MQTT.. I sent custom waypoints (regions) to MQTT server and those are published but not added on mobile app under waypoints

[apppdevv2015]

Do we have import waypoints option in IOS? I didn't find it

[jpmens]

the message should be published with QoS>0

[apppdevv2015]

Okay so this is possible:

so we can add custom waypoints (regions) to MQTT server through "owntracks/user/device" and will be displayed on mobile app under waypoints

[apppdevv2015]

I tried this:

const region = {
"_type": "cmd",
"action": "setWaypoints",
"waypoints": {
"waypoints": [
{
"desc": "Aman2 place",
"rad": 8867,
"lon": 10.428771973,
"lat": 46.935260881,
"tst": 1437552714,
"_type": "waypoint"
}
],
"_type": "waypoints"
}
}

client.publish('owntracks/user/device', JSON.stringify(region), { qos: 1 }, (error) => {
    if (error) {
      console.error('Publish error:', error);
    } else {
      console.log('Region published');
    }
    client.end();
  });
  
  this is added on MQTT server but not added on Mobile app

[apppdevv2015]

I tried to import the below as json:

{
"_type": "cmd",
"action": "setWaypoints",
"waypoints": {
"waypoints": [
{
"desc": "Aman2 place",
"rad": 8867,
"lon": 10.428771973,
"lat": 46.935260881,
"tst": 1437552714,
"_type": "waypoint"
}
],
"_type": "waypoints"
}
}

But getting the message ImportFailed: Message is not a valid configuration

Please help

[jpmens]

The topic is wrong. It should be owntracks/user/device/cmd and remote cmd must be enabled on the device.

[apppdevv2015]

Cmd option is not available on Andriod phone

[apppdevv2015]

Allowremote location and cmd in enabled in IOS device

[apppdevv2015]

Could you please send me the file sample to import through Importwaypoints? I tried the json file but it didn't work

[growse]

Cmd option is not available on Andriod phone

Sure it is. What makes you think it's not?

[apppdevv2015]

Could you please send me the file sample to import through Importwaypoints in Andriod phone? I tried the json file but it didn't work

[jpmens]

This works for me.

$ mosquitto_pub -u user -P password -t owntracks/user/device/cmd -f wp-blau.json -q 1

The file wp-blau.json:

{
  "_type": "cmd",
  "action": "setWaypoints",
  "waypoints": {
    "_type": "waypoints",
    "waypoints": [
      {
        "_type": "waypoint",
        "tst": 1361636517,
        "rid": "blauw-utrecht-nl",
        "desc": "Restaurant Blauw",
        "rad": 50,
        "lat": 52.087822392366,
        "lon":  5.119438515394096
      }
    ]
  }
}

[apppdevv2015]

Is it working on Android? or IOS. Are you able to see it in Your Mobile app?

[apppdevv2015]

I tried it from Andriod phone, importwayPoints but getting the message ImportFailed: Message is not a valid configuration.

Please let me know full process:

when i tried to send to MQTT Server and its published in server:

{
"_type": "cmd",
"action": "setWaypoints",
"waypoints": {
"_type": "waypoints",
"waypoints": [
{
"_type": "waypoint",
"tst": 1361636517,
"rid": "blauw-utrecht-nl",
"desc": "Restaurant Blauw",
"rad": 50,
"lat": 52.087822392366,
"lon": 5.119438515394096
}
]
}
}

But not showing in Mobile app..

[jpmens]

Show me the COMMAND line you use to publish that to your MQTT broker. (Obviously without passwords.)

[apppdevv2015]

I just published this and its on mqtt server:

{ "_type": "cmd", "action": "setWaypoints", "waypoints": { "_type": "waypoints", "waypoints": [ { "_type": "waypoint", "tst": 1361636517, "rid": "blaur-utrecht-nl", "desc": "brr Blauw", "rad": 50, "lat": 52.087822392366, "lon": 5.119438515394096 } ] } }

But its not showing in Mobile app

[apppdevv2015]

I used code:

const topic = 'owntracks/user/device/cmd'; // Replace with your topic
// Create MQTT client and connect
const client = mqtt.connect('mqtt server', {
username: 'user',
password: 'pass',
});

// Read the waypoints file
const waypointsFile = 'wp-blau.json';
const waypoints = fs.readFileSync(waypointsFile, 'utf-8');

client.on('connect', () => {
console.log('Connected to MQTT broker');

// Publish the waypoints
client.publish(topic, waypoints, { qos: 1 }, (err) => {
  if (err) {
    console.error('Failed to publish waypoints:', err);
  } else {
    console.log('Waypoints published successfully');
  }
  client.end();
});

});

[apppdevv2015]

This is published on MQTT Server but not showing in mobile

[apppdevv2015]

Hi @jpmens

could you please let know what could be the issue in IOS device

[jpmens]

Don’t harass us please!

1. What is the setting for cmd on your iOS settings?
2. what is the content of subTopic on your iOS settings?
3. which MQTT broker are you using (brand of software)?
4. I asked you to show me the Linux command line with which you demonstrate that what I showed earlier works for you. You’ve not done that.
5. please stop showing me the content of the message that I give you; I know what’s in the Blauw waypoint description
6. show us logs of the MQTT broker at the point the cmd message arrives there
7. show us logs taken on the iOS app for the same time frame

[apppdevv2015]

Apologies Guys, Earlier I was tried the Andriod phone.. I will send you all the details soon

[apppdevv2015]

1. Attached the IOS Screen-shot
2. MQTT Broker : hivemq.cloud
3. MQTT LOG:
   { "_type": "cmd", "action": "setWaypoints", "waypoints": { "_type": "waypoints", "waypoints": [ { "_type": "waypoint", "tst": 13616356
   
   
   
   
   17, "rid": "test-ui", "desc": "Ashwani Blauw", "rad": 50, "lat": 52.087822392366, "lon": 5.119438515394096 } ] } }

[jpmens]

that JSON that you constantly keep pasting is not a log …

The iOS screenshot shows the logfile name. You’ll need to send that to yourself or to us (support@owntracks.org) so we can see what’s IN the file

[apppdevv2015]

org.mqttitude.MQTTitude 2024-07-19--11-10-56-739.log

[jpmens]

in iOS settings, please make sure that in subTopic you see a topic which ends in cmd (I don’t see that from your screenshot)

[apppdevv2015]

do i just need to add " /cmd "

[apppdevv2015]

org.mqttitude.MQTTitude 2024-07-19--11-10-56-739.log

[jpmens]

also you’ve been publishing to a topic called owntracks/user/test/cmd, but in the screenshot it’s called testUser (capital U) and the device name is C30…………

The topic branch used by iOS MUST match the topic you’re publishing to.

[jpmens]

also you’ve been publishing to a topic called owntracks/user/test/cmd, but in the screenshot it’s called User (capital U) and the device name is C30…………

From your log I see you should be publishing to

owntracks/testUser/C30AE8FD-6135-4D6C-AD7B-B6333457ED2E/cmd

[apppdevv2015]

I did this now under SubTopic: owntracks/testUser/device/cmd

[apppdevv2015]

Still not showing under mobile regions

[jpmens]

That’s not what I asked you to do. Listen, this is getting very tedious for me. you are asking for help, and I’m trying to help you understand how to solve the issue. I said the topic to which you should MQTT publish; I did not say change the configuration of your phone.

I cannot keep track of what you’re doing.

I’m going to explain, and then I’ll stop: your program (javascript?) is trying to publish a payload to MQTT with a JSON which iOS will interpret. The phone is connected (hopefully) to a broker and your app to the same broker. If the broker permits, the publish your app does is read by the phone, and the phone will react. The topic to which your app publishes MUST MATCH the topic on which the phone subscribes.

This topic is configured automatically on the phone by setting up a user and a device. By default OwnTracks constructs topics of the form owntracks/user/device and for certain operations adds a branch to that, e.g. /cmd
Without this matching, the phone will never get what the app is publishing.

My reccomendation: Uninstall the iOS app and re-install it. Configure it with a username (e.g. jane) and a device name (e.g. myphone). The phone will then subscribe to owntracks/jane/myphone and owntracks/jane/myphone/cmd

When your app publishes (with QoS>0) the CMD payload to owntracks/jane/myphone/cmd the phone should show the newly received waypoint/region in the list of regions.

[jpmens]

1. no
2. you publish the data the same way you did for iOS, adjusting the topic
3. UTC

[apppdevv2015]

Okay, thanks

1. In Android, i was talking to Import Waypoints feature. Will it work?
2. I have shared the configuration. Can you please check my configuration?

[jpmens]

1. sure it works, just give it a list of waypoints without the cmd bit in it

{
  "_type": "waypoints",
  "waypoints": [
    {
      "_type": "waypoint",
      "tst": 1361636517,
      "rid": "blauw-utrecht-nl",
      "desc": "Restaurant Blauw",
      "rad": 50,
      "lat": 52.087822392366,
      "lon": 5.119438515394096
    }
  ]
}

2. no I cannot check your configuration because I don't know your environment, but what I see from the screenshots looks ok

[apppdevv2015]

Thanks Import file is working fine.. Is there any way for ios device to import the waypoints?

[jpmens]

how often are you going to ask that question? scroll up for the answers, please!!!