owntracks / ios

OwnTracks' iPhone App

ios

OwnTracks' iPhone App

OwnTracks initially was MQTTitude.

Prepare to Compile and Run

CocoaPods

OwnTracks uses COCOAPODS.

Xcode

Staying in the OwnTracks/ directory, launch xcode:

     % open OwnTracks.xcworkspace

Next, click on the OwnTacks project and you will see two targets, OwnTracks and OwnTracksToday. For each project, go to the General tab.

For the OwnTracks target, set the Bundle Identifier accordingly:

     com.example.OwnTracks

For the OwnTracksToday target, set the Bundle Identifier accordingly:

     com.example.OwnTracks.OwnTracksToday

For the OwnTracks project, go to the Signing and Capabilities tab and set the appropriate team. Then scroll down to App Groups, uncheck group.org.owntracks.OwnTracks, and then click on the + to create your own group, e.g.,

     group.com.example.OwnTracks

Finally, for the OwnTracksToday project, go to the Signing and Capabilities tab, set the appropriate team. Then scroll down to App Groups, uncheck group.org.owntracks.OwnTracks, and check the group you create for the OwnTracks project.

Note that most these changes will result in Xcode creating provision profiles, repairing things, etc. Please take your time and be patient!

With these steps complete, you should be able to compile and run the project.

ios's Issues

Configured waypoints disappear upon upgrade to 6.0

No waypoint events reported by phone since upgrade. I now see all waypoints I had on the device have gone.

Enable import of waypoints

copy of binarybucks/mqttitude#311

[CLOSED] Remind User of undelivered Messages in IOS

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.

0,0 waypoints when hitting + button

I was somehow also able to add a load of 0, 0 waypoints by repeatedly
hitting the + button on the waypoint creation screen ;)

Create geo-fence for non-visited region

copy of binarybucks/mqttitude#310

Link to docs from within the apps

It appears some people install the app before reading the docs (sigh) and before stumbling over @owntracks and owntracks.org (more sigh)

Let us please consider adding a link to the docs page in some prominent spot (probably on the settings page). IIRC (sorry: ENOPOWER) Android app already points to github (somewhere), but I mean the documentation wiki.

Error on return from Set Waypoint with share

Steps to reproduce (7.1.2):

1. Create waypoint
2. Set radius 500 (not tried with others)
3. Share = true
4. Back

Message is not PUBlished. Popup error

Native iPad version

Suggestion: publish retained NULL on friend deletion

(very low prio)

When a friend is swiped away (deleted), it would be nice if the app would publish a null retained message to clear the topic from the broker. (Whether or not the message actually gets to the broker is a question of QoS, but that's not so important, at least not to me.)

cc: @binarybucks for Android

[CLOSED] [iOS] Location publishes cease after losing WIFI connection and don't restart again

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.

URL in Status display isn't a URL

The URL really isn't a URL.

Change URL to something like connection

Considering Background Fetch

In IOS 7 it is possible to wakeup the app in background eventually and perform fetch requests.

This would enable OwnTracks to receive friend's enter/leave messages in background.

Currently, the app does connect and receives updates when it is activated by the user or when a location change is to be published reported only.

Multitasking in IOS 7

Config export

copy of binarybucks/mqttitude#313

[CLOSED] iOS: is this a communications error?

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

ios + owntracks 7.1

I updated to 7.1 and now I am seeing an odd behavior.

When i enter a zone, it appears to send out additional messages about me leaving other zones. Here is a sample. I arrived at work, but it send that I left the starbucks close to my house and left my home zone as well.

{"desc":"Home","tst":"1400079758","acc":"1414","lon":"-82.6612","_type":"location","lat":"27.8785","event":"leave","batt":"35"}
{"desc":"Starbucks at Gulf","tst":"1400079758","acc":"1414","lon":"-82.6612","_type":"location","lat":"27.8785","event":"leave","batt":"35"}
{"desc":"Jason Work","tst":"1400079758","acc":"1414","lon":"-82.6612","_type":"location","lat":"27.8785","event":"enter","batt":"35"}
{"desc":"Home","tst":"1400079760","acc":"1414","lon":"-82.6612","_type":"location","lat":"27.8785","event":"leave","batt":"35"}
{"desc":"Starbucks at Gulf","tst":"1400079760","acc":"1414","lon":"-82.6612","_type":"location","lat":"27.8785","event":"leave","batt":"35"}
{"desc":"Jason Work","tst":"1400079760","acc":"1414","lon":"-82.6612","_type":"location","lat":"27.8785","event":"enter","batt":"35"}

I did not see this type of behavior on 7.0. Is there a setting maybe I need to change?

Create geo-fence for non-visited region

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.

Enable import of waypoints

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.

Invoke navigation to friends location

Niv Gal Waizer wrote via G+:

Feature request : allow to invoke maps to a friend location. This way I can navigate to my friend using Google maps

New Icon

Looks great on my iPad. Thanks Christoph ;)
Is it possible to change the icon of an app? If so, could you add the \new
icon that is on Twitter etc. for the next version?
If you need any special resolution or format I can provide it to you.

