Falaah Falaah AI

Locations and Devices

Record your buildings and rooms, group devices by the site they live at, pair a new tablet or screen with a setup code, and review every command sent to your fleet.

A location is a building. Rooms live inside it, and a room is what people book. Device locations are a separate, simpler list: the sites your tablets and screens physically live at.

When you’d use this

  • You run more than one building and bookings or reports need to tell them apart.
  • A new tablet arrived and needs pairing as a kiosk or a screen.
  • You are deploying twenty screens and do not want to pair them one at a time.
  • A screen is not responding and you want to see whether your command reached it.

Locations: buildings and rooms

  1. Go to Administration → Locations (/platform/locations). Owners and admins only.
  2. Select Add Location or, on an empty list, Add your first building. “The main building, the school, the community center: whichever you run.”
  3. Fill in the address, the responsible Person, Timezone, Capacity, Billing and Shipping addresses, a Description and Tags.
  4. Then Add rooms inside it. Each hall, classroom or prayer area is its own room under that building.
  5. Set up a facility to make a room bookable: give it rules and a rate card, and people can start requesting it.

The summary cards count Total Locations, how many are Active, how many are Assigned to entities, how many are Unassigned, Total seats across listed rooms, and Rooms without capacity so you know which rooms are not being counted.

One location can be marked Primary.

Posted occupant load

The occupant load your fire marshal or building department posts for a room is the record of truth. Capacity is your own estimate.

  1. Open the room and edit it.
  2. Enter Posted occupant load, as shown on the permit or certificate.
  3. Enter Permit or certificate stating it, for example “Place of assembly permit A-2024-118”. It is required whenever a posted load is entered.
  4. Save.

When you change the posted load, Muin keeps the previous value and the date of the change.

The facilities audit (the Audit check tab in Facility Rentals) reads these figures:

  • No posted occupant load on file for any room: the audit asks for the place-of-assembly permit or certificate of occupancy.
  • A room’s Capacity above its posted occupant load: the audit raises it for that room, citing the permit or certificate.
  • A posted load that changed: the audit names the old and new figure, so you can re-check bookings taken against the previous number.

Device locations

  1. Go to Administration → Device Locations (/platform/device-locations).
  2. Select Add Location and give it a Name (for example Ground Floor, East Wing, Prayer Hall), a Type, and optionally a Parent Location so you can nest sites. None (Top Level) leaves it at the top.
  3. Grouping devices by site lets you deploy, filter and report on them together.

This list is about where hardware lives. Bookable rooms are the Locations screen above.

Setup codes: pairing a device

  1. Go to Administration → Setup Codes (/platform/setup-codes).
  2. For one device, select Generate Code, then Add a Device. Muin shows Your new setup code with Copy Code, and the device claims it during setup.
  3. For many devices, select Generate Batch. Set Number of Codes, a Name Template (for example Kiosk-{n}), Tags (for example lobby, event-day), a Kiosk Configuration, and optionally an Exit PIN of 4 to 32 digits which is set once and applies to every device on that code.
  4. Pending Pairings lists codes issued but not yet claimed. Resume continues an unfinished pairing, Copy copies the code again, Regenerate issues a fresh one and Revoke kills it.
  5. Codes that have been used, have expired or were revoked are listed separately.

Fleet commands

  1. Go to Administration → Fleet Commands (/platform/managed-devices/commands).
  2. Filter by device ID, by status or by command type.
  3. The Commands tab is the history of what was sent; the Activity tab is what the devices did.

Use this to tell “the command was never sent” apart from “the command was sent and the device ignored it”.

What it affects

  • A location drives room booking, facility rentals, event venues and any report broken down by site.
  • Capacity on a room feeds the seat counts used by events and bookings, so a room with no capacity is invisible to those totals.
  • Revoking a setup code stops any device that has not yet claimed it from pairing.
  • An Exit PIN set on a batch code applies to every device paired with that code and cannot be changed per device afterwards from this screen.
  • Deleting a location does not delete the devices or bookings that referenced it; re-assign them first.

When it goes wrong

What you see What to do
“Failed to load locations” Reload. No location was created or changed.
“Location not found” after following a link The location was deleted. Go back to the list and pick another.
“Rooms without capacity” is non-zero Open each room and set its capacity so seats are counted.
“Unable to load locations” on Device Locations Reload. This is the device-site list, not the building list.
“No setup codes generated yet” Nothing is wrong. Generate one before setting up a device.
A device shows a code as invalid The code was revoked, expired or already used. Generate a new one.
“Failed to load command history” Reload. The absence of history is not proof a command was not sent.
A screen says it needs to be reset in Muin Use Reset pairing on that device under Operations Settings.

Next step