oz1sej

joined 1 year ago
 

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?

[–] oz1sej@lemmy.world 5 points 1 month ago

Ubuntu was the first Linux distro I tried, and I've never tried anything else, across three laptops. I've never experienced problems like the ones you describe.

[–] oz1sej@lemmy.world 0 points 1 month ago* (last edited 1 month ago) (5 children)

Oh, only reception. Should definitely have mentioned that... Title updated.

EDIT: Wow, you're Onno VK6FLAB! Love your podcast! 😀

[–] oz1sej@lemmy.world 0 points 4 months ago

Thanks - I figured out how do to it - I had to use git remote set-url origin.

[–] oz1sej@lemmy.world 0 points 4 months ago* (last edited 4 months ago)

Ok, I figured it out - I needed to

$ git remote set-url origin ssh://git@codeberg.org/OrgName/repoName.git

-and then I could push.

 

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?

[–] oz1sej@lemmy.world 2 points 4 months ago

Because he has a big army. Previous leaders have honored the principle that with great power comes great responsibility. Trump honors the principle that with great power comes the power to take what the hell you want, and nobody can do a goddamn thing about it.

[–] oz1sej@lemmy.world 0 points 4 months ago

Yes, with a Raspberry Pi, and sending data to the MQTT server directly with rtl_433 and the MQTT option.

 

I just got this

$ sudo apt update && sudo apt -y install timeshift
Henter:15 https://www.synaptics.com/sites/default/files/Ubuntu stable InRelease [9.626 B]
E: Repository 'https://www.synaptics.com/sites/default/files/Ubuntu stable InRelease' changed its 'Origin' value from '' to 'Synaptics Inc'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

What fresh hell is this?

[–] oz1sej@lemmy.world 0 points 5 months ago (2 children)

But what's all the GUI shenanigans for, then? There are so many configuration options under MQTT devices in the GUI, but nowhere to enter an actual MQTT topic. I wonder what it's for.

 

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?

[–] oz1sej@lemmy.world 12 points 1 year ago (2 children)

YSK americans always assume everybody else are americans.

[–] oz1sej@lemmy.world 0 points 1 year ago

I don't think they will bother. They will end up in a landfill, and the school will buy new Windows computers.

[–] oz1sej@lemmy.world 0 points 1 year ago

You spunk trumpet.

[–] oz1sej@lemmy.world 0 points 1 year ago (2 children)

"Sir! The radar! It appears to be - jammed!"

 

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?

view more: next ›