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
@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 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?
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:
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!).
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.