I just filed a bug about this and sent github.com/tailscale/ta... as a start.

Lukas & Team - Smart Home Fix: August

August Local API: HomeAssistant Connection Troubleshooting

#August #LocalAPI #ConnectionIssue

🔍 Full Report: https://www.digitalhomefaults.org/august/local-api/august-local-api-homeassistant-connection-fix

gist.github.com/lbruno/5dd8c...

yous should brace yourselves, there's some major seniority happening here :) i had my eyebrows singed by how fast Claude generated this content

this is drunk-intern level, if that:

let url = format!("http://local-tailscaled.sock/localapi/v0/whois?addr={}", ip);

Are you curious about working with AI, but aren't sure where to start? I have a quick high-level overview that can get you set up fast. You can reach the local models through endpoints, too.

Leave a comment if you try this project out!

www.linkedin.com/posts/anothe...

#LocalAI #APIProject

i was testing a ton of changes (lots of recompiling, compose up+compose down, etc) today and i think i broke something...

http: TLS handshake error from [X.X.X.X]:63283: Get "http://local-tailscaled.sock/localapi/v0/cert/idp.[tail-net].ts.net?type=pair&min_validity=0s": context deadline exceeded

NatureRemoのLocalAPI，間を空けずに連続で叩いてると404しか返さなくなるのは仕様なのか手元のこいつがおかしいのか

For that you need the localapi, which is what the CLI queries to get the info you want. It’s not super well documented but if you look at the CLI source it’s not too hard to follow.

Incredible improvements in @payload.dev 3.0, especially the LocalAPI—super useful for many common single-client JS projects. Simpler and faster!

payloadcms.com/blog/payload...

Wish there was way you (tailnet status) can give a hint. Maybe ping latency for each DERP relay (probably better than trying to GeoIP/distance calculations), imagine if localapi included this info, refreshed every packet sent, a la webrtc internals.

Can I presume that if the "internet" internet is down, but peers are on same net (and have once discovered each other), they will keep seeing each other (via localapi) for the duration the internet is down (even days?)?

That said, clients that need to find "the right" backend to call for a service only need to know about nodes they have ACL access to, so it can be perfect.

The really nice thing about callling the localapi (aka --json) is that it's all local, thus resilient even when your Internet link is down.

I followed one of your examples I found for the tsnet package that uses the LocalClient so I think it's using localapi under the hood

nice! and if you don't mind sharing, how are you getting the identity info in there? with the ID headers, or through our localapi?