smiletolerantly

Image

“Some practical notes”

Looks inside

Three slop in a trenchcoat

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:

• install quick actions app on the shield
• reconfigure Netflix button on the shield remote to open quick actions popup
• add two quick actions, night and day, that curl simple HTTP endpoints on a VM I set up
• on the VM, a simple flask server listens, and then sends the (too complex for the quick actions app) API request to the TV.

(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.

Fleet Commander 🚀

• Fleet: 6–10 devices · 11–20 TB
• Motivation: Privacy & data ownership, Independence from Big Tech & subscriptions, Learning & experimenting
• My MVPs: Jellyfin, Home Assistant, Immich, Proxmox VE, nixos-mailserver

Monkey’s paw curled, huh

Which shouldn’t really be an issue since you should only host on 443, which tells bots basically nothing.

Configure your firewall/proxy to only forward for the correct subdomain, and now the bots are back to 0, since knowing the port is useless, and any even mildly competent DNS provider will protect you from bots walking your zone.

Sorry, saw this only just now. I don’t really have any guides to point to, so just the basic steps:

• host jellyfin locally, e.g. on 192.168.10.10:8096
• configure some reverse proxy (nginx, caddy, in my case it’s haproxy managed through OPNSense)
• that proxy should handle https (i.e. Let’s Encrypt) certificates
• it should only forward https traffic for (for example) jellyfin.yourdomain.com to your Jellyfin server
• create a DNS entry for jellyfin.yourexample.com pointing either to your static IP, or have some DynDNS mechanism to update the entry

90% of this is applicable to any “how to host x publicly” question, and is mostly a one-time setup. Ideally, have the proxy running on a different VM/hardware, e.g. a firewall, and do think about how well you want/need to secure the network.

In any case, you then just put in jellyfin.yourdomain.com in the hotel TV.

I have never used Tailscale. I have also Jever seen anyone in the wild recommend it and explain what exactly the use-case is beyond plain, old, reliable, open source WireGuard.

So yeah, agreed.

Also I have been hosting Jellyfin publicly accessible for years with zero issues, so idk… I also dint k ow what the “you have to use Tailscale for jellyfin” people are doing with TVs/Firesticks/… in hotels, airbnbs,…