How do you set up the Owntracks app?
There is Quiet / Manual / Significant / Move …
I would choose « Significant », it’s the default mode and it’s a good mode for tracking your position changes without consuming too much battery.
See:
@Jean34 All Firefox bugs have been resolved normally. If you are using the Gladys image, your image should have updated automatically. Otherwise, update it. On Gladys Plus, a hard refresh of the web app should update the app for you. If you find other Firefox bugs, do not hesitate.
@pierre-gilles, purely for information, owntrack is open-source, but cannot be used without Google services.
There is phonetrack, a Nextcloud app extension and an open-source APK via F-Droid
I tested it and it works quite well, but as for integration with Gladys, I couldn’t say. But if it can give some ideas to some people ^^
*On Android! ^^
But I see the idea!
On their website it says « Log to any server which can receive HTTP GET or POST requests (custom log job) », so it shouldn’t be more complicated than owntracks.
If you are motivated to develop an integration, it will be with pleasure ![]()
@pierre-gilles Unfortunately, I’m not a developer
, if I have the chance and some time, I’ll try to tinker something based on existing modules, but I think it won’t be for a while ^^
When some of the modules I use are compatible with v4, I’ll try to switch to them, but before that, I need to play with Docker, and I think I’ll have questions for you about it ^^ I seem to have read about the Docker privileges option in some forum topics, and even before starting Docker, I wonder: Does Gladys really need the privileges option? In terms of security, if the unprivileged option can be used, it’s much better. Compared to my LXC containers, I don’t have any with privileges, hence this little question ![]()
This is for USB device access (e.g., Z-Wave dongle) but it’s optional.
The most secure way is to use the --device argument.
Privileged is the easy way out.
We need to document this.
I think we need to think at a higher level:
Why do we use Docker?
In Gladys 3, I remind you that we ran Gladys directly on the machine, without Docker, so Gladys had access to the entire machine.
In Gladys 4, we use Docker to facilitate packaging, deployment, and updating of Gladys instances. Given that we are in embedded systems, we need to access devices (USB, GPIO, Camera Pi via the camera bus, for example), it makes perfect sense to give Gladys full access to the machine, as it would be the case if we were just running the program directly on the Raspberry Pi.
We are not at all in the Docker usage of a cloud provider that would want to isolate the execution of untrusted code, limit access to the physical machine, and limit the resources used by a third-party user.
Here, the user runs on their own machine, alone, an embedded program that makes intensive use of external devices and hardware. On the contrary: we want to take advantage of the super capabilities of the Raspberry Pi, and have the same functionalities as if we were running Gladys directly on the host like most programs do.
After that, as @VonOx said, it’s optional, and if you use Gladys in a context where you don’t need any hardware, you can remove the --privileged. The gain in « security » is quite minor or even non-existent in this specific use case of Docker. (Do not generalize, I’m talking about this case here)
Hello, is it possible now to use owntracks with Gladys 4?
It is possible to do this via Gladys Plus, but via MQTT the task is still pending, no one has developed the integration.
GitHub todo reference: