JohanKuster
commented
5 years ago Hi,
I cannot help you with this issue, I am not using Homey anymore and I stopped developing or mainting software for it a long time ago. I believe there is a second mqtt client for Homey, please use this software.
Regards, Johan
Verstuurd vanaf mijn iPad
Op 23 dec. 2018 om 01:06 heeft BBEHannes notifications@github.com<mailto:notifications@github.com> het volgende geschreven:
Hello,
I have been a very happy user of MQTT Broker and Owntracks Client on Homay for almost a year. In that time I have had 0 wrong geo location misses. However, starting from this week I have had strange problems. Sometimes I see myself returning home even though I am already home and receive no message when I leave, whilst my partner's phone (in the same car) is correctly showing going out of the Home zone at the exact same time. Not sure what has been updated but I'd appreciate looking into it.
One of the strange issues from the logs (when everyone is at home and has not moved from the couch in time);
Here we see that the geo location is still\already set to "Home"
20181223-00:23:53 getUserArray called 20181223-00:23:57 getLogLines called 20181223-00:24:28 OnMessage called 20181223-00:24:28 received '{"batt":100,"lon":xxxx,"acc":1924,"p":xxxx,"vac":13,"inregions":["Home"],"lat":xxxx,"conn":"w","tst":xxx,"alt":-2,"_type":"location","tid":"br"}' on 'owntracks/Bas/bas' 20181223-00:24:28 We have received a location message 20181223-00:24:28 Set battery percentage for Bas to 100% 20181223-00:24:28 inregions: Home 20181223-00:24:28 region Home 20181223-00:24:43 getUserArray called 20181223-00:24:54 getUserArray called 20181223-00:24:58 getLogLines called 20181223-00:25:58 OnMessage called
\
Then, a couple of minutes later, almost same lon\lat and for a strange reason it starts setting me to "Home" anyway;
20181223-00:31:52 OnMessage called 20181223-00:31:52 received '{"batt":100,"lon":xxxx,"acc":65,"p":xxxx,"vac":10,"inregions":["Home"],"lat":xxxx,"conn":"w","tst":xx,"alt":-2,"_type":"location","tid":"br"}' on 'owntracks/Bas/bas' 20181223-00:31:52 We have received a location message 20181223-00:31:52 Set battery percentage for Bas to 100% 20181223-00:31:52 inregions: Home 20181223-00:31:52 region Home 20181223-00:31:52 isAccurate 20181223-00:31:52 Listener enterGeofence_AC called 20181223-00:31:52 state.topic = owntracks/Bas/bas topic = undefined 20181223-00:31:52 received user Bas trigger user: Bas 20181223-00:31:52 Received Fence = Home trigger fence = Home 20181223-00:31:52 triggerFence = equal 20181223-00:31:52 Listener enterGeofence_AC called 20181223-00:31:52 state.topic = owntracks/Bas/bas topic = undefined 20181223-00:31:52 received user Bas trigger user: Jurjen 20181223-00:33:23 OnMessage called 20181223-00:33:23 received '{"tst":"xx","_type":"lwt"}' on 'owntracks/Bas/bas' 20181223-00:33:30 getLogLines called 20181223-00:33:46 getUserArray called 20181223-00:33:49 getLogLines called
Again, this also has hit and miss when leaving where it doesn't register. It worked flawlessly until this week.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/JohanKuster/homey-mqtt-client/issues/7, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQXSqvL1-nHvL3HCYW5VpW7OFww3Dchwks5u7skFgaJpZM4Zfp9N.
BBEHannes
Hello,
I have been a very happy user of MQTT Broker and Owntracks Client on Homay for almost a year. In that time I have had 0 wrong geo location misses. However, starting from this week I have had strange problems. Sometimes I see myself returning home even though I am already home and another time i see no message when I leave, whilst my partner's phone (in the same car as mine) is correctly showing going out of the Home zone at the exact same time. Not sure what has been updated but I'd appreciate looking into it.
One of the strange issues from the logs (when everyone is at home and has not moved from the couch in time);
Here we see that the geo location is still\already set to "Home"
20181223-00:23:53 getUserArray called 20181223-00:23:57 getLogLines called 20181223-00:24:28 OnMessage called 20181223-00:24:28 received '{"batt":100,"lon":xxxx,"acc":1924,"p":xxxx,"vac":13,"inregions":["Home"],"lat":xxxx,"conn":"w","tst":xxx,"alt":-2,"_type":"location","tid":"br"}' on 'owntracks/Bas/bas' 20181223-00:24:28 We have received a location message 20181223-00:24:28 Set battery percentage for Bas to 100% 20181223-00:24:28 inregions: Home 20181223-00:24:28 region Home 20181223-00:24:43 getUserArray called 20181223-00:24:54 getUserArray called 20181223-00:24:58 getLogLines called 20181223-00:25:58 OnMessage called
\\
Then, a couple of minutes later, almost same lon\lat and for a strange reason it starts setting me to "Home" anyway;
20181223-00:31:52 OnMessage called 20181223-00:31:52 received '{"batt":100,"lon":xxxx,"acc":65,"p":xxxx,"vac":10,"inregions":["Home"],"lat":xxxx,"conn":"w","tst":xx,"alt":-2,"_type":"location","tid":"br"}' on 'owntracks/Bas/bas' 20181223-00:31:52 We have received a location message 20181223-00:31:52 Set battery percentage for Bas to 100% 20181223-00:31:52 inregions: Home 20181223-00:31:52 region Home 20181223-00:31:52 isAccurate 20181223-00:31:52 Listener enterGeofence_AC called 20181223-00:31:52 state.topic = owntracks/Bas/bas topic = undefined 20181223-00:31:52 received user Bas trigger user: Bas 20181223-00:31:52 Received Fence = Home trigger fence = Home 20181223-00:31:52 triggerFence = equal 20181223-00:31:52 Listener enterGeofence_AC called 20181223-00:31:52 state.topic = owntracks/Bas/bas topic = undefined 20181223-00:31:52 received user Bas trigger user: Jurjen 20181223-00:33:23 OnMessage called 20181223-00:33:23 received '{"tst":"xx","_type":"lwt"}' on 'owntracks/Bas/bas' 20181223-00:33:30 getLogLines called 20181223-00:33:46 getUserArray called 20181223-00:33:49 getLogLines called
Again, this also has hit and miss when leaving where it doesn't register. It worked flawlessly until this week.