Steps

  1. Open Occupancy intelligence → Settings → Import configuration for the intended property. Review the existing room mappings and devices so the import uses their correct identifiers and revisions.

  2. Paste Configuration JSON or CSV. JSON has rooms and devices arrays. CSV uses type, room_id, provider_room_id, provider_room_number, provider_device_id, kind, label and guest_approved columns; each row's type is room or device, and guest approval is true or false.

  3. Include the room mapping before its devices, or use rooms already mapped in this property. A device needs its room ID, provider device ID, control kind and label. Keep provider identifiers as text, and set guest approval only for physically verified addresses. Invalid JSON, unclosed CSV quotes and unsupported field values must be corrected before submission.

  4. For existing devices, use JSON with the current device id and expected_revision from setup. CSV device rows submit a new-device revision and are not an update mechanism for an existing device.

  5. Choose Validate and import, complete any security verification and wait for Configuration saved. A failed import rolls back its submitted changes; an uncertain network outcome still requires reloading the existing setup before another attempt.

  6. Review the saved room mappings and device entries, resolve any revision/addressing conflicts, and verify physical operation before enabling the separate Guest IoT remote property setting. Importing devices does not switch guest remote access on automatically.