This mounts the data volume needed for persisting the default H2 database files to the host. This is pretty much the command in the docs translated over, except for the second to last line. "/mnt/docker-data/traccar/traccar.xml:/opt/traccar/conf/traccar.xml:rw" "/mnt/docker-data/traccar/data:/opt/traccar/data:rw" I followed along the instructions in the Readme, until it came to the final docker run command, where I wanted to put it into docker-compose. Don’t! Just use the official one (unless you have a good reason not to). When reading that documentation I initially thought I had to build the image myself. It seems to be rather badly documented, but there is an official Docker image for Traccar on Docker Hub. There is also a Home Assistant integration for Traccar.
Traccar cpanel plus#
The main plus point for me is that it is a stand-alone server which I could host in my DMZ. Traccar is a self-hosted GPS tracking system which supports a multitude of different devices and has mobile apps available for both major OSes. While I was dithering around not doing very much about this problem, another alternative cropped up: Traccar. However, it’s exactly the use case that MQTT is made for! Sending data to both HASS and the recorder would be difficult via HTTP. I hadn’t switched over to it because I wanted to try out the Owntracks recorder for logging position data over time. GPS Based Presence OptionsĪside from using Owntracks in MQTT mode, it also supports HTTP mode (which is now actually the recommended mode). In the meantime I was looking into other options for GPS based presence detection. Also, DNS is pretty critical to the operation of, well, everything – so I want to take my time and get it right. However, it’s quite a bit of work to migrate over. However, my DNS provider (Namecheap) don’t allow API access unless you have a large enough account with them.Įventually I will migrate my DNS to a supported provider and get internal TLS working. The solution to this would have been to use DNS validation to get the certificate issued. In turn, this meant that the MQTT server wasn’t able to renew it’s Let’s Encrypt certificate. This was due to moving separating my HA/MQTT server from the reverse proxy. This worked well until my Owntracks setup broke due to internal network changes. I was using a combination of Owntracks and SNMP to query my Pfsense firewall for devices on the network. One of the outstanding issues I’ve had with my Home Automation system in recent months has been to fix my presence detection. Please see the disclaimer for more information.
0 kommentar(er)
