oz1sej

I'm running my own HA locally, in my house, but I would like to be able to access it also when I'm not home. So I've put it on my Zerotier One VPN, which works fine. Except for two things:

1. HA no longer knows when I'm home - it thinks I'm always home;

2. Other people in my household would also like to have remote access, but it's unrealistic to have them install and use the VPN.

So - can I just open it up, and rely on long, complex passeords? Or is that a complete no-go?

I have a repo that I've just uploaded to codeberg. In earlier versions, I had a ton of media files - they have now been removed. However, when I uploaded the repo to codeberg, I'm getting this notification:

Your private repo uses up a large amount of disk storage, while all content should ideally be public and licensed under an OSI- or FSF-approved Free Software licence. Please refer to our ToS and the FAQ about software licenses and private repositories. Thank you for considering to release this repo to the public or reducing your required disk space for this repo.

Turns out, my pushed files are 1 MB, but the .git folder is 279 MB - how do I slim it down?

I have a repo that I want to push to codeberg. First, I tried to push to create and got the message

$ git push --mirror
Forgejo: Push to create is not enabled for organizations.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

So I created a new repo, but wasn't allowed to push until I had pulled - which just deleted all my local files 🙄

So - what do I do?

I still have trouble understanding how to add an MQTT device without YAML. It seems there's an elaborate GUI flow made to deal with this, so why is this so complicated?

I have MQTT messages coming in. Their topics are e.g.

wx/temperature wx/humidity wx/light_lux wx/rain_mm wx/wind_dir_deg

How do I tell Home Assistant to just add the bloody device, and let me configure units afterwards and not type out 600 lines of YAML manually?

I used to just update stuff when I could see an update was available. This changed dramatically when a few months ago, I updated Zigbee2mqtt to version 2 and my whole house stopped working. That marked the moment when the other inhabitants in my house decided that the home automation project had gone too far.

Since then, when I saw an update was available, I've waited - preferably until I had seen other people reporting that stuff still worked. But now I've realised, that if I wait too long with an update, another update just comes along...

Can I somehow configure HA to always automatically install e.g. update 2.1.3 once update 2.1.4 becomes available? Or is that a nogo too? I realise that the only sure-fire way to do this is with a staging environment, where everything is tested out before updating the production environment. But how many of us has that kind of a setup?