I am struggling with the config for Hosted Owntracks. The Owntracks app on my iPhone sends push notifications when I leave and enter my home but Openhab never receives them. I have included a part of my openhab.cfg, a part of my items file and relevant log file entries.
Just to confirm, you need to use your account token for authentication, not your Owntracks hosted account password. Can you try subscribing to the Owntracks hosted broker using mosquitto_sub just to ensure you are successfully able to connect and receive messages?
Ok - so if I were you I would focus on getting something simple like mosquitto_sub working before worrying too much about openHAB. What error do you get when trying to connect using mosquitto_sub?
Hi Ben,
There was an old mqtt client on my openhab server (with lousy tls support), I managed to update it and now mosquitto_sub works, how to I add the tls/certificate file to the openhab config or is that not necessary ?
Vincent
I typically configure mosquitto to only require TLS certificates for external connections (i.e. port 8883). And since openHAB is a local connection it doesn’t require any certificate. Otherwise check the MQTT binding WIKI page for details on how to set this up.
That is the problem Ben, I am using hosted owntracks (remotely) at hosted-mqtt.owntracks.org and they require 8883 and tls, nothing to be found on the binding page about certificates.
Ah I see, sorry Vincent I got a little lost there. Yep I don’t believe the MQTT binding supports TLS certificates. But I think you should be able to connect to Owntracks hosted without? Although I am not certain.
FYI - hosted is there for OwnTracks app users - maintained by the OwnTracks guys. The Mqttitude binding for openHAB was written (by me) to allow openHAB to using the OwnTracks app for presence detection. It was written well before the hosted stuff was setup and in the beginning was designed to be run on a local MQTT broker (for your own privacy).
Feel free to make changes to the Mqttitude binding to add support for TLS etc.
don’t get me wrong - I’m not complaining. It is more the question if I’m to stupid to get it working
If hosted opwntracks is not supported at the moment then I know that I’m not doing something wrong…
Ben a BIG thankyou for the work on the Mqttitude binding, just got it working with a couple of geofences and it is fantastic!
I thought about running it in the hosted mode but it didn’t (wasn’t) seem that hard to set it up on a local version of mosquitto with dynamic dns on the router and port forwarded.
Whats even better is I can use the mosquitto install for a heap of other ideas that have just sprang to mind.
Yep running your own MQTT broker opens up a world of possibilities! Check out mqttwarn, it is a wonderful script that works really well with openHAB and allows you to decouple all your notifications from your rules. You just create a set of items for different notification levels, I.e. trace, info, warn, alarm, and bind them to individual MQTT topics. Then set mqttwarn to monitor these and let it handle all your notifications, e.g. email, syslog, pushover, xbmc, slack, whatever you like.
Makes it very easy if you want to add or remove a device from notifications, or add a new notification channel, you just update mqttwarn instead of a load of openhab rules.
I’m having trouble with OpenHAB to update an item in the Sitemap; i defined a Switch to do that.
Should i set in mosquitto every single “location” as i set my “home” location?
I would like to use it as “Region Mode” as it says in the Wiki, but:
if i don’t set the “home” location there are Log Errors (see my other post)
mosquitto receives updates OK from the OwnTracks app (Android)
the App seems to do a Location update when i unlock the phone, or enter the App…and seems different in Ios than Android…not fully convinced with it
i believe the app OwnTracks doesn’t make updates when i’m moving, i’m missing events (enter, leave)…i suppose that is because the phone stays “sleeping”…?
mosquitto and openhab in the same computer
openhab.log:
2016-03-11 10:59:41.397 [TRACE] [b.m.internal.MqttitudeConsumer] - Checking item LG_work...
2016-03-11 10:59:41.398 [TRACE] [b.m.internal.MqttitudeConsumer] - Not a location enter/leave event, ignoring
2016-03-11 10:59:41.398 [TRACE] [b.m.internal.MqttitudeConsumer] - Checking item LG_work2...
2016-03-11 10:59:41.399 [TRACE] [b.m.internal.MqttitudeConsumer] - Location received for LG_work2: Lat: -XX.XXX03, Long: -XX.XXX033
2016-03-11 10:59:41.399 [DEBUG] [b.m.internal.MqttitudeConsumer] - LG_work2 is outside the 'home' geofence (4628.492730344677m)
2016-03-11 10:59:41.400 [TRACE] [b.m.internal.MqttitudeConsumer] - Checking item LG_home...
2016-03-11 10:59:41.400 [TRACE] [b.m.internal.MqttitudeConsumer] - Not a location enter/leave event, ignoring
When using region mode the region_description must match the region name in the Owntracks app. Unless you have regions named enter and leave your items LG_work3 and LG_work4 will never fire.
If i want LG_4 switching: should i define the “work” in openhab.cfg as i did with “home”?
(remember i’m testing, i don’t need to execute nothing at my house when i reach “work”)
I suppose i don’t have to, but also defining “home” says it is optional, and i was getting errors until i defined it in openhab.cfg
The few Transitions i saw were published to topic owntracks/maxi_OT/CelLG/event
so i suppose the only Item firing up will be LG_3 when leaving or entering “home”…? i think i will test that with an email Rule…
And also i see many messages to topic owntracks/maxi_OT/CelLG (type location)
