No, the Mqttitude project has ended support. it makes no sense for OH to include stuff that isn’t supported. Mqttitude support never really worked well anyway and Mosquito use but hard to set up. If you are using openHABian, it’s just a menu option.
For the GPS tracker add-on, which supported supports OwbTracks, the preferred interface is to use HTTP now anyway so perhaps you don’t even need MQTT at all any more.
I use mosquitto on my server to collect owntracks positions. In openhab I use the the mqtt binding to connect to mosquito and get the location informations to my openhab installation. I wrote a small rule, to convert the mqtt messages to a location object, every time a new mqtt message is received.
@kuczerek Could you share your rule(s) and config(s), please redact as necessary?
I’m not satisfied with GPS Tracker and I also want to keep the OwnTracks Server component up and running and receiving data (GPS Tracker disables this functionality, by rerouting the messages from OwnTracks directly to OpenHAB). From my perspective, GPS Tracker is a workaround, not a solution.
Create string items and connect them to the channels. I created four of them with the names “OwntracksChannel_person1String” to “OwntracksChannel_person4String”. They will receive a JSON string from owntracks via mosquitto, each time an onwtracks client posts an update.
Create four location items for each person (maybe name them hperson1Position to hperson4Position) and leave them unconnected to any channel. They will be updated by the following rule. The rule should be triggered each time a OwntracksChannel_personXString item is updated.
I apologize for the delay. I finally got time to put this is. I got the first two thing files, (actually combined to one actual file) implemented. The GUI shows everything as it should from that point. I tried getting the rules example you gave, but I can’t seem to get it in typical rule format. Any assistance would be appreciated.