This is a very interesting project. Protocol choice on constrained hardware like this is always underestimated, most people default to JSON over HTTP, but on devices with limited MTU or battery constraints the overhead adds up really fast.

We have seen similar trade-offs working on binary encoding for our alerting systems; even a few hundred bytes difference per message changes what's feasible over BLE or LoRa. What protocol the intercom uses natively and how much of the HomeKit overhead is format vs transport?

The fork itself is not the problem, but presenting it as your own project. Put the upstream link high in the README, say clearly what you actually changed and don't bury attributions just at the bottom.

Nice work, well done. I'm also building a .NET open source project (emergency communications protocol and related systems). I'm curious about your experience contributing to dotnet/runtime. Was the PR process straightforward? Thanks.

This is what we do. We use AI for drafting but we never merge without doing a manual review of dependencies. Every package version is pinned explicitly, and our CI always runs a dependency scan before deploy.

The AI is fast at scaffolding, the bottleneck is still us catching what it gets wrong. NOthing is easy unfortunately

I will try this in Cursor. The C# tooling in VS Code has improved a lot. I'm curious to see how ReSharper adds to it. Thankyou