Impact from Weber shutting down cloud services for the June ovens?

[Taudris]

Just wondering what the impact on this will be come Sep 22.

[cmmichael]

Bumping this with ~5 weeks to go — Weber's cutoff is Sep 22, and as far as I can tell nobody has publicly started on a fallback.

Three things, in increasing order of ask:

1. Do you have a read on what happens to the plugin on Sep 22?

My assumption is everything stops: pairing, commands, and telemetry all transit api.junelife.com / messaging.junelife.com, so when those go the plugin has nothing to talk to. Worth stating explicitly in the README either way, since anyone installing this in the next month is buying a few weeks.

2. Could JUNE_CLOUD_PROTOCOL.md be published?

JUNE_INTEGRATION_SPEC.md §12 references it for the full protocol notes, but it isn't in the repo. Whatever's in there is the most complete public description of this protocol that exists, and its usefulness has a hard expiry date — after Sep 22 there's no live server left to check anything against. Even a rough dump would be worth more now than a polished one in October.

3. Would you take a PR making the API hosts configurable?

Right now they're three constants in src/settings.ts:

export const JUNE_API_URL       = 'https://api.junelife.com';
export const JUNE_MESSAGING_URL = 'https://messaging.junelife.com';
export const JUNE_WS_URL        = 'wss://messaging.junelife.com/1/messaging/websocket/companion';

(plus CAMERA_HOSTS in src/protocol-decode.ts, which also allows june-api.s3.amazonaws.com)

The reason this matters more than it looks: the oven verifies command signatures itself against the Ed25519 key it trusted at pairing — per the spec, June's cloud never signs anything, it only relays. So a replacement server doesn't have to impersonate June's authority, just its transport. If someone does stand one up, this plugin becomes a working client against it by pointing those constants somewhere else. Making them overridable now costs almost nothing and keeps the option open.

The open question is whether the oven pins certificates, which decides whether a DNS-redirect approach works at all or whether it needs firmware access. I haven't found anyone who's captured traffic from the oven side — every public artifact traces back to Frida on the Android app. I'm planning to put mine behind mitmproxy and find out, and I'll report back here either way.

Happy to do the settings PR if you're open to it.