iBeacon waypoints shown on map

Somewhere off the coast of Africa, at 0, 0 ;-))

Screenshots avail on request.

This feature could be optimized away...

[CLOSED] [iOS] Connection dies if no subscription value in settings

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.

Too many local notifications

Great app btw.

I am getting a lot of local push notifications from owntracks, every time it sends a message, enters a zone, ect, it pushes a message to my lock screen which is kinda annoying. I did not see a way in the code to turn this off. I'm wondering if there should be a debug switch in settings to filter the normal notifications off and only notify when there is a serious issue.

Geofencing Events Not Detected on iOS7

I am using iOS version 7.0.4 and OwnTracks version 6.1.

I have clicked on one of the reported waypoints and gave it the Description "Home" and the Radius for Region Monitoring of "50". I then enabled the Share option. The waypoint description was then correctly published to the MQTT server. I also then correctly see the geo-fencing circle around the waypoint.

My problem is that when I enter the region, no event is published. Similarly, when I leave the region, no event is published. The color of the waypoint circle also does not update until I restart the application. This is still true even when I manually publish my location and in both move mode and significant changes mode. The app is allowed access to location services and background refresh. Attached is a screenshot showing my current location inside of the geo-fence, but the circle is still blue.

can't set URL on IOS7

Hi there,

it's not possible to set the URL under IOS7 in the owntracks app.

The field just get grey, but no possiblitiy to set something

[CLOSED] iOS MQQtitude TLS connection issues

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?

[CLOSED] iOS 5.4 submits all waypoints on start

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?

Crash with database corruption

copy of binarybucks/mqttitude#259

Friend error ABRecordSetValue (null)

I'm testing some iOS/Android interoperation with the new 7.2 version.

I'm seeing an "Friend error ABRecordSetValue (null)" when I want to clear a assigned contact

• Go to a friend that I had previously assigned a contact to
• Tap the Book icon to assign a new one
• Tap the trash bin icon
• Above error message shows up
• The contact is cleared successfully and I see the bare topic

Depending on the contact null becomes a defined contact <CPRecord 0xdeadbeef ABPerson>

OwnTracks 6.0 is still labelled MQTTitude

App name (as seen in launcher) is still called MQTTitude after installing from app store.

iPad doesn't find app on store

This needs testing: I'm hearing an iPad didn't find Owntracks in the app store:

12:28 JP: and the iPad install didn't work? I've never tried; it is marked as an
                iPhone app iirc
12:28 CUST: jpmens, but it left me confused
12:28  CUST: it is an iphone app 'compatible with ipad'
12:28 CUST: we couldn't find it
12:28 CUST: when i sent her a direct url to the store she could install it fine

[CLOSED] Waypoint is published every time entering/leaving a region

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

OwnTracks dropped support for iOS 6

Not really an issue, just a question...
Wanted to update MQTTitude to OwnTracks, but unfortunately iOS 7 is required for this. Is there a specific reason you do not support iOS 6 anymore? Would there be any drawback setting the deployment target back to iOS 6? :)

waypoints, two questions...

Correct me if I'm wrong n both of these...

1. I noticed in the waypoints part of the wiki that if shared is enabled on your waypoint (geofence) it publishes to the base topic i.e owntrack/matthew/phone as well as owntrack/matthew/iphone/waypoint ? If that is the case, mine is working fine on the base topic owntrack/matthew/phone but i don't see anything coming thru on the other one. owntrack/matthew/iphone/waypoint
2. Can you import waypoints as a remoteconfig file similar to the way you can import the config settings?

iBeacon support for detecting what room you are in.

Future enhancement, for home automation detecting which room u r in....

This is good news and makes it easier to implement....

"As of today, once an app is installed it will “look” for beacons even if your app is shut down or you’ve rebooted your phone."
http://beekn.net/2014/03/apple-ios-7-1-launches-major-ibeacon-improvement/

Just need to build/buy some...

