I was covering for a colleague on holiday last week, but now I'm covering for 2, so I could have 50 people needing my help this week...
Oh and a manager wanted "an update", worst meeting I've had in a while... one of those that stick in your head and later on you think of all the great things you should've said.
Apart from that... all good 😁
Birthday parties... ah I miss those (my daughter's grown up now)
Dune... that's a hellofabook... then you'll have to read all the others next. But there's (obviously) so much more in there than the films... enjoy!
Your dogs can swim at the butchers? Wow
Yeah, there's a butcher near us, it's great getting local food from them. Steaks an inch thick...
Ok, next check your wifi signal strength is ok.
If you have a laptop / PC open the cli and use ping with the Pi's IP address.
If not, get a ping app on your phone (I used vernet from Fdroid), check the settings have a really high number of pings (ie 60) and ping your Pi...
If the ping times out or the response times are all over the place with , then it's either your wifi or something else on the Pi / phone.
I presume your only running home assistant on that Pi, nothing else?
Ok, you're going to need to give us more to work on here...
Ie, I could be assuming the Pi has ethernet cable to the router and you're trying to access it via a desktop PC which is also cabled to the router? I'm guessing at least one of those assumptions are wrong...
Are you trying to access it from a webpage, or the Home Assistant app?
First up, how comfortable are you with command line? I'd run a continuous ping to the Pi and just see what happens there first...if that's flaking out, your network or Pi has issues and you need to fix that before anything else.
If you're accessing the Pi from a phone, is it only connected to the local wifi or are you also connected to a VPN, or does the phone keep auto-connecting to a nearby Starbucks, etc...
Jeez. Didn't hear about that one, back in the day.... wow.
I'm kinda overlapping with a few other comments here, but perhaps adding a little...
As others have said, getting something down is the main point, so I keep everything in Logseq markdown files. The instantaneous ability to create links between topics means that I can write a note about installing [[X]] and then realise I should mention I had to update the [[DHCP]] and [[DNS]] entries... job done.
I try to automate things in Ansible and put rough notes and URLs I was following in the ansible file. I recently setup an old Ras Pi 1 B+ as a NUT server and the instructions on 1 site didn't work correctly, so I just threw links into the comments and mentioned it in Logseq... next year I'll visit it all again and maybe improve the notes.
I also have a DEATH.txt file which my partner knows where to look... that gives them a high-level overview of what's going on, where the keepass and logseq files are, etc. Maybe they'll understand, but our friends will be able to help... just in case...
Not over here it isn't.
(I'm assuming you're from over there of course)
Nice.
It's those memories that make it all worthwhile when they come home drunk and shout at you becuase you don't understand... that'll happen MUCH sooner than you'll realise 😉
Yeah, it's nice when that happens
I use plain Arch not Endeavour, but with the AUR I presume you should also check now and again whether old dependency packages can also be removed with pacman -Qtd... you might be able to find even more space 😉
Advanced: if you know what you're doing, you can try:
sudo pacman -Rnsc $(pacman -Qqtd)
Don't say I didn't warn you if it breaks something...
I moved from Backblaze to a Hetzner storagebox, to backup my Arch (btw) NAS.
Simpler to work with and cheaper.