Get/borrow a thermal camera, and use that to see where the heat is coming in. Some libraries have thermal cameras, but that might be rare. You can also get very cheap and nasty thermal cameras from Aliexpress for $60 AUD

Never heard that term, but its a very obscure concept, so wouldn’t surprise me if it had multiple names. Probably vender specific names?

Seems quite a few people havent heard of it, hence a lot of the split DNS answers :/

I can’t remember exactly what its called, but something like router NAT loopback is what you want. I’ll have a look around. But if you set it right, things should work properly. It might be a router setting.

Found it: https://community.tp-link.com/en/home/stories/detail/1726

4 cores is a bit limiting, but definitely depends on the usage. I only have 1 VM on my NUC, everything else is docker.

I thought all the core processors had VT* extensions, I was using virtualization on my first gen i7. They are very old an inefficient now though.

I5 3470 is old, but its not that bad. Lots of people are homelabing on NUCs which are only very slightly faster. Performance per Watt will be terrible though. (I am on an i7-10710u, and I’ve yet to run out of steam so far - https://cpu.userbenchmark.com/Compare/Intel-Core-i7-10710U-vs-Intel-Core-i5-3470/m900004vs2771 )

It has VTx/VTd, so should be okay for proxmox, what makes you think it won’t work well?

You have a typo: platform: esphome.

Thanks for posting, good catch!

At 8tb, I can’t find any, but here is a 5tb disk:

https://www.amazon.com.au/Seagate-Barracuda-Internal-Drive-Factor/dp/B01LXO31IZ/ref=mp_s_a_1_13

Check the thickness though, your device may not accept 15mm disks.

The OPs device can take a nvme SSD and an internal HDD. Unclear if the current SSD is nvme or not though, but I assumed it was nvme.

The USB connection will likely be quite slow, and some external harddisks will power save aggressively.

You could get a largish 2.5" HDD and hook it up internally, might be a middle ground cost-wise?

I cant test this, but should it be something like:

# Example button configuration
button:
  - platform: template
    name: Livingroom Lazy Mood 1
    id: my_button

    # Optional variables:
    icon: "mdi:emoticon-outline"
    on_press:
      - logger.log: "Button 1 pressed"
  - platform: template
    name: Livingroom Lazy Mood 2
    id: my_button2

    # Optional variables:
    icon: "mdi:emoticon-outline"
    on_press:
      - logger.log: "Button 2 pressed"

As for the other thing, that might be something you need to write your own driver for? if you need some inspiration, this repo has a driver for mitsubishi heatpumps, which does something similar (read/write to a uart): https://github.com/echavet/MitsubishiCN105ESPHome

Homeassistant is another option. Host the server and run the app on your phone. Its not very granular though, and the user interface is not great

Here in Aus, this is how the NBN is provided in some areas, there is a NBN coax-to-ethernet box, and then you can plug in your own router.

There is always a chance that your ISP is doing something weird that prevents that working, but I think it should be fine.

Its not, but if the value of the data is low, its good enough. There is no point backing up linux isos, but family photos definitely should be properly backed up according to 3-2-1.

To be fair, we only know of this one. There may well be other open source backdoors floating around with no detection. Was heartbleed really an accident?

It depends on the value of the data. Can you afford to replace them? Is there anything priceless on there (family photos etc)? Will the time to replace them be worth it?

If its not super critical, raid might be good enough, as long as you have some redundancy. Otherwise, categorizing your data into critical/non-critical and back it up the critical stuff first?

Sorry, wasn’t meant to be condescending, you just seem fixated on file size when it sounds like RAM (and/or CPU?) is what you really want to optimise for? I was just pointing out that they arent necessarily correlated to docker image size.

If you really want to cut down your cpu and ram, and are okay with very limited functionality, you could probably write your own webserver to serve static files? Plain http is not hard. But you’d want to steer clear of python and node, as they drag in the whole interpreter overhead.

RAM is not the same as storage, that 50mb docker image isn’t going to require 50mb of ram to run. But don’t let me hold you back from your crusade :D

Having PHP installed is just unnecessary attack surface.

Are you really struggling for space that 50mb matters? An 8gb usb can hold thar 160x?

Just go nginx, anything else is faffing about. Busybox may not be security tested, so best to avoid on the internet. Php is pointless when its a static site with no php. Id avoid freenginx until its clear that it is going to be supported. There is nothing wrong with stock nginx, the fork is largely political rather than technical.

Same, Uptime Kuma is fantastic. I put it on my most critical server, if Kuma is down, everything is down :D