I believe #ActivityPub has some underappreciated ways of being flexible about this sort of thing, where at-account-at-house can point to the specific appliance whose built in server can handle requests.
The house server can specify a URI by IP address for the actor object representing the coffee pot.
Whether this is a good idea from a scalability stance I can't say off the top of my head, but it's an interesting feature.