[CLOSED] Other device is republishing my events about android HOT 6 CLOSED

Comment by binarybucks from Saturday Jan 25, 2014 at 13:45 GMT

I'll check if it's my broker

Mit freundlichen Grüßen / With kind regards
Alexander Rust
--Sent from mobile
Am 25.01.2014 14:43 schrieb "JP Mens" [email protected]:

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

—
Reply to this email directly or view it on GitHubhttps://github.com/binarybucks/mqttitude/issues/303
.

from android.

Comment by jpmens from Saturday Jan 25, 2014 at 13:47 GMT

It isn't. This happened before you set up your bridge.

from android.

Comment by jpmens from Saturday Jan 25, 2014 at 13:48 GMT

@ckrey Here's another example.

00401 2014-01-25 12:03:39 mqttitude/yak/4s {"acc": "65", "_type": "location", "lon": "y.476563", "batt": "30", "lat": "x.034417", "tst": "1390647819", "event": "enter", "desc": "$HoMe"}
00402 2014-01-25 12:07:32 mqttitude/jpm/5s {"acc": "165", "_type": "location", "lon": "y.476438", "batt": "90", "lat": "x.034474", "tst": "1390648052", "event": "enter", "desc": "$HoMe"}
00403 2013-12-01 15:33:45 mqttitude/jpm/5s {"acc": "10", "rad": "1200", "lon": "y.476609", "_type": "waypoint", "batt": "90", "lat": "x.034438", "tst": "1385908425", "desc": "$HoMe"}

Interestingly, the timestamps are the wrong way around this time.

And you can believe me: she wouldn't have entered a waypoint called $HoMe ;-)

from android.

Comment by jpmens from Saturday Jan 25, 2014 at 13:59 GMT

@ckrey Another hint: this occurred yesterday morning: a friend who uses my broker approached the company we're both working at, and I recognized a PUB of his containing my waypoint description.

It's as though the iPhone stores the waypoints/geo-fences but doesn't differentiate (when recognizing in/out of a fence) whom the waypoint actually belongs to, and thus just publishes it as its own.

Do I get a prize? :-)

from android.

Comment by ckrey from Saturday Jan 25, 2014 at 14:28 GMT

@jpmens I found the bug two days ago already. It's fixed. And I think this is a trigger to upgrade to 5.6

from android.

Comment by ckrey from Saturday Jan 25, 2014 at 14:30 GMT

Closed with https://github.com/binarybucks/mqttitude/commit/3039eec5abeb6ef8abdac2284d6da54985dff438

from android.