mplogas

I have set up a Fedora 39 desktop VM (and a Debian, Arch, Win11 one for testing as well) and it seems the German Alt-Gr + Q combination is not supported via Unraids VNC, no matter what I try or what distro I use. This topic came up in various forums (Unraid, Proxmox, name it) and I tried (almost?) all the advices: removing SPICE, setting locale in the VM, (or VM creation UI or XML directly), remap Alt-Gr in Gnome/KDE, configuring keymaps, you name it.... I also tried Debian, Ubuntu and Arch and Windows 11. All installed VMs show the same behavior, so I think it's safe to assume it's a VNC issue. Yet, many people also report they fixed it at some point (or they stopped bothering). So what's the secret sauce? I would like to use my VM mainly as personal, centralized email/browser client so having the @-character would be really convenient. //edit: I installed xrdp on the Fedora VM to connect via RDP and all Alt-Gr characters work. So it's clearly a VNC issue.

It seems you are using your Docker network (class b - 172.16.x.x) in your config. Instead, use the IP of your Unraid instance / Navidrome instance (likely class c - 192.168.x.x) as BNB_SUBSONIC_URL (Key 3) and the IP of one of your Sonos speakers as SEED_HOST (Key 5). Your BNB_URL (Key 6) should be your Unraid IP.

LiquidCTL can read the sensors attached to the control unit, but it seems it's not possible to read other sensors (e.g. cpu, mainboard or hdds). Is your Commander XT actually a Core XT? This unit allows up to two temp sensors, you could place them very close to your HDDs. It's what I did with my Commander Pro and it works quite reliable.

Hey @mjorud, sorry fror the late reply. The output looks good so far. > WARNING: some attributes cannot be read from corsair-cpro kernel driver This is nothing to worry about, it'S coming from liquidctl / the commander pro kernel module. > I just found out (and I have been using Unraid for 10 years or so) that Unraid has native support for the Corsair Commander Pro That has been added in the last 6 months, but you can't control the fans based on temperature sensors. If you just want to monitor your fan speed, you don't need the container.

Ah, that makes sense. I already made the liquid cooling optional yesterday evening, but it's still in the dev branch (https://github.com/mplogas/laac/tree/dev). I'll update the container later today and update this post accordingly. This will remove the "usage: [...]" output in your log files. edit: container has been updated. cooling is optional now.

Okay, let's get to the bottom of this 1. Make sure your container is up-to date. Should be, but couldn't hurt to double-check 2. Could you post you entire config.yaml and your setup (e.g. KRaken X53 and Commander Pro)? In the meantime I'm looking into ways to get my dev/test container environment "ready for public". I have the feeling this could be useful long-term. edit: my output looked a little bit different, hence my questions: NZXT Kraken X (X53, X63 or X73) ├── Firmware version 2.1.0 ├── Pump Logo LEDs detected └── Pump Ring LEDs detected Result #0: NZXT Kraken X (X53, X63 or X73) cooling color: set sync color off Result #0: Corsair Commander Pro controller fan1: 20 0 30 400 35 900 40 1200 45 1500 --temperature-sensor 2 controller fan2: 20 0 30 400 35 900 40 1200 45 1500 --temperature-sensor 2 controller fan3: 25 0 30 500 35 800 40 1000 45 1500 --temperature-sensor 1 controller fan4: 25 0 30 500 35 1000 40 1500 --temperature-sensor 4 controller fan5: 25 0 30 500 35 1000 40 1500 --temperature-sensor 4 controller fan6: 25 0 30 500 35 1000 40 1500 --temperature-sensor 3 edit2: Debug container is up. Add a new container from Unraid using the LaaC template but use this image instead: mplogas/laac:debug. Then turn off your stable container to avoid conflicts.

Alright, the option is now called "fan_sync_speed". Please try again, I had to fix a bug I introduced with the option.

> The LaaC-folder created under \appdata is created by root:root instead of nobody:users. This makes it hard to create config.yaml using the share. Adding PUID 99 and PGID 100 helped. Good catch, I'll look into that. I have my container configs on a different pool, so I didn't catch that. > I can't wrap my head around the yaml-file. All I want is to run I see, so instead of configuring each fan individually, you are looking for a "one size fits all"-setting? I think I can add that real quick. Give me a few minutes! // edit: GitHub is updated, container image is uploading to Docker Hub. Give it a spin and let me know if it works for you. I still need to dig into the permissions issue and will update this post accordingly.

As part of the process to get my container(s) approved, I am asked to provide a support thread. I'm always happy to help, but I'm asking you to consider posting issues regarding LaaC on GitHub first. I'm an engineer, so I'm on GitHub all day and I can get back to your issues/questions/feature requests much quicker. For Unraid / container related questions, feel free to post here.