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.
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.
In that order. I self-host both XMPP and Matrix, and I wouldn’t want to stop using matrix. Spaces, arbitrary amounts of self-chats, and so on are great. I use matrix every day.
But for chatting… It sooner or later fails you. It’s slow. Notifications break. Messages are shown as sent, but somehow do not appear in the recipient’s devices until TWO WEEKS LATER (yeah IDK, happened twice already, in different chats and directions. Best part is, I’m not even federated!). Encryption is great IF YOU KNOW SOME CRYPTOGRAPHY BASICS, and utterly confusing otherwise.
XMPP just works. Especially the calls, holy shit, I had to fight Matrix for so long to make voice and video calls work, and xmpp just… Works. Notifications are way more reliable (as in, have been absolutely perfect). I really like monocles as a chat app on Android. (The downside is: can’t decrypt old messages on new devices, and desktop clients are ugly.)
So why Signal above XMPP?
Because it’s not your fault should something ever break in a vital service. Also the encryption and privacy afforded by it a great.
I’ll second Pocket-ID.
I originally had Authentik setup. It worked well enough. However, their packaging constantly broke and no-one seemed to care.
Switched to Pocket-ID and won’t be looking back. Passkey-based OAuth was all I wanted anyways. (Also, the logins themselves are noticeably faster!)
This started off as a single file in my private nix config, to see if I could get it working at all. In that initial part, some parts were indeed LLM generated (esp. testcases based on my existing intents and failures).
When I noticed that this might actually work and be useful not just for myself though, I moved everything out manually, refactored and cleaned it up, and everything since has just been myself. I guess you’re still right though. I’ll see about adding a disclaimer to the README until I’ve gotten the chance to properly rewrite everything.
Huh, interesting. Does that work with wildcards like “put x on my shopping list”? Also, what are you using for that, if I may ask?
Sorry, I don’t quite follow 😅
What’s the problematic response?
Yay, that’s fantastic to hear!
Also, how’s your experience been with the PE? Getting a readymade device in a nice shell is appealing for sure 😅
Oh, in the demo gif, that’s via a shortcut (holding power for half a second). Sorry, can’t help with wakeword there 😅
Very cool. I’ll definitely look into that, and let you know back here :D
Glad to be of service… 😄
did you consider metaphone matching?
I did not even know about this. Sounds super interesting. Though it seems to be very language specific?
My original intent was to not rely on language specifics. But maybe we could just define additional steps in the pipeline for specific languages. Hm. I’ll have to think about this some more, but it might definitely be a great idea for a future version, so thanks for telling me about it!!
Is it an LG though? The APIs I’m using are WebOS specific