Connect rooms, floors and calendars
Keep the display in the same Spaze project and make its location and schedule sources agree.
Before you begin
- Confirm the project and approved device credentials.
- Have a known room, real floor/zone relation and test bookings available.
- Check Outlook or Google ingestion independently from the display connection.
Product design guide: these are the required Signage workflows, not a claim that every step exists in the reviewed overview branch. Check the rollout guide and your installed build before use.
Step by step
Start with the shared project
Use the same Spacetime project as the rest of Spaze. The reviewed live overview reads resources, resource_kinds, bookings and booking_lines. It also includes mock, advertising and offline states; sample content is not proof of a live connection.
Map real places
Use signage_places for resource-to-floor/zone relations. Resolve the appropriate floor_plan_url or layout_bg_url for the actual place. Do not create one fake floor per resource kind. Verify that a room’s marker and card refer to the same resource.
Bring together today’s schedules
Use signage_schedules for the unified booking and ingested-calendar windows, and enrich with the room and booking details needed on screen. The qat view includes Spaze bookings as well as external schedules: do not add those same bookings twice when combining it with raw booking tables.
Add the session detail deliberately
Meeting cards need a title and booker. In-room needs attendees or current gym employee names and an event meeting link. These fields are not all present in the reviewed signage_schedules projection; connect and validate the additional data before exposing the related UI.
Verify freshness and time
Test a known Spaze booking and an ingested Outlook or Google event on the correct local day. Check the device clock, resource mapping, connection state and offline indication. Keep the view read-only; Graph calendar write-back belongs to booking work.
You’re ready when
The device shows the correct real place and a non-duplicated schedule, with only verified session detail and actions.
Troubleshooting
- Sample rooms appear instead of live rooms
- Check project authorisation, saved credentials and the source connection. The reviewed overview can display mock data; do not mistake that for successful provisioning.
- A booking appears twice
- Check whether the same Spaze booking was supplied through both signage_schedules and the raw bookings/booking_lines feed. Preserve source identity when assembling the day view.
- Rooms appear but a calendar event does not
- Check ingestion status, matching resource IDs, event time and active status. Resource availability and calendar ingestion are separate checks.
Technical details
- Current live overview feed
- resources, resource_kinds, bookings and booking_lines; project-scoped resource and booking queries.
- qat place and schedule views
- signage_places supplies floor/zone relations and floor_plan_url. signage_schedules supplies active external schedules and Spaze booking windows. Its current fields do not include attendee lists or event join links.
- Display identity
- The wizard persists the device’s project and credentials. ?project and ?token are target post-wizard debug overrides, not an installation recipe.
Common questions
- Does a resource kind define a floor?
- No. Meeting rooms and gym resources are categories, not places. Use real signage_places relationships.
- Does having calendar ingestion enable meeting join?
- Not by itself. Joining also needs the event’s Teams or Google Meet link to reach the bound session.
- Is there a Copperwired-only branch to install?
- The requested product contract uses one app and the shared project. Customer-specific configuration must not require a separate product fork.
Still stuck? Tell support what happened and which step you reached.
Email support