Settings keep getting deleted

This is a screenshot of the error message owntracks is popping up for me. The resulting issue is that my previously saved settings are all gone, and I have to enter them again. The app will work for a day or two and then I'll get the same error and my settings are gone.

[CLOSED] UserID still has auto-correct enabled

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?

[CLOSED] Stale PUBs in 5.4

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 |

friends view.

not sure if this has been covered before, but when you change to friends view, mine shows my current location, one of my friends location and ALL of my past locations.

I thought friends view should just show everyones current locations and no past locations?

[CLOSED] Add iOS app version to status screen

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! :-)

ios, 'will' message not being sent.

I have the will message set in the expert mode settings to the words 'offline'

but i have been monitoring the lwt topic and it doesnt look like it is being sent? or have I missed something?

lwt/matthews-iphone {"tst":"1395381689","_type":"lwt"}

Events being published every time you open app.

v7.1

Not sure if this is the normal, but every time I open the app when I am within a waypoint it will publish a message with the event enter, even if I entered the waypoint hours ago? Seems to happen more often since the upgrade to 7.1

How do you delete a dropped pin from the map?

I can't find an obvious way to delete pins from the map.

Issue enter when pressing PUB within a region?

When the Android up starts afresh and publishes it's location, if it finds itself within a configured geo-fence, it publishes an enter event (with desc) for that region.

Would that be easy for us to do on iOS as well?

Case in point on the openHAB mailing list: people who want to test whether regions are working but don't want to go for a walk ... ;-)

Cosmetic, delete button.

When sliding over to delete a waypoint, delete is partially obscured.

Crash with database corruption

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: :-)

UI feedback

Hi Christoph,

I've gathered a bit of UI feedback for the iOS version (7.1, the other has not made it to my device). Totally scientific tests with some people have shown, that the current UI is not very intuitive to which I have to agree to a certain extend.

Navigation

I think the navigation inside the different views of the app is quite confusing and does not follow the UI guidelines at some instances. The navigation bar indicates a hierarchy that at least for me, is none. After switching between the friends view, the map view and the status view I'm totally lost where a new tap will bring me and the slide animation direction on the friends view doesn't help either.

Getting to the preferences is also quite an adventure. In the status page there's a section about effective settings where nothing happens if I tap on it.

The URL really isn't a URL.

The last error could be merged with the status display. E.g. say "Connected" or "Disconnected - There was an error".

Iconography

Without trying it, I cannot say what the toolbar buttons do when I press them. With some buttons that cycle more modes I'm unsure even after pressing it multiple times.

The launcher Icon is different to those on Twitter etc. However I'm not sure if you already fixed this in the new version.

I suggest the following:

1. Change the toolbar at the bottom of the maps view to a tab bar with three distinct tabs to flatten the view hierarchy (Contacts, Map, Settings).

2. In the navigation bar of the map, show a dedicated action menu as a popover.
   

3. Merge the Status, Settings and Export. Change URL to something like connection and provide the broker connection preferences behind that view. Show Connection status there and/or in the map popover and include possible error conditions. Merge Credits and license in the settings page with version display on the status page and other informational things like the other effective settings. E.g. setup a new "information" section for all those things.

Flatten settings (now there are owntracks app, mqtt conection while mqtt connetion contains the advanced settings of owntracks app, mqtt connection and mqtt).
I get what these sections are supposed to contain but only because I know the inner workings.

What about structuring the preferences like the Android app with a master/detail view on iPads (list left, details right like the native settings app)?

[CLOSED] Other device is republishing my events

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"}

[CLOSED] Publish location does not contain description when leaving/entering region

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

[CLOSED] Friends UI has /waypoint PUBs in it

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 ?

App is being disconnected on quit. New?

Forgive the question, but I have the feeling this is new behaviour. I'm noticing that when I exit the app 7.1.2 (and one prior version) by pressing 'home', the app is disconnected. I noticed, because when I re-enter the app, the connection indicator (correctly) starts off in 'red' mode.

I don't think I saw this earlier.

Mosquitto log:

Received DISCONNECT from jpm-5s             # press HOME


New connection from a.b.c.d on port 8883.    # re-launch app
OpenSSL Error: error:140D9115:SSL routines:SSL_GET_PREV_SESSION:session id context uninitialized
Socket read error on client (null), disconnecting.
New connection from a.b.c.d on port 8883.
New client connected from a.b.c.d as jpm-5s (c0, k45).
Sending CONNACK to jpm-5s (0)
Received DISCONNECT from jpm-5s