

Is it an LG though? The APIs I’m using are WebOS specific


Is it an LG though? The APIs I’m using are WebOS specific


Hmm, you mean when HA sees the TV come back? Interesting, that might work.
I’s rather not do the force refresh option, because sometimes you do want different profiles. Very dark show, sometimes I want the bright setting at night. Very overcast day, sometimes the dark setting is better during the day.


Hah, great question. I did. And then I realized, this only works if the TV is on the moment the switch happens.
Which in the evening is actually pretty commonly the case… But never in the morning.


Do you need a Github link? Assuming recent-ish LG, should he the same.


I have a lot of custom stuff, esp. regarding HomeAssistant integrations. But my favorite “stupid/not stupid if it works” solution is the following:
I have an LG TV and attached Nvidia Shield. The Shield is the only input we ever use on the TV, and since its remote also can turn the TV on/off and control volume, its all we need. Which is pretty neat, only one remote.
Except for image settings (i.e. proper bright picture during the day, different less bright image mode during the night). I don’t want to keep the extra remote on the couch just for that, but unfortunately, these settings are not exposed via HDMI CEC.
They are, however, exposed via a web API on LG TVs. So my utterly stupid solution is this:
(I feel the need to add: the TV is in an isolated subnet and has never once communicated with the internet, and it will damn well die an internet virgin.)
Anyways, this has been working flawlessly for 2+ years! I also have toggles in HA for the same endpoints, but honestly, never use them. It’s so nice to just be able to toggle the image via remote.


Does it actually? My VM has a lot of RAM, and Proxmox reports usage always around 90%, but that’s no matter how much RAM it ACTUALLY has, because almost all of that is cache and not strictly necessary. free -m shows Jellyfin using maybe 2 Gigs.
Haha. Might have slightly exaggerated. But only slightly.
The Proxmox host in question has a 1Gbit connection to the NAS. (Unfortunately. The other hosts don’t have a GPU, but SPF+… Oh well, can’t have everything.)
At some point in the last couple of months, it must have been damaged, and negotiated down to only 100Mbit. This must roughly have coincided with the Jellyfin 10.11 update, since I remember thinking that it must be the cause, due to close proximity of update and first issues.
Anyways. For basically everything in my library, 100Mbit is fine. Streaming an episode NAS->Jellyfin and Jellyfin->TV at the same time basically never saturates the link.
BUT, from what I’ve gathered by digging through Jellyfin issues and PRs, there’s a separate issue where Jellyfin will pull the episode, and if you need subtitles extracted from the episode file server-side (to transcode them in, if the clients can’t play them), it will at the same time pull the episode AGAIN, and together with the Jellyfin->TV direction, that’s frequently enough that it saturates the link.
Symptoms is (was) either a 20-30s wait before the episode would start playing, or complete freeze.
However, I believe this particular issues has been solved for a while. I’m not sure, because I instead opted for the Subtitles Extractor Plugin, which runs nightly and pre-fetches all the subtitles and stores them on the Jellyfin VM itself.
Where it was still noticeable though was if one of [Library Scan/Trick-play Extraction/Subtitle Extraction/Media Segment Scan] ran while playing an episode, the server would completely lock up.
Long story short: cable swapped, 1Gbit, all issues gone.
Sorry, but why not just fetch a single media file with multiple languages?
Domain + reverse proxy. The security issues some people here claim are significantly overblown.
Can’t speak to that, I’m not involved. All I know is that,
So yeah, I don’t know or really care about leadership change, I just know it’s gonna run like a rocket now 😄
Now THAT is a changelog.
Really excited about the query performance improvements, and the improvements to subtitle handling.


nixos-rebuild switch
Yeah, that’s my point. I never got around to putting things in Debian repos or the AUR because shit seemed unnecessarily complicated. Now on NixOS, I happily help maintain a bunch of packages and modules. Because the packaging, build system, and OS are just sane, stable, and a joy to work with!
Sorry, but calling the dumping ground for obsolete and outdated packages an “OS” goes a little too far in my opinion.
“Smaller userbase yet more stable and more and better maintained packages” is not the insult you thought it was, I’m afraid…
(/s, just in case, hope this is all still in good fun!)
I don’t how hoch you managed to accidentally type “Debian” while you were obviously trying to type NixOS.
Idk it took me 3 attempts to learn (neo)vim, but now every Linux system I SSH in I just go straight for vi(m), because moving around and editing in Nano is just so slow when you’re used to vim keys.
I swear I’m not trying to proselytize. People should use whatever they want, and these discussions are pointless. It’s all just tradeoffs and getting used to things.
“Some practical notes”
Looks inside
Three slop in a trenchcoat