OH1 OwnTracks... not getting anywhere

Have you tried to do what I did in the mqttitude.conf in order for it to pick up the configuration changes?

I removed the values (commenting them out is not the same). I ended up with a mqttitude.conf that only contains the following:

home.lat=
home.lon=
geofence=

Be aware you are on OH 2 and I am on OH1 = different binding versions.
I did the mosquitto item and it worksā€¦
ā€¦ and have no entries related to mqttitude in the openhab.conf
But why not; will try the empty entries :slight_smile:

@ben_jones12: donā€™t stress about it; I feel youā€™ve done the best you couldā€¦
sometimes there things beyond what we seeā€¦

OK, added the mqttitude section in openhab.conf with uncommented parameters and leaving them ā€˜emptyā€™ā€¦ result:

after restart with mqttitude empty values
2017-01-18 10:32:47.913 [INFO ] [.io.transport.mqtt.MqttService] - MQTT Service initialization completed.
2017-01-18 10:32:47.918 [INFO ] [o.i.t.m.i.MqttBrokerConnection] - Starting MQTT broker connection 'mymosquitto'
2017-01-18 10:33:07.715 [DEBUG] [.m.internal.MqttitudeActivator] - Mqttitude binding has been started.
2017-01-18 10:33:07.777 [DEBUG] [.b.m.internal.MqttitudeBinding] - Registering Mqttitude consumer for owntracks/owntracks/maxg-iphone/event (on mosquitto)
2017-01-18 10:33:07.780 [DEBUG] [.b.m.internal.MqttitudeBinding] - Activating Mqttitude binding
2017-01-18 10:33:07.785 [DEBUG] [.b.m.internal.MqttitudeBinding] - Mqttitude binding configuration updated, no 'home' location specified. All item bindings must be configured with a <region>.
2017-01-18 10:33:07.792 [DEBUG] [.b.m.internal.MqttitudeBinding] - Unregistering Mqttitude consumer for owntracks/owntracks/maxg-iphone/event (on mosquitto)
2017-01-18 10:33:07.802 [DEBUG] [.b.m.internal.MqttitudeBinding] - Registering Mqttitude consumer for owntracks/owntracks/maxg-iphone/event (on mosquitto)
2017-01-18 10:33:08.974 [WARN ] [o.p.m.i.MqttPersistenceService] - mqtt-persistence:broker
2017-01-18 10:33:08.975 [WARN ] [o.p.m.i.MqttPersistenceService] - mqtt-persistence:topic
2017-01-18 10:33:08.977 [WARN ] [o.p.m.i.MqttPersistenceService] - mqtt-persistence:message

msoquitto log:

1484699546: Socket error on client openhab, disconnecting.
1484699568: New connection from 127.0.0.1 on port 1883.
1484699568: New client connected from 127.0.0.1 as openhab (c1, k60).
1484699760: New connection from ::1 on port 1883.
1484699760: New client connected from ::1 as mosqpub/14933-rpiautoma (c1, k60).
1484699760: Client mosqpub/14933-rpiautoma disconnected.
1484699793: New connection from ::1 on port 1883.

ā€¦ in essence no change, and no TRACE messages or further DEBUG messages when publishing the owntracks messagesā€¦

I say: letā€™s give it a restā€¦ and I do Plan B :slight_smile:

Hang on - your item binding is using mosquitto as the broker name, but it looks like the MQTT binding is named mymosquitto in your log above?

1 Like

I do not understand the inner workings of OH or mqttā€¦ but the mosquitto.log shows and entry at epoch 1484699760 (18 January 2017 10:36:00 GMT+10:00) connecting and disconnecting a mosqoub on rpiAutomationā€¦ could this a problem.
I did not define this name; so it must be auto assigned??
Is this relevant?

Can you tryā€¦

Switch   GeoLoc_MaxHome		"Max @ Home [%s]"		{mqttitude="mymosquitto:owntracks/owntracks/maxg-iphone/event:Home"}

Wellā€¦ we crossed postsā€¦ and I did it again; embarrassed myself to the max!
When I noted the entry in the mosquitto.log I went checking; I usually copy existing working bits and modify them (to avoid typos); the entries were:

Switch   GeoLoc_MaxHome		"Max @ Home [%s]"		{mqttitude="mosquitto:owntracks/owntracks/maxg-iphone/event:Home"}
//String mqttitudeTest "mqttitudeTest [%s]"			{mqtt="<[mymosquitto:owntracks/owntracks/maxg-iphone/event:state:default]"}

and should be

Switch   GeoLoc_MaxHome		"Max @ Home [%s]"		{mqttitude="**my**mosquitto:owntracks/owntracks/maxg-iphone/event:Home"}
//String mqttitudeTest "mqttitudeTest [%s]"			{mqtt="<[mymosquitto:owntracks/owntracks/maxg-iphone/event:state:default]"}

as usual, copying these to the other itesm home2 home3 we had at the beginning, I copied the mistake, hence the thing does not work.

I do apologise, and at the same time thank you @ben_jones12 in particular!
The learning: go with a comb over each word (literally) before posting!

Just to state the obvious for the record: mqttitude works!

Happy days! And donā€™t feel too bad, you are not the first and wonā€™t be the last to comb over such a simple mistake (I myself have done it many times in the past!).

Just glad we got it working.

2 Likes

For completeness sake: I can now confirm seeing TRACE messages as TRACE in the openhub.log.

The following can be seen in the openhab.log with logging set to TRACE when receiving an Owntracks command:

2017-01-18 10:57:48.199 [TRACE] [b.m.internal.MqttitudeConsumer] - Message received on topic owntracks/owntracks/maxg-iphone/event: {"desc":"Home","t":"c","tst":1484616290,"acc":50,"lon":152.3871252314675,"_type":"transition","wtst":1484570767,"lat":-27.32542779299181,"event":"leave","tid":"MG"}
2017-01-18 10:57:49.231 [TRACE] [b.m.internal.MqttitudeConsumer] - Checking item GeoLoc_MaxHome...
2017-01-18 10:57:49.233 [DEBUG] [b.m.internal.MqttitudeConsumer] - GeoLoc_MaxHome has left region Home
2017-01-18 10:58:12.255 [TRACE] [b.m.internal.MqttitudeConsumer] - Message received on topic owntracks/owntracks/maxg-iphone/event: {"desc":"Home","t":"c","tst":1484616288,"acc":30,"lon":152.3707630859244,"_type":"transition","wtst":1484570767,"lat":-27.31735945681791,"event":"enter","tid":"MG"}
2017-01-18 10:58:12.287 [TRACE] [b.m.internal.MqttitudeConsumer] - Checking item GeoLoc_MaxHome...
2017-01-18 10:58:12.289 [DEBUG] [b.m.internal.MqttitudeConsumer] - GeoLoc_MaxHome has entered region Home

I strongly hope this threat will provide (at least) some guidance to someone encountering a problem with mqttitude 1.8.3!

Hey @Max_G, how do you convert mosquitto log epoch to real time (date, hourā€¦) ?

thanks!

Havenā€™t done it ā€“ was actually thinking about the same todayā€¦
Try: Display/Convert Epoch as DateTime
or: Converting Unix Timestamp into DateTime item

Hi Max_G
did you solve this issue with events and owntracks?

Well, it is workingā€¦ get OwnTracks GPS data via iPhone -> hole in firewall for port 1883; and an see the track in OwnTracks webā€¦ but have not done anything further with OH.

1 Like