OwnTracks Android App
Home Page: http://owntracks.org
License: Eclipse Public License 1.0
OwnTracks allows you to keep track of your own location. You can build your private location diary or share it with your family and friends. OwnTracks is open-source and uses open protocols for communication so you can be sure your data stays secure and private.
To get started, install OwnTracks on your smartphone. Afterwards you can connect it to an existing server straight away or follow the guide in our Documentation to set up your own.
![dependabot-preview[bot] avatar](https://avatars.githubusercontent.com/in/2141?v=4 "dependabot-preview[bot]")
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot]")
On the connections/preferences screen, I cannot click the Connect button as it is greyed out. I do not have a username or password on my server, but it seems that if I enter some text into those fields then the connect button works.
On 0.4.16 Android (nexus 4 4.4.2) after migrating pub/sub topic to the new base topic
Enter/Leave Events are not firing correctly.
By modifying a shared waypoint the message is published correctly to the topic.
node-red flow to help testing the issue:
[{"id":"935915de.8aaf08","type":"mqtt-broker","broker":"10.0.1.10","port":"1883"},{"id":"3e2f6060.7495a","type":"mqtt in","name":"owntracks geofence","topic":"owntracks/+/+/waypoints","broker":"935915de.8aaf08","x":158,"y":153,"z":"b4348802.41dcf","wires":[["2c9a5ef1.d3c942","a39036aa.cafa18"]]},{"id":"2c9a5ef1.d3c942","type":"debug","name":"","active":true,"complete":false,"x":503,"y":153,"z":"b4348802.41dcf","wires":[]},{"id":"46e9a84c.1ae098","type":"pushover","name":"","title":"Node-Red Message","message":"","priority":"-1","x":504,"y":277,"z":"b4348802.41dcf","wires":[]},{"id":"a39036aa.cafa18","type":"function","name":"","func":"// The received message is stored in 'msg'\n// It will have at least a 'payload' property:\n// console.log(msg.payload);\n// The 'context' object is available to store state\n// between invocations of the function\n// context = {};\nvar now = Date();\ndata = JSON.parse(msg.payload);\n\nmessage = "Event: " + data.event + " Location: " + data.desc\n\n\nmsg.payload = message;\n\nreturn msg;","outputs":1,"x":359,"y":277,"z":"b4348802.41dcf","wires":[["46e9a84c.1ae098"]]}]
Issue by ckrey from Wednesday Jan 15, 2014 at 10:47 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/268
This causes unnecessary network usage.
Waypoints will be published when created or updated only.
Waypoints will always be published without the retain-flag set so they don't overwrite retained locations
Yesterday's changes miss a call to setShared. Fogot that one yesterday.
Issue by ijwhite from Thursday Nov 28, 2013 at 21:31 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/216
On the samsung Galaxy S2:
Galaxy S4 is fine.
Issue by sumnerboy12 from Monday Jan 13, 2014 at 05:56 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/263
I cleared the subscription config on my wife's iPhone since I only want Mqttitude to send enter/leave events and don't care about any other messages (also set to manual mode).
However once I did this all I saw on my broker were LWT messages from her phone. The connection details were ok, since the LWT publishes were coming through, but any time I entered or left a region or tried to manually publish I just got a LWT.
When attempting a manual publish the connection status icon flashed yellow and then went red. Checking the status page showed a 'NSOSStatusErrorDomain -9806' error.
I tried all sorts of different things and was about to log the bug, when I remembered removing the subscription settings. I added it back and voila - everything started working again!
So it seems with an empty subscription value, the app fails to send any location publishes, even though it can connect ok.
This is only on iOS, my Android phone seems fine with an empty subscription value.
Issue by jpmens from Friday Jan 10, 2014 at 18:36 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/259
version 5.4 running on iOS 7 on an iPhone 4
After restart of app, settings are gone:
Exiting the app displays a new popup I hadn't seen before: :-)
Issue by ckrey from Tuesday Jan 28, 2014 at 13:26 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/307
As you know, in IOS the App does not run in background, but is woken up by IOS only if location updates occur.
This may lead to the situation where location messages are produced but not transmitted because the app is not woken up after a temporary network problem (server down, transition from Wifi to mobile, ... you name it).
To solve this problem, the app will now (>= version 5.6) set an alarm like the calendar or reminder app to remind the user of the fact.
First notice of this as I'm still having big trouble with #33.
Denied PUBLISH from jpm-nex4 (d0, q1, r0, m146, '$SYS/keepalive', ... (1 bytes))
I note the code contains
src/st/alr/mqttitude/services/ServiceBroker.java
770: MqttTopic topic = mqttClient.getTopic("$SYS/keepalive");
What's that for?
I'm asking, obviously, because I can't get it to ticker anything ...
Issue by jpmens from Thursday Jan 16, 2014 at 12:53 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/269
Had my phone (jpm/5s) in my pocket until 13:34, when I launched the app. I know that some "friends" had published locations until then (watching broker).
Friends list didn't show the updates, i.e. old timestamps on the Friends list.
I pressed PUB on the app (and my current location was published). I then returned to the Friends list to see new timestamps, i.e. updated locations.
Help me understand this, please.
MQTT communication works, as can be seen in the attached broker log. PUBs were transmitted during the evening of the 15th, and those arrived at the broker. However, PUBs by friends to the same broker never reached the phone, at least they weren't ACKed until 13:34:28, just after I explicitly PUB.
Is this a bug?
Jan 15 20:52:13 Received PUBLISH from jpm-5s (d0, q2, r1, m99, 'mqttitude/jpm/5s', ... (133 bytes))
Jan 15 20:52:13 Sending PUBREC to jpm-5s (Mid: 99)
Jan 15 20:52:13 Received PUBREL from jpm-5s (Mid: 99)
Jan 15 20:52:13 Sending PUBCOMP to jpm-5s (Mid: 99)
Jan 15 20:52:13 Sending PUBLISH to jpm-5s (d0, q1, r0, m4207, 'mqttitude/jpm/5s', ... (133 bytes))
Jan 15 20:52:13 Received PUBACK from jpm-5s (Mid: 4207)
Jan 15 20:52:30 Received PUBLISH from jpm-5s (d0, q2, r1, m100, 'mqttitude/jpm/5s', ... (145 bytes))
Jan 15 20:52:30 Sending PUBREC to jpm-5s (Mid: 100)
Jan 15 20:52:30 Received PUBREL from jpm-5s (Mid: 100)
Jan 15 20:52:30 Sending PUBCOMP to jpm-5s (Mid: 100)
Jan 15 20:52:30 Sending PUBLISH to jpm-5s (d0, q1, r0, m4208, 'mqttitude/jpm/5s', ... (145 bytes))
Jan 15 20:52:30 Received PUBACK from jpm-5s (Mid: 4208)
Jan 15 20:52:35 Received DISCONNECT from jpm-5s
Jan 15 21:41:06 New client connected from xxxxxx as jpm-5s (c0, k45).
Jan 15 21:41:06 Sending CONNACK to jpm-5s (0)
Jan 15 21:41:06 Received PUBLISH from jpm-5s (d0, q2, r1, m101, 'mqttitude/jpm/5s', ... (149 bytes))
Jan 15 21:41:06 Sending PUBREC to jpm-5s (Mid: 101)
Jan 15 21:41:06 Received PUBLISH from jpm-5s (d0, q2, r1, m102, 'mqttitude/jpm/5s', ... (145 bytes))
Jan 15 21:41:06 Sending PUBREC to jpm-5s (Mid: 102)
Jan 15 21:41:06 Received PUBREL from jpm-5s (Mid: 101)
Jan 15 21:41:06 Sending PUBCOMP to jpm-5s (Mid: 101)
Jan 15 21:41:06 Sending PUBLISH to jpm-5s (d0, q1, r0, m4209, 'mqttitude/jpm/5s', ... (149 bytes))
Jan 15 21:41:06 Received PUBREL from jpm-5s (Mid: 102)
Jan 15 21:41:06 Sending PUBCOMP to jpm-5s (Mid: 102)
Jan 15 21:41:06 Sending PUBLISH to jpm-5s (d0, q1, r0, m4210, 'mqttitude/jpm/5s', ... (145 bytes))
Jan 15 21:41:06 Received PUBACK from jpm-5s (Mid: 4209)
Jan 15 21:41:06 Received PUBACK from jpm-5s (Mid: 4210)
Jan 15 21:41:14 Received DISCONNECT from jpm-5s
Jan 15 21:55:23 New client connected from xxxxxx as jpm-5s (c0, k45).
Jan 15 21:55:23 Sending CONNACK to jpm-5s (0)
Jan 15 21:55:23 Received PUBLISH from jpm-5s (d0, q2, r1, m103, 'mqttitude/jpm/5s', ... (99 bytes))
Jan 15 21:55:23 Sending PUBREC to jpm-5s (Mid: 103)
Jan 15 21:55:24 Received PUBREL from jpm-5s (Mid: 103)
Jan 15 21:55:24 Sending PUBCOMP to jpm-5s (Mid: 103)
Jan 15 21:55:24 Sending PUBLISH to jpm-5s (d0, q1, r0, m4211, 'mqttitude/jpm/5s', ... (99 bytes))
Jan 15 21:55:24 Received PUBACK from jpm-5s (Mid: 4211)
Jan 15 21:55:31 Received DISCONNECT from jpm-5s
Jan 15 22:24:51 New client connected from xxxxxx as jpm-5s (c0, k45).
Jan 15 22:24:51 Sending CONNACK to jpm-5s (0)
Jan 15 22:24:51 Received PUBLISH from jpm-5s (d0, q2, r1, m104, 'mqttitude/jpm/5s', ... (99 bytes))
Jan 15 22:24:51 Sending PUBREC to jpm-5s (Mid: 104)
Jan 15 22:24:52 Received PUBREL from jpm-5s (Mid: 104)
Jan 15 22:24:52 Sending PUBCOMP to jpm-5s (Mid: 104)
Jan 15 22:24:52 Sending PUBLISH to jpm-5s (d0, q1, r0, m4212, 'mqttitude/jpm/5s', ... (99 bytes))
Jan 15 22:24:53 Received PUBACK from jpm-5s (Mid: 4212)
Jan 15 22:24:57 Received DISCONNECT from jpm-5s
Jan 15 22:31:46 New client connected from xxxxxx as jpm-5s (c0, k45).
Jan 15 22:31:46 Sending CONNACK to jpm-5s (0)
Jan 15 22:31:47 Received PUBLISH from jpm-5s (d0, q2, r1, m105, 'mqttitude/jpm/5s', ... (99 bytes))
Jan 15 22:31:47 Sending PUBREC to jpm-5s (Mid: 105)
Jan 15 22:31:47 Received PUBREL from jpm-5s (Mid: 105)
Jan 15 22:31:47 Sending PUBCOMP to jpm-5s (Mid: 105)
Jan 15 22:31:47 Sending PUBLISH to jpm-5s (d0, q1, r0, m4213, 'mqttitude/jpm/5s', ... (99 bytes))
Jan 15 22:31:49 Received PUBACK from jpm-5s (Mid: 4213)
Jan 15 22:31:49 Socket error on client jpm-5s, disconnecting.
Jan 15 22:39:15 New client connected from xxxxxx as jpm-5s (c0, k45).
Jan 15 22:39:15 Sending CONNACK to jpm-5s (0)
Jan 15 22:39:15 Sending PUBLISH to jpm-5s (d0, q1, r0, m4214, 'mqttitude/jpm/5s', ... (34 bytes))
Jan 15 22:39:15 Received PUBLISH from jpm-5s (d0, q2, r1, m106, 'mqttitude/jpm/5s', ... (98 bytes))
Jan 15 22:39:15 Sending PUBREC to jpm-5s (Mid: 106)
Jan 15 22:39:15 Received PUBACK from jpm-5s (Mid: 4214)
Jan 15 22:39:15 Received PUBREL from jpm-5s (Mid: 106)
Jan 15 22:39:15 Sending PUBCOMP to jpm-5s (Mid: 106)
Jan 15 22:39:15 Sending PUBLISH to jpm-5s (d0, q1, r0, m4215, 'mqttitude/jpm/5s', ... (98 bytes))
Jan 15 22:39:15 Received PUBACK from jpm-5s (Mid: 4215)
Jan 15 22:39:21 Received DISCONNECT from jpm-5s
Jan 16 07:06:30 New client connected from xxxxxx as jpm-5s (c0, k45).
Jan 16 07:06:30 Sending CONNACK to jpm-5s (0)
Jan 16 07:06:30 Sending PUBLISH to jpm-5s (d0, q1, r0, m4216, 'mqttitude/dt27/iphone5c', ... (99 bytes))
Jan 16 07:06:31 Received PUBLISH from jpm-5s (d0, q2, r1, m107, 'mqttitude/jpm/5s', ... (137 bytes))
Jan 16 07:06:31 Sending PUBREC to jpm-5s (Mid: 107)
Jan 16 07:06:31 Received PUBLISH from jpm-5s (d0, q2, r1, m108, 'mqttitude/jpm/5s', ... (132 bytes))
Jan 16 07:06:31 Sending PUBREC to jpm-5s (Mid: 108)
Jan 16 07:06:31 Received PUBACK from jpm-5s (Mid: 4216)
Jan 16 07:06:31 Received PUBREL from jpm-5s (Mid: 107)
Jan 16 07:06:31 Sending PUBCOMP to jpm-5s (Mid: 107)
Jan 16 07:06:31 Sending PUBLISH to jpm-5s (d0, q1, r0, m4217, 'mqttitude/jpm/5s', ... (137 bytes))
Jan 16 07:06:32 Received PUBREL from jpm-5s (Mid: 108)
Jan 16 07:06:32 Sending PUBCOMP to jpm-5s (Mid: 108)
Jan 16 07:06:32 Sending PUBLISH to jpm-5s (d0, q1, r0, m4218, 'mqttitude/jpm/5s', ... (132 bytes))
Jan 16 07:06:32 Received PUBACK from jpm-5s (Mid: 4217)
Jan 16 07:06:33 Received PUBACK from jpm-5s (Mid: 4218)
Jan 16 07:06:34 Received DISCONNECT from jpm-5s
APP Launched now!
Jan 16 13:34:27 New client connected from xxxxxx as jpm-5s (c0, k45).
Jan 16 13:34:27 Sending CONNACK to jpm-5s (0)
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4219, 'mqttitude/xal/y300', ... (113 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4220, 'mqttitude/yak/4s', ... (34 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4221, 'mqttitude/xal/y300', ... (115 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4222, 'mqttitude/xal/y300', ... (114 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4223, 'mqttitude/yak/4s', ... (99 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4224, 'mqttitude/yak/4s', ... (128 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4225, 'mqttitude/yak/4s', ... (96 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4226, 'mqttitude/xal/y300', ... (115 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4227, 'mqttitude/xal/y300', ... (115 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4228, 'mqttitude/xal/y300', ... (115 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4229, 'mqttitude/xal/y300', ... (113 bytes))
Jan 16 13:34:27 Sending PUBLISH to jpm-5s (d0, q1, r0, m4230, 'mqttitude/yak/4s', ... (34 bytes))
Jan 16 13:34:28 Received PUBLISH from jpm-5s (d0, q2, r1, m109, 'mqttitude/jpm/5s', ... (96 bytes))
Jan 16 13:34:28 Sending PUBREC to jpm-5s (Mid: 109)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4219)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4220)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4221)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4222)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4223)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4224)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4225)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4226)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4227)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4228)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4229)
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4230)
Jan 16 13:34:28 Received PUBREL from jpm-5s (Mid: 109)
Jan 16 13:34:28 Sending PUBCOMP to jpm-5s (Mid: 109)
Jan 16 13:34:28 Sending PUBLISH to jpm-5s (d0, q1, r0, m4231, 'mqttitude/jpm/5s', ... (96 bytes))
Jan 16 13:34:28 Received PUBACK from jpm-5s (Mid: 4231)
Jan 16 13:35:14 Received PINGREQ from jpm-5s
Jan 16 13:35:14 Sending PINGRESP to jpm-5s
Jan 16 13:35:21 Received DISCONNECT from jpm-5s
Test wether Android will connect to a TLS v1.2 broker.
Issue by jpmens from Thursday Jan 30, 2014 at 17:21 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/310
Bryan Boyd just asked on Twitter:
any way to create a geofence at any location, without having published at the location previously?
This is possible on Android, but not on iOS. Maybe we could think about that as a feature request.
Just a cosmetic issue but should show something as "Not configured" instead.
Issue by sumnerboy12 from Tuesday Jan 14, 2014 at 06:36 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/266
Not sure what exactly is going on here but since the latest version on iOS I have noticed that when the phone moves out of my home WIFI range and onto 3G, location publishes stop - all kinds. Even when the phone arrives home and goes back on WIFI nothing happens.
But if I then manually hit the publish button in the app (blue pin) then all of a sudden I get a load of messages dumped to my broker - enter/leave events for home, and for another region I have configured for work.
This used to work on the previous version.
Today I've noticed a missing geofence event.
Looking at the notifications on the phone the reported status was Err:Timeout | Connected
Since I use mqttwarn to push notifications I've double checked the log and the last notification pushed is the relative prior "Leave" event.
These are my settings right now:
Publish Qos: 1
Locator Displacement: 100
Locator Interval: 2
Location Background accuracy: Balanced Power
Location Foreground accuracy: High Power
Issue by jpmens from Friday Jan 03, 2014 at 09:39 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/246
I see 5.4 PUBlishes all stored waypoints on startup. Didn't we decide against that?
in prefs/Connection I see "Error: java.lang.illegalArgumentException" (before configuring connection parameters).
Other than that, everything looks very good! Congrats!
Issue by therealprologic from Friday Jan 03, 2014 at 05:54 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/245
Not sure if this is a bug or mis-configuration but I'm not able to get the IOS client connected and see this error on the broker side:
1388728246: New connection from 10.0.0.1 on port 8883.
1388728246: OpenSSL Error: error:140D9115:SSL routines:SSL_GET_PREV_SESSION:session id context uninitialized
1388728246: Socket read error on client (null), disconnecting.
Any ideas?
Issue by ckrey from Saturday Jan 04, 2014 at 14:04 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/251
with 5.4, description is missing
in 0.4.21
ActivityMain.java:599st.alr.mqttitude.ActivityMain$MapFragment.handleHandlerMessage
StaticHandler.java:19st.alr.mqttitude.support.StaticHandler.handleMessage
Issue by jpmens from Friday Jan 03, 2014 at 11:10 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/248
Can that be disabled?
in 0.4.18 when click on "Donate Bitcoins". (!?!)
Issue by jpmens from Thursday Jan 30, 2014 at 18:04 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/311
As discussed on the ML: we'll enable import of waypoints from a file (.mqtw) (MQTTitude Waypoints) similarly to import of configurations
Waypoint export will not be required, as these are (mostly anyway) published to the back-end from which they can be exported.
Issue by jpmens from Thursday Jan 30, 2014 at 18:04 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/311
As discussed on the ML: we'll enable import of waypoints from a file (.mqtw) (MQTTitude Waypoints) similarly to import of configurations
Waypoint export will not be required, as these are (mostly anyway) published to the back-end from which they can be exported.
Issue by jpmens from Tuesday Jan 21, 2014 at 09:28 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/292
When a friend publishes (shares) a waypoint, this is done on .../waypoint as we recently discussed. What then obviously happens, is that iPhone considers these PUBs to be "a new friend" ;-)
This isn't a bug (actually could even be considered a feature -- waypoints seen separately from normal location reports) and, apart from ignoring those (subscribe to mqttitude/+/+ instead of to mqttitude/#) I can't think of a clean way to hide them, except by ignoring _type=waypoint in the Friends list.
This screen shot shows what I mean:
Thoughts, @ckrey ?
Issue by jpmens from Tuesday Jan 07, 2014 at 08:28 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/252
Possibly related to #249, #246, and #240
Upon opening the app this morning, I noticed the progres bar at bottom was "half full". It drained after a few seconds, and the back-end got this:
mqttitude/jpm/5s {"tst":"1388991216","acc":"165","lon":"yy.529943","_type":"location","lat":"xx.023829","event":"leave","batt":"80"}
mqttitude/jpm/5s {"rad":"1200","desc":"$HoMe","tst":"1385908425","acc":"10","lon":"yy.476609","_type":"waypoint","lat":"xx.034438","batt":"80"}
mqttitude/jpm/5s {"tst":"1388991216","lat":"xx.023829","_type":"location","lon":"yy.529943","acc":"165","batt":"80"}
mqttitude/jpm/5s {"tst":"1388994429","lat":"xx.031703","_type":"location","lon":"yy.502123","acc":"165","batt":"80"}
mqttitude/jpm/5s {"tst":"1388995333","acc":"50","lon":"yy.478519","_type":"location","lat":"xx.034858","event":"enter","batt":"80"}
mqttitude/jpm/5s {"rad":"1200","desc":"$HoMe","tst":"1385908425","acc":"10","lon":"yy.476609","_type":"waypoint","lat":"xx.034438","batt":"80"}
mqttitude/jpm/5s {"tst":"1388995333","lat":"xx.031703","_type":"location","lon":"yy.502123","acc":"165","batt":"80"}
mqttitude/jpm/5s {"tst":"1388995333","lat":"xx.034837","_type":"location","lon":"yy.478513","acc":"10","batt":"80"}
mqttitude/jpm/5s {"tst":"1389077847","lat":"xx.034837","_type":"location","lon":"yy.478513","acc":"10","batt":"60"}
mqttitude/jpm/5s {"tst":"1389077877","lat":"xx.034452","_type":"location","lon":"yy.476525","acc":"10","batt":"60"}
The first payload is dated yesterday morning (Mon Jan 6 07:53:36 2014)
The back-end confirms this (note the ids)
mysql> select id, tst from location where username = 'jpm' and device = '5s' order by tst;
| 10726 | 2014-01-06 06:53:36 |
| 10724 | 2014-01-06 06:53:36 |
| 10727 | 2014-01-06 07:47:09 |
| 10728 | 2014-01-06 08:02:13 |
| 10730 | 2014-01-06 08:02:13 |
| 10731 | 2014-01-06 08:02:13 |
| 10732 | 2014-01-07 06:57:27 |
| 10733 | 2014-01-07 06:57:57 |
Using v0.4.19 on HTC One.
Connecting to my broker ok.
But the app is not reporting/showing my current location and when I look at the notification tray on my phone it says OwnTracks - Google Play Services are not available.
This was all working fine previously and I haven't changed anything on my phone (AFAIK).
Issue by jpmens from Saturday Jan 25, 2014 at 13:43 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/303
I've been noticing this for a few days, and I'm trying to track it down. (both devices: iOS with 5.5 on them)
It seems to me as though my ENTER/LEAVE events are being republished by my wife's device. I have verified that her phone does NOT have this waypoint set up. Even so, my (5s) events are sort-of republished as hers (4s).
by "sort-of" I mean the event and desc are being copied in. Her tst and location are correct for her device.
00376 2014-01-25 10:34:41 mqttitude/jpm/5s {"acc": "65", "_type": "location", "lon": "y.532743", "batt": "95", "lat": "x.018992", "tst": "1390642481", "event": "leave", "desc": "Ratsgymnasium"}
00377 2013-12-19 12:59:41 mqttitude/jpm/5s {"acc": "10", "rad": "150", "lon": "y.528701", "_type": "waypoint", "batt": "95", "lat": "x.019256", "tst": "1387454381", "desc": "Ratsgymnasium"}
00378 2014-01-25 10:36:11 mqttitude/jpm/5s {"acc": "65", "_type": "location", "lon": "y.532747", "batt": "95", "lat": "x.019103", "tst": "1390642571"}
00379 2014-01-25 10:36:54 mqttitude/yak/4s {"acc": "65", "_type": "location", "lon": "y.532368", "batt": "35", "lat": "x.019925", "tst": "1390642614", "event": "leave", "desc": "Ratsgymnasium"}
in 0.4.21
ActivityMain.java:224st.alr.mqttitude.ActivityMain$FragmentHandler.removeAll
ActivityMain.java:357st.alr.mqttitude.ActivityMain.onDestroy
0.4.16 here.
Opened app which said "Location reported", but nothing was being published. Tried multiple times. Rebooted nexus4 (that has helped previously); nothing doing.
Mosquitto log shows
Feb 6 10:57:35 New client connected from xx.yy.aa.bb as jpm-nex4 (c0, k900).
Feb 6 10:57:35 Sending CONNACK to jpm-nex4 (0)
Feb 6 10:57:35 Sending PUBLISH to jpm-nex4 (d1, q1, r0, m4262, 'mqttitude/jpm/5s', ... (97 bytes))
Feb 6 10:57:35 Sending PUBLISH to jpm-nex4 (d1, q1, r0, m4263, 'mqttitude/jpm/5s', ... (97 bytes))
Feb 6 10:57:35 Sending PUBREC to jpm-nex4 (Mid: 148)
Feb 6 10:57:35 Sending PUBREC to jpm-nex4 (Mid: 152)
Feb 6 10:57:35 Received SUBSCRIBE from jpm-nex4
Feb 6 10:57:35 #011mqttitude/+/+ (QoS 1)
Feb 6 10:57:35 jpm-nex4 1 mqttitude/+/+
Feb 6 10:57:35 Sending SUBACK to jpm-nex4
Feb 6 10:57:35 Socket read error on client jpm-nex4, disconnecting.
with appropriate lwt being published by the broker.
After, oh, about 10 attempts, things back to normal.
Issue by jpmens from Wednesday Jan 22, 2014 at 07:47 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/300
I know this sounds stupid, and it may be, but I always have a devil of a time remembering where to find iOS app versions, quite apart from the fact that when I do finally stumble over where they are, it takes ages for the OS to list all apps.
Can we take the MQTTitude version and stick it on the status screen? That would make people's lives easier ... (mine at least! :-)
"est opus, quod upgraded, quod patrarat" (courtesey of google translate…)
i used to be able to have a username with 36 characters, and i used to be able to set the clientID. both of these options seem to have gone away…
ouch. good thing i have both an android and an iOS phone (-;
Since the last update I have noticed my enter/leave events are being published without any waypoint description/name.
I thought we'd fixed this ... Date is formatted at YYYY-MM-D (single digit today)
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.