Hi

I've done two installs of Mosquitto on raspberry pi, one from repository and one with a docker image. I have installed OwnTracks on 3 iPhones and connected the iPhones with 3 different users.

I can see messages coming from all 3 iPhones and MQTTInspector subscribes to owntracks/+/+ and can see messages from all three users.

But in the OwnTracks app on the 3 phones I don't get a list of friends, it only seems to see the logged in user's messages

In the latest install of Mosquitto I have no user passwords, ACL or TLS to see if I could get it working

My conf file just says:

persistence true
persistence_location /mosquitto/data/
log_dest file /mosquitto/log/mosquitto.log

I have a static IP address for the pi, port forwarding on 1883, and DuckDNS for dynamic dns

Is there any trouble shooting steps that I can take to see why the OwnTracks apps appear to only subscribe to their own user topic?

Or anything obvious in the set up I can check?

Thanks

Last night my OwnTracks auto-upgraded to 7.4, and now it seems to be sending out a long stream of messages to my Mosquitto server.

Here's the trailing snippet of them, but they're all of the same general form:

{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":335,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0001","t":"t","tst":"1426866369","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}
{"cog":264,"batt":"67","lon":"-120.000","acc":"10","vel":0,"vac":4,"lat":"30.0000","t":"t","tst":"1426866382","alt":23,"_type":"location","tid":"NE"}

The lat's weren't changing, but the lon's were only changing in the 4th dp, (values anonymized, but their relative values are correct)

It queued up over 1000 over night, without the phone moving, and then unloaded them when I started the app up this morning. It did this in "chunks", where it would pause in between and the screen had to be touched to get it going again.

Side-bar: It would be handy if these were "batched" into a smaller set of larger "array" messages. I think the round-trips are killing it when you get an opportunity to go online.

I suspect this is what's causing the weird non-responsive UI I saw last night (see Video on Box.net https://app.box.com/s/oyko2x0a363b0at2vdczko0m4i2az6p5). The timestamp on the video is real-time, so you'll get a sense for how the OwnTracks UI is reacting on my phone.

In that vid, you can see that when the App is started, it doesn't respond (No map) until the UI is touched, at which point the backlog counter in the corner starts to change. From then on, only when the UI is touched does this value change (up, or down) and the Map is unresponsive.

Env:

• iPhone 6 on iOS 8.2 (on WiFi)
• Mosquitto version 0.15 (build date 2013-08-23 19:24:40+0000) on Quad-core ARM Odroid C1 (on GigE)
• OwnTracks configured with Port 1883, no TLS, Auth enabled, a custom ClientID & DeviceID, No Remote Cmd (off), Allow Remote Location (on), Update Address Book (on) and ExtendedData (on).
• Topic is owntracks/myuserid/iphone (on iPhone), but I have iPad and Nexus 7 Devices also.

NB: The app is reporting Version 7.4.2 via the Settings UI, but the App Store indicated it updated it to 7.4 last night (Thu Mar 19th, sometime in the afternoon in California)

I was playing with an app called 'today steps' and it has an excellent 'Notification Center widget' and I was thinking that owntracks for iOS could have something similar.

Whereby it lists the friends you follow and next to that it displays the following information. (You would tap to change between each item.)

• suburb/town/city
• distance from you
• last updated

Just an idea, which would require a bit of coding, but something for the future versions.

iOS10, iPhone 5s Phone enters low power mode. Owntracks location reporting stops. Phone is recharged. Low power mode is switched off. Location reporting remains suspended indefinitely, resumes only after reloading Owntracks app.

Hi,

I've set up owntracks to communicate with my own server using the http mode. Update mode is set to "Significant Location Change". But there are no location updates even when I drive with car a longer distance. Opening the app imediatly updates the location and sends it to the server.

The app has the permission to run in background and to always obtain the current location.

Device is a iPhone 7 with iOS 7.2

I have been using OwnTracks for a few years now and it is a great app. I use it to publish my location via http to a home server to track my whereabouts. Ever since I started using the app, every few weeks the connection gets lost. I can fix it by changing the HTTP URL to a faulty one, publish my location, get errors, put back the same URL as there has always been, publish my location et voila: fixed.

This has become a nuissance. Is this a known problem?

I have installed OwnTracks on my iPhone today. To test it, I configured iot.eclipse.org. After some playing around, OwnTracks crashed. I closed the app by swiping it from the open apps screen, uninstalled it, restarted my phone and reinstalled it. Nothing worked. When I open the app, I go to the settings screen, enter the minimally required setup and when I 'Check' the connection, the app crashes again. Running iOS 7.2 on iPhone 4s

Latest settings:

server: test.mosquitto.org port: 1883 tls: off auth: off user: anonymous device: phone

Hi, Working with the above command, would it possible to add desc to the response to the above command? (maybe this is not only for ios) Like location: object lat: 59.42870689075506 lon: 18.005181523421005 name: "wk" desc: "waypoint name" // the current waypoint the device is in or "none" if not inside any

Updated as Dec 30, 2017 I changed the subject & description to be more precise. I believe the issue is from Geoforce not working when the app is in the background. (App post location properly as per significant change mode rule)

Original Post: Hi,

My set up of Owntracks to publish privately to MQTT server (CloudMQTT) used to work well till recently.

Now I found that often Owntracks will not post location to MQTT server anymore.

Do you know why? And how to fix it?

By the way, Location is set as Always /// Background App Refresh = ON

Thanks.

Yesterday I started in switzerland, tracking on IPHONE 4. While within der primaray Gridoperator (swisscom), OWNTRACKS sends "SIGNIFICANT CHANGES" to mqtt SERVER. When changing borders to (mobile Austria or German telekom - Dataroaming is set off), OWNTRACKS started reporting 5 undelivered Messages up to 40 Messages.

I came back to swisscom, hoping OWNTRACKS is now sending all buffered Locations (in germany or austria). But owntracks shows nothing more to deliver the mqtt Server received nothing. So I assume, OWTRACKS withdraws all buffered locations.

Hi,

love Owntracks but have a hard problem. I track some IOS devices but they loose connection mostly when changing from 4G to WLAN or WLAN to 4G. Status then is not connected and it doesn't recover even its on for hours. If I go to settings and back, it reconnects without problem. Looks like if entering settings it disconnects ad reconnect. Would love to see this working! Thank you so much! Greetings.

I have been using Owntracks for about a year on Android and recently started using IOS for one of my devices with details as above.

I have not been able to get Owntracks to report locations unless the APP is active and not in background.

I have tried all the solutions posted that I could find with no luck.

Not sure if this is a device issue (Iphone Xs) or something else. I have attached the current config

config.otrc.txt

I would appreciate any guidance on getting this to work reliably again on IOS?

Thanks Mark

Use case: My ibeacon is pluged into a 12v -> USB adapter in my car. The goal is to let Home Assistant know if I'm in my car. I don't need to know where I am, just that my phone is physically near the ibeacon and then push some version of true/false to mqtt -> Home Assistant.

Here's my current config:

Some problems I've seen recently:

1. Left my office out to my car and started it up. Home Assistant didn't show I was in my car. I opened the iBeacon app and started scanning. The beacon was detected easily. I then opened Owntracks and saw that Owntracks hadn't turned the icon from Blue to Red indicating it wasn't detected. After flipping to the map view and back, it changed red, and then Home Assistnat showed I was in my car. Yay!
2. Drove my car to my office. Got out, turned the car off, walked 100+ft to the door, then up a 5 story elevator. Home Assistant showed I was still in my car. I opened Owntracks and saw that the beacon was still red on the Regions and Map screen. I then opened iBeacon and scanned -- nothing detected (obviously out of range). But OwnTracks didn't pick that up?
3. Drove all the way home, parked my car, went inside. Opened Owntracks to see that the beacon was Red. Opened iBeacon and scanned which didn't find anything (this is expected inside the house) -- but why did owntracks still show that it was "red".

So, there's a variety of conditions in which owntracks appears to not be properly reflecting whether I'm near, or not near, the beacon. However, If I go in and 'fiddle' with it, then eventually it'll update, and send the MQTT event to Home Assistant.

I'm curious why this isn't happening automagically in the background. Is this a limitation of iOS killing the app and being lame?

Thanks!

Running version 16.2.5/en_GB, if I "Create Card", then enter a name and press Save, the app crashes.

If I add a photo before saving, it seems to work fine.

Thank you developer. The Owntracks App is the most power-efficient app I have used among similar open-sources apps. I really like the switch of "significant" and "move", that makes me to choose between accuracy and power-efficiency.

Now that it requires a server-end to work, could you add a pure offline mode, to make it save all the recordings on the phone and export to gpx file, just like the Open GPS Tracker (http://www.merlos.org/iOS-Open-GPX-Tracker/). I like that app but it uses a lot more power since it keeps GPS on all the time.

I may well be doing something wrong.... I have the OT app set up on 2 iPhones and on an Android phone. I'm using them in HTTP mode to report region changes. Android seems to work OK. On iOS, it's reporting lat & long OK, but the Regions do not update. They stay coloured with a red circle in the app even when I've walked well outside of the region, and waited long enough (I've reduced "locatorinterval" to 60 and "LocatorDisplacement" to 15), and done a forced location push. If I alter the lat/long of the region, so that I'm outside it, then it does change the circle to blue, and transmits the correct inregions list over HTTP. I.e. - if I alter the region so that I fall outside it, it works as it should. If I move the phone so that we're outside the region, it fails to update the region status. I can't find the logs in iOS to investigate further - help!