Posts by chaosen3

    If we're going strictly by OP's desire to only use internal storage then the aforementioned NUC is a good place to start, or a tiny form factor PC from Dell/HP/Lenovo should suffice as those usually have the motherboard connector that allows you to connect a SATA ribbon cable. I find these work best as most modern "mini pcs" have dropped SATA connectivity completely so anything Intel gen 7-11 gen is usually a safe bet for me.

    Models I've had success with LibreELEC Generic installed on an 128GB M.2 SATA SSD, and my media on the internal 2.5" SATA SSD:

    Lenovo P330 TFF, Lenovo P340 TFF, Dell OptiPlex 7040 TFF (they all have drive trays too)

    Nope, the NAS can be just a dumb storage device in the network. You can push the local media DB there too (MariaDB, etc.) if you have more than one client, but Kodi is not a true 'server' app that supports 'client' devices. If you want to run alternate non-Kodi server apps that's a different topic, but displacing Kodi wasn't in the original question.

    Honestly this. You would then just need a way to expose your HDD as a samba share on your network. Some home routers even have a USB port just for this use case (using an enclosure for a HDD/SSD). You mentioned a tall NUC and I've actually tried on my NUC8i5BEH and for my uses it was okay (but just okay). The NUC supports M.2 SATA/NVMe SSDs and SATA HDDs/SSDs so on a device like this you could install LibreELEC to the M.2 SSD, and leave the SATA slot for your 2.5" HDD.

    Or you can just use an enclosure for your HDD to connect it with USB to whatever device running LibreELEC you choose to use.

    Strange that you don't encounter the issues on both instances of Windows 11, but perhaps one of the devices upgraded to 24H2 whereas the other came with that version of Windows? The reason? Microsoft's attempt to guard you against "insecure" samba connections.

    In any case you should be able to resolve with PowerShell commands (ran as admin):

    Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force

    Set-SmbClientConfiguration -RequireSecuritySignature $false -Force

    Set-SmbServerConfiguration -RequireSecuritySignature $false -Force

    The Argon ONE Control add-on is not required for the ONE V5 case, so you can skip this step. To enable the I2C bus, this line in the config.txt file is sufficient:

    dtparam=i2c=on

    In addition to this I wanted to add that you need dtoverlay=dwc2, dr_mode=host in order for the front USB ports of the ONE V5 to work.

    The Argon ONE Control add-on is not required for the ONE V5 case, so you can skip this step. To enable the I2C bus, this line in the config.txt file is sufficient:

    dtparam=i2c=on

    Is it not needed at all? I never tested the power button on the V5 prior to installing the Argon One Control add-on but I was under the impression it was needed to allow the use of fan "curves" in relation to CPU and SSD/NVMe temps at the least. Does the ONE V5 fan turn on automatically based on some hardcoded temp value?

    In any case its a lot of fun tinkering with the OLED screen to get it to display what I want it to:

    Hey guys, I got the Argon ONE V5 case and OLED module today and had similar thoughts to OP (I also use the NVMe add-on but this just works straight out of the box). I got this working by using the Argon ONE Control add-on and Docker (add-on) with Python to run a script, where the I2C of the RPi5 is passed through to the Docker container (uses luma.oled).

    1) Install Argon ONE Control add-on (enables I2C, fan, power button, temp controls)

    In Kodi:

    1. Add-ons → Install from repository → LibreELEC Add-ons → Program add-ons → Argon ONE Control → Install
    2. Reboot to complete install


    2) Verify I2C is enabled and can see the OLED module

    SSH into LibreELEC and then run:

    Code
    i2cdetect -y 1

    You should see the OLED module at 0x3C


    3) Install Docker Kodi add-on

    In Kodi: Add-ons → Install from repository → LibreELEC Add-ons → Services → Docker → Install


    4) Create the OLED script

    Create a directory for the script and then create oled_stats.py:

    Code
    mkdir -p /storage/oled
    nano /storage/oled/oled_stats.py

    Paste and save this:


    5) Run the OLED container

    Create and run the container by copying/pasting the below into your SSH session

    6) Interacting with the OLED container

    • Container Logs: docker logs -f argon-oled
    • Restart Container: docker restart argon-oled
    • Stop/Start Container Manually: docker stop argon-oled / docker start argon-oled
    • Remove Container: docker rm -f argon-oled

    The --restart=unless-stopped flag makes the OLED container auto-start on every boot
    The --network host flag is needed for the OLED screen to show the IP of the RPi5, and not the IP of the bridged docker network/container.

    This is just very basic so I'm sure someone who actually knows what they're doing can create something more elegant.