{"version":"2.1.281","anchor":"roompresence-wiring-gains-namessilent-remote-status-forwar","canonical_anchor":"roompresence-wiring-gains-namessilent-remote-status-forwar","heading":"Room\/presence wiring gains namesSilent; remote status forwards deviceMcpQuestion","tier":"internal","area":"Remote Devices","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/roompresence-wiring-gains-namessilent-remote-status-forwar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Room\/presence wiring gains namesSilent; remote status forwards deviceMcpQuestion\n\nInternal wiring adds a `namesSilent` callback for shared rooms and passes `deviceMcpQuestion` along in remote status updates\n\n**Unclear.** The finding does not say what `namesSilent` or `deviceMcpQuestion` do for a user.\n\n**What**\n\nTwo small internal additions:\n\n- `namesSilent`: a callback, tied to a room's web address, now handed to the code that manages shared rooms and consent.\n\n- `deviceMcpQuestion`: a value now included in a remote status update, next to `servedSettingsChanged`.\n\n**Why**\n\nThese are plumbing changes. Nothing new appears on screen from them alone.\n\n- Area: Remote Devices\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}