• 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 7th, 2023

help-circle


  • You might want to look up SMR vs CMR, and why it matters for NASes. The gist is that cheaper drives are SMR, which work fine mostly, but can time out during certain operations, like a ZFS rebuild after a drive failure.

    Sorry don’t remember the details, just the conclusion that’s it’s safer to stay away from SMR for any kind of software RAID

    EDIT: also, there was the SMR scandal a few years ago where WD quietly changed their bigger volume WD Red (“NAS”) drives to SMR without mentioning it anywhere in the speccs. Obviously a lot of people were not happy to find that their “NAS” branded hard drives were made with a technology that was not suitable for NAS workload. From memory i think it was discovered when someone investigated why their ZFS rebuild kept failing on their new drive.



  • This sounds like a FOSS utopian future :)

    There’s a few projects that have started towards this path with single-click deployable apps, you could even say HomeAssistant OS does this to some extent my managing the services for you.

    I believe one of the biggest hurdle for a “self hosting appliance” is resilience to hardware failure. Noone wants to loose decades of family photos or legal documents due to a SSD going bad , or the cat spilling water on their “hosting box”. So automated reliable off-site backups and recovery procedures for both data and configs is key.

    Databox from BBC / Nottingham University is also a very interesting concept worth looking in to:

    A platform for managing secure access to data and enabling authorised third parties to provide the owner authenticated control and accountability.





  • One way is to make a new “entity”, that’s not actually linked to your previous temperature sensor. I’m not familiar with how to tie them together in a “device” like how ZigBee2mqtt auto discovery does.

    So just add a new “sensor”/“entity”

      - name: "Sala_battery"
        unique_id: "temp_sala_battery"
        state_topic: "zigbee2mqtt/temp_sala"
        value_template: "{{ value_json.battery }}"
        unit_of_measurement: "%"
    

    Use MQTT Explorer to listen to your ZigBee2mqtt broker topic “zigbee2mqtt/temp_sala” to get the exact field name (battery, battery_state or some such)







  • Like others said it’s mostly just practice.

    What helps is to align the (short) ends and hold them flat between your index finger and thumb. Use your free hand to get them in order. Once they’re in order, keep holding them still between your index finger and thumb using one hand, then use your free hand to slot on the connector

    Edit: also bending them back and forth a bit will soften them up and reduce them curling in all sorts of directions. It also weakens them, so don’t overdo it (mostly only works for solid cable, the type meant for permanent installations like inside walls)



  • Yes please consider the software, not just the form factor. Because SteamOS is Linux there is no Photoshop and Lightroom. There is however Gimp and Darktable (and Krita) which may or may not fit your needs.

    Also you want to make sure you install desktop software as Flatpaks. Lke others have said, the root filesystem is read-only, and pacman repositories are old. The root filesystem gets reset on SteamOS updates, but flatpaks are installed in your home directory which persists across updates.




  • For RPi the two major causes of issues (in my experience) are low spec power supplies and low spec SD-cards.

    Power supplies drop voltage when the loads gets too high, which is especially pronounced with high power USB devices like external harddrives.

    SD-cards tend to get worn out or give write errors after enough writes. Class 10 SD cards are recommended for both speed and longevity. And ideally try to avoid write intensive stuff on the SD card