I ran HA on mine for a while before I moved it to a VM. Right now I’m using my Pi as a secondary wireguard VPN in case my primary is down for some reason.
Also, quick tip, I found that ikea zigbee bulbs work really well but have really bad coil whine when off, don’t use them for bedside lighting.
Not a lawyer; would this likely stand up in court? Obviously I wouldn’t risk it were I the dev, but just curious.
It’s pathetic that I’ll happily recommend my Emporia Vue2 energy monitor to folks running HA — not because it works out of the box, but because the company is aware of the community integration projects and seems ok with it, even if they don’t actually support it. (ESPHome Firmware flash gives you local control — It’s been pretty great!)
Not a lawyer; would this likely stand up in court?
I’m not a lawyer either, but I don’t think so.
The developer of this Home Assistant integration is German. European law allows people to reverse engineer apps for the purpose of interoperability (Article 6 of the EU software directive), so observation of the app’s behaviour or even disassembling it to create a Home Assistant integration is not illegal.
In general, writing your own code by observing the inputs to and outputs from an existing system is not illegal, which is for example how video game emulators are legal (just talking about the emulator code itself, not the content you use with it).
If it’s a Terms of Service violation, it’d be the users that are violating the ToS, not the developer. In theory, the Home Assistant integration could have been developed without ever running the app or agreeing to Haier’s Terms of Service, for example if the app is decompiled and the API client code is viewed (which again is allowed by the EU software directive if the sole purpose is for interoperability).
The code in this repo is likely original Python code that was written without using any of Haier’s code and without bypassing any sort of copy protection, so it’s not a DMCA infringement either.
First, you should something decent, not DietPi. You’ve Armbian for a ready to go experience or official Debian.
Once you get into something Debian 12, you can run LXD/LXC as a containerization / virtualization solution and use the same Pi to run the official HA VM image and whatever else you would like.
Why is dietpi a worse choice? it’s still basically debian (11).
I’ve chosen DietPi because of their sane defaults that I would have to setup myself like vm swappiness, fs noatime, tmp journal, and some more I am not even aware of.
Armbian has sane defaults for SBCs as well (yes log2ram so you won’t burn SD cards) and it is way more stable and polished than DietPi with less overhead. About bare Debian, you’ve the images I linked to and you can make it log to the ram with a simple line in systemd’s config.
Storage= Controls where to store journal data. One of “volatile” (…) If “volatile”, journal log data will be stored only in memory, i.e. below the /run/log/journal hierarchy (which is created if needed).
Already got ssd as a nfs share in my openwrt-based router before that I did have it set up on the rpi. I did want to do offsite backup into that disk originally but I’ve got “only” ~100Mb/s up/down speed here so I didn’t want to risk slow-downs etc (but now that you remind me, borgbackup should be rather light on traffic!).
NEMS being a whole OS is a pitty, I like the possibility to have multiple different services there.But you are absolutely right I could have a offsite resource monitoring for my Hetzner setup with these, thanks!
UPDATE: In the end I got a hetzner dedicated server and the performance is a lot better than a vps could ever be with similar specs and am loving the experience.
Yeah, I had the same issue. Sometimes it was the SD card, sometimes the network interface (not your case obviously), sometimes things connected to USB, sometimes it was running hot… I gave up and now I just run everything on an older Slimbook Zero. Yes, power consumption is higher (still pretty low) but so is stability.
Yeah it seems a lot of people are saying the SD card is the issue which wouldn’t surprise me. I do have some spare space on my proxmox server but it would just be a huge pain in the dick to move everything… But it’s looking like I may need to sadly.
The company says services like Plex, Pluto TV, Sling TV, Starz, and ZDF will introduce support later this year.
I always had the impression that plex was really slow when it comes to implementing new features. I’m definitely looking forward to a chromecast alternative though. Being locked into googles DNS gives me problems due to it prohibiting streaming from my local server via hostname.
I really hope it will be implemented in Jellyfin as well since I can’t get my installation to work with Chromecast at all (most likely again due to the DNS issue)
I solved that by adding an 8.8.8.8 ip to my pihole interface. Because of how TCP/IP works, this has the fewest hops and is, therefore, the one to be used. I’m blocking all outbound DNS traffic for good measure.
By adding do you mean blocking it in pi-hole or somehow redirecting it to your pi-hole dns server?
I currently have it blocked in my router and can confirm this by trying to ping 8.8.8.8 without any response. If you mean redirecting to your pi-hole I would really like to know how to do it
I didn’t add it to any lists, but to the network interface itself. You know the output of ip a? The one pihole listens on (wg0 in my case, because wireguard) has something like, say, 10.0.0.1, but also8.8.8.8. So when a DNS packet is spit out by chromecast to go to 8.8.8.8 UDP port 53 - my pihole happily answers that request. You could also do a separate unbound instance on a new virtual interface with a quad8 ip and just forward everything to pihole, if you fancy.
I hope to see Jellyfin support this too (Plex is already getting support apparently) and hopefully it will work desktop-to-desktop and not just between streaming devices and phones.
Although it’s probably not massively needed as Jellyfin can already control remote devices.
If something could cast from one of my devices to another of my devices using the cast button, that’s all I want. I can strap one of those devices to my TV and be golden.
There are a few ways around it. The simplest is to add the –privileged option.
The more secure method with podman is by specifying a user (ex -u 10001:10001) from your extended subuid:subgid range after your full and proper setup of rootless podman :-)
Then instead of chown you’ll want to use the oddly named podman unshare tool to automatically set the permissions of the host directory. You would then want to start your service with systemctl --user instead of sudo systemctl
This denotes the range of subuids that are available to your user.
-u 100000:65536
This part specifies two things ([UID]:[GID]) even though it’s the same syntax as the earlier part that specifies one range :)
I suspect what you will want to do is use the following:
<span style="font-style:italic;color:#969896;"># change ownership of the directory to the UID:GID that matches something in your subuid:subgid range, in this case 10000:10000
</span><span style="color:#323232;">podman unshare chown -R 100000:10000 /home/privatenoob/media/storage1/Filmek/
</span>
Then we can specify that the user in the container can match the user (UID) we specified above:
As a note, if you copy/pasted that ExecStart line, you might have gotten the invalid argument error because you entered 100000 (outside of your subuid range, i.e. >65536) instead of 10000.
There’s a nice guide that gives a great walkthrough. I’ll dig through my bookmarks and add it here when I get some time.
This is likely an issue with your SD card…Pi’s eat them up, even the good ones that supposedly can handle it get chewed up pretty quickly. It really sucks that they haven’t transitioned to emmc but insist on using SD cards.
selfhosted
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.