I personally am running 1.8.3. Sounds like Fredrik has got his issue sorted. Since you have proven that your MQTT broker is receiving those messages I think the only thing left is your item config (but I am not sure what).
Can you post your full items config currently? I would suggest paring it right back to a single Switch item to remove any confusion and see if we can make any progress with that.
no entry related to mqttitude in openhab.conf
mosquitto (has been and) is running nicely
mqttitude does not seem to process the messages.
After reducing the items config to one switch, I rebooted the rPi (just to be sure)
On a side note: if you have 1.8.3 running, why not check the log level by adding TRACE to the logger, and see, what the outcome of openhab.log is. Even if I set it to TRACE it says DEBUG in the log. (The same with the EXEC and Yahoo weather binding); so I doubt that the openhab.log will show TRACE as a word; whether this affects its inner working; e.g. whether it does actually do TRACE I cannot tell.
In any case, thank you for your continued help with this issue.
@westermarck: As you can see in a previous post, I have done exactly the same. In my case (as I suspect in yours) mosquitto is working. But the mqttitude binding, despite subscribing to the OwnTracks topic does not seem to process any of it.
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.