peedub

Ok, sure. But that’s not what you’ve shown in your post. What you’ve shown definitely won’t do what you want.

HomeKit Bridge is used to get device from Home Assistant into HomeKit. There’s another integration, HomeKit Devices, that will do what you’re wanting.

That was tough! I definitely needed to phone a friend for the latter half.

I found it easy to get the front end showing but the backend stuff required a little trial, error, and searching to get sorted. Here’s a part-example of what I needed to make sure the correct traffic was sent to the back end (this is using a yaml file, not inline in a compose file):

rule: "(Host(`domain.com`) && (PathPrefix(`/pictrs`) || PathPrefix(`/api`) || PathPrefix(`/feeds`) || PathPrefix(`/nodeinfo`) || PathPrefix(`/.well-known`))) || (Host(`domain.com`) && Method(`POST`)) || (Host(`domain.com`) && Headers(`Accept`, `application/activity+json`)) || (Host(`domain.com`) && Headers(`Accept`, `application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\"`))"

I also decommissioned mine as I was seeing comments and posts coming up a lot quicker and more reliably on the lemmy.nz instance.

I second this. I’m a big fan of homepage. Easy to set up so long as you don’t mind a yaml config file (you can copy and paste the examples if you’re new to the format).

It’s called homepage