Skip to main content

SwitchBot temperature sensors

SafetyBrik can read live temperatures from SwitchBot sensors so your team doesn't have to open every fridge with a probe at the start and end of every shift. The reading still gets logged, the corrective-action prompt still appears if it's out of range, but the number comes from the sensor instead of someone's notebook.

This is an optional layer on top of the manual temperature flow. Manual entry is always available as a fallback.

SwitchBot is the alerting source

SafetyBrik reads sensor values when your team logs a check. Realtime out-of-temperature alerts continue to come from the SwitchBot app, not from Brikly. Keep SwitchBot push notifications enabled for whoever is on call - that's still the fastest way to find out a fridge has failed overnight.

What you'll need​

  • A SwitchBot account with at least one supported temperature sensor (Meter, Meter Plus, Outdoor Meter, Hub-connected meters)
  • The SwitchBot Hub Mini / Hub 2 paired with the sensors (so they're reachable from the cloud)
  • A SwitchBot API token and secret - you generate these in the SwitchBot mobile app under Profile > Preferences > Developer Options

Connect SwitchBot to Brikly​

Brikly connects one SwitchBot account per business, for all your sites. Owners, admins and members can connect SwitchBot; viewers see whether it is connected.

  1. Go to Settings > Integrations.
  2. Find the Temperature monitoring section.
  3. Click Connect SwitchBot.
  4. Paste your API token and secret from the SwitchBot app.
  5. Click Test connection, then Save & connect.

Brikly checks the credentials with SwitchBot before saving them. If they are wrong or SwitchBot can't be reached, the test says so, and nothing is saved until it works.

Only one SwitchBot account can be connected, so keep the sensors for every site on that account. Sensors on another SwitchBot account can't be bound: read those fridges by hand.

If SwitchBot stops accepting the saved token (because it was regenerated in the SwitchBot app, say), the card shows Needs reconnecting with "SwitchBot needs reconnecting. Connect it again with a new token and secret: your sensors stay bound." and a Reconnect SwitchBot button. Viewers read "SwitchBot needs reconnecting. Ask an owner or admin to connect it again: your sensors stay bound." If Brikly can't check the connection at that moment, the card says "We couldn't check whether SwitchBot is connected." with Try again.

Where to find your token and secret

In the SwitchBot mobile app, tap Profile > Preferences, then tap the app version number ten times. A new Developer Options menu appears at the bottom of the Preferences screen, and that's where the token and secret live.

Bind a sensor to a fridge or freezer​

Connecting the account makes sensors available to Brikly. Binding tells Brikly which sensor belongs to which piece of equipment.

  1. Go to Temperature checks (/safety/temperature-checks).
  2. Click Edit on the fridge, freezer, hot hold or display you want to monitor.
  3. Under Temperature sensor, choose a sensor in Bind a SwitchBot sensor. Sensors are listed by their SwitchBot device name (rename them in the SwitchBot app if the names aren't operator-friendly).
  4. Click Bind.

Bind acts straight away: "Sensor bound. Check via SwitchBot is ready for this equipment." It doesn't save the rest of the form, so save any other changes as usual. Once bound, the section shows Sensor bound with the sensor's name and its last reading, for example "Last reading: 3.1°C at 17 Jun 2026, 14:39".

Each sensor can be bound to one piece of equipment at a time. A sensor already on other equipment is listed greyed out, with where it is, for example "Meter 1, on Walk In Fridge, Station Road". When every sensor is in use, the section says "All your SwitchBot sensors are bound to equipment. Unbind one, or archive its equipment, to use it here." With no sensors at all it says "No SwitchBot sensors found. Connect a SwitchBot account in Settings > Integrations, or add a sensor in the SwitchBot app."

To unbind, edit the equipment and click Unbind sensor: "Sensor unbound. You can bind it to other equipment now." Archiving the equipment unbinds its sensor too.

If SwitchBot can't be reached when you bind a sensor or load the list, you see "We couldn't reach SwitchBot just now. Try again in a moment." If two people bind the same sensor at once, one of them sees "Someone changed this sensor's binding a moment ago. Refresh the list and try again."

Moving a sensor​

A sensor moves from one piece of equipment to another in two steps: unbind it there (or archive that equipment), then bind it here. Its readings stay with the equipment it was on.

A sensor on equipment at a site that has been switched off or removed is the exception, because nothing there can be changed: it can be picked, and reads, for example, "Meter 1, on Walk In Fridge, Station Road (closed)". Picking it says "Binding it here moves it from Walk In Fridge, Station Road (closed). Its readings there are kept." Bind then moves it in one step.

Use Check via SwitchBot on the daily checklist​

Once a sensor is bound, the daily checklist gets a small upgrade.

When a team member opens an opening or closing checklist that includes a temperature item linked to a sensor-bound fridge, they'll see a Check via SwitchBot button next to the temperature input. The button only shows for equipment at the checklist's site, so a checklist for all sites never offers another site's sensor. A sensor reading that can't be used for an item says "That reading can't be used for this item. Take the reading again or type it in."

A reading pulled from a sensor counts once, for the number it read, on the checklist's own day, week or month. A reading taken outside that day, week or month, used a second time, or sent with a different number is refused with the sentence above.

  1. They tap Check via SwitchBot.
  2. Brikly fetches the current reading from the sensor (typically under two seconds).
  3. The temperature input fills in automatically, with "From SwitchBot at 09:12" under it, and the in-range / out-of-range status updates. The box is locked to that reading.
  4. If the reading is out of range, it asks What did you do? just like a typed reading. The team member describes what they did about it: the checklist can't be signed off until they do.
  5. They sign the checklist off as normal. The reading saves to that fridge's temperature history with the source marked SwitchBot.

To enter a probe reading instead, click Type it in instead under "From SwitchBot at 09:12": the box clears, and what you type is saved as a manual reading. The pulled reading stays in the equipment's temperature history. If it was out of range, the checklist says "The SwitchBot reading stays in this equipment's temperature history. It was out of range, so add a corrective action to it there."

This means the team can do an opening sweep across every fridge in the kitchen with a couple of taps each, instead of opening doors and waiting for a probe to settle. The audit trail is identical to manual entry: timestamp, value, who logged it, in-range judgement, plus the source badge.

Manual entry still works

The Check via SwitchBot button is a shortcut, not a requirement. If your team prefers a probe reading, or the sensor is offline, they can type the temperature in by hand exactly as before, or use Type it in instead after a pull. SafetyBrik treats both readings the same way once they're saved.

What happens when a sensor is unavailable​

Sensors drop offline occasionally - flat batteries, a hub that needs rebooting, the SwitchBot cloud having a slow day. SafetyBrik is designed so this never blocks a checklist:

  • Check via SwitchBot fails gracefully - if Brikly can't reach the sensor within a few seconds, the button shows an error. The temperature input stays empty, or keeps a reading already pulled: "The reading pulled earlier still stands. Use Type it in instead to enter a probe reading."
  • Manual entry is still available - the team member just types the reading from a probe or the equipment's own display.
  • The checklist can still be signed off - there is no requirement that the reading came from a sensor. A manual reading carries the same weight in your records. Nothing is recorded about the failed lookup: the typed reading is saved as a manual one.
  • A sensor unbound since the page opened - Check via SwitchBot says "No SwitchBot sensor is bound to this equipment now. Type the reading in." and the button goes. The button also appears or goes straight after a bind or an unbind, without reloading.

If a sensor is offline for more than a few hours, check it in the SwitchBot app. SafetyBrik does not try to re-establish the connection on its own - the SwitchBot app and hub are the right place to triage hardware problems.

Check sensor on the reading board​

On the reading board, a unit with a bound sensor has Check sensor beside its reading box. It reads the sensor and records the reading in one tap, so the opening and closing checks of a sensor-bound fridge take a tap each. An out-of-range reading asks what you did about it, with Add it later, as below.

Reading a sensor from the history sheet​

A sensor reading can also be taken outside a checklist, from the equipment's temperature history sheet. If it is out of range, the sheet stays open and says, for example, "SwitchBot read 11°C at 15:00, which is out of range (acceptable: 1°C to 5°C). The reading is recorded." with a What did you do about it? box, Record corrective action and Add it later. A reading left without one shows an Add corrective action link in the history.

An out-of-range sensor reading is also written to the Audit log as Out-of-range sensor reading, a system event hidden behind Show system events. SafetyBrik doesn't send a notification for it: realtime alerts still come from the SwitchBot app.

Where SwitchBot readings show up​

A reading captured via SwitchBot is stored exactly like a manual reading, with one extra detail:

  • Equipment temperature history - the Source column shows SwitchBot instead of the checklist or Manual badge. A sensor reading used on a checklist shows once, as "SwitchBot · checklist".
  • Diary, Today and safety score - every SwitchBot reading, from a checklist or the history sheet, counts in the diary's out-of-range readings and the safety score, and on Today and in the Overview's temperature alert until it has a corrective action, each reading once.
  • EHO Report Pack - the EHO Report Pack's Temperature Log gives each sensor one row per day, with its lowest and highest reading, the number of readings and how many were out of range, then lists every out-of-range sensor reading on its own. Sensor readings taken on a checklist are listed with that checklist's readings. Out-of-range readings are counted in the summary and their corrective actions listed.

Removing the integration​

If you stop using SwitchBot, or change accounts, an owner or admin can disconnect it. Members do not see the Disconnect SwitchBot button.

  1. Go to Settings > Integrations > Temperature monitoring.
  2. Click Disconnect SwitchBot. Brikly asks first: Disconnect SwitchBot? with "Every sensor is unbound from its equipment, at every site. Readings already taken stay. To use SwitchBot again, connect it and bind each sensor again."
  3. Click Disconnect. Every sensor binding in the business is removed, at every site. Manual entry continues to work as before. If it can't be done, the dialog stays open and says why, for example "We couldn't disconnect SwitchBot. Try again."

Disconnecting does not delete any historical readings - the audit trail stays intact. If you connect SwitchBot again, bind each sensor to its equipment again.

Cross-references​