SIMO.io Quick Start Guide

Set up your wire‑first SIMO.io system: place the hub, create an instance, pair Game Changer boards, and build your first automations.

Welcome! This Quick Start shows how to set up a SIMO.io wire‑first smart home: place the hub, create an instance, pair boards, and build your first automations.

1. SIMO.io brain center location

Every smart home installation begins with a first decision: where the central brain will run. A vast number of consumer systems put the brain in the cloud, which makes you 100% dependent on internet connectivity and third‑party services. Professional systems include a local hub installed on the property.

SIMO.io supports both models. You can run the brain in our cloud or use a plug‑and‑play local hub for privacy and fully autonomous operation during power outages.

General rule of thumb: if your internet connection is decent and your needs are small, you can omit a hub and still have a great SIMO.io experience. For anything serious or whole‑home, choose a local hub.

On the other hand, if you are building anything more complete, we recommend a SIMO.io hub. It provides autonomous operation, the full feature set, automatic backups, and power‑user tools like root access and direct programming.

If you choose a local SIMO.io hub, connect it to your internet router via Ethernet.

For resilience, place your router and SIMO.io hub on a UPS so the system stays online through power outages. Modern UPS units are affordable and can run network gear for hours or days.

2. Getting started with the SIMO.io app

1. Download and install the SIMO.io app from Google Play or Apple App Store.

2. Create an account.

3. You have no instances yet. Tap + Add New.

4. Tap Local if you have a hub, or Virtual for a cloud‑hosted instance.

Note: to invite someone later, they can tap Scan QR and join in seconds.

5. Name your instance and complete the form.

6. Your SIMO.io instance is ready.

Of course it is completely empty, except a few generic already preconfigured components. 

3. Hooking up the Game Changer boards

Our Game Changer boards are the pinnacle of the SIMO.io system. They fit standard 12‑unit circuit breaker boxes. A two‑board setup provides 36 I/O ports for relays, dimmers, and binary inputs, and two digital ports for I2C sensors or a DALI network.

These boards pack a ton of connectivity options to gather sensory information and deliver control to every room.

Grounding

Before you start connecting anything to it, connect your true home GND to the board's GND.

This ensures we don’t introduce phantom voltages when connecting devices and lets you use house ground for stable signaling. This step is important and prevents odd, hard‑to‑trace issues during installation.

PoE is brilliant

The preferred method is PoE over twisted‑pair Ethernet. This delivers uninterrupted power and a rock‑solid connection to every board.

Use a PoE switch connected to your router. Keep the switch, router, and hub on the same UPS for an outage‑resilient system.

Wi‑Fi fallback

If PoE is not possible, power the board with a 12 V DC driver. Connect GND to the negative pole and +12 V to the 12 V terminal.

Game Changer Mini boards include a built‑in AC‑DC converter and can be powered directly from mains.

 

 

4. Pairing the Game Changer boards

After wiring, press the Power button. The red LED turns on and stays on, indicating power.

The Status LED shows connectivity. On power‑up it cycles through checks, then blinks blue when in Bluetooth pairing mode and ready to pair with your SIMO.io instance.

Open the SIMO.io app. Tap the menu (three lines) and select Colonels. Your newly connected board appears here. Tap it to configure.

Name the board, select your connection method, and tap Connect.

The board reboots and runs checks. The Status LED slowly flashes green when fully connected to your hub and ready.

If it flashes orange, it cannot reach your local network. If it flashes yellow, it cannot reach your SIMO.io instance.

Keep it up to date

Once it's fully connected you will see some information regarding firmware version. If you see an update available, please initiate it before you do anything else. If you do that, the board will reboot and flash PINK for 10 minutes or so. Make sure you do not mess with it while it's doing it and make sure it has good internet connectivity.

It's a good measure of maintenance to check this interface from time to time and apply those updates periodically, at least once every 6 months as we sometimes find some issues that get's fixed or add new features.

5. Connecting devices

Connect appliances using SIMO.io modules and interfaces.

Binary Input Module: wall switches, bell buttons, motion, door/window contacts, smoke or flood sensors.

Relay Module: on/off loads—regular lights, valves (heating, ventilation, watering), pumps, blinds, gates, and some HVAC.

AC Dimer / DC Dimmer / 0-10 V Driver: control lights and devices that accept variable signals (Triac, PWM or 0–10 V).

Let's go through a few most common scenarios.

Binary Input Module - Simple but Powerful - Motion sensor example

Generic 12 V motion sensors are cost‑effective and reliable for security and automation. Hooking them up is straightforward. We recommend 12 V sensors because the Binary Input Module provides 12 V power from the Game Changer board. With your network on a UPS, each sensor remains available during outages.

Use CAT5 twisted pair wiring. Connect your motion sensor to the Binary Input Module in the following order:

Motion Sensor -12V → White/Green → GND
Motion Sensor +12V → Orange → 12V
Motion Sensor Relay → Brown → IN
Motion Sensor Relay → White/Brown → GND

This wiring pattern also leaves room for running I2C line, which allows adding MCP9808 temperature sensor later.

The Binary Input Module has a Pull‑Up switch, which pulls its signal high when the GND‑to‑IO loop is open. A motion sensor keeps the loop closed and opens it on detection. Best practice is GND signaling: route GND to the sensor and return GND to the IO terminal when idle. On motion the loop opens (signal high). If the sensor is disconnected or fails, the signal stays high, clearly indicating a fault.

Turn off your Game Changer board and plug the module into any free port except IO1 or IO2 (reserved for digital interfaces). Turn your Game Changer back on and verify operation. The module’s red LED turns on with motion and off when idle.

 

In the app, tap Add New + on the main screen.

SIMO.io is organized into Gateways—systems SIMO.io can access and benefit from. For Game Changer boards, use the SIMO.io Fleet gateway.

Select Binary Sensor (on/off). Then name it, set icon, zone, and category. Leave Show in app on for this demo. Use Notes for future details.

Any device can participate in the alarm system. For a motion sensor, set Alarm category to Security. Select your Game Changer board and port IO3.

The sensor is not inverted. It delivers a high signal on motion, so set Inverse = No. Leave Debounce at 50 ms. No hold time needed.

Tap Save. The board restarts. When the Status LED is flashing green again, the motion sensor is live and reporting events.

 

Long‑press any component to view its event history:

Switch — siren example

The Relay Module turns on/off almost any load. It’s the most common, robust control in professional installs: simple devices are easy to wire, replace, and scale—no fragile wireless gadgets required.

Example: connect a 12 V siren to the demo board. The siren sounds and flashes when 12 V is applied.

Feed 12 V from the Game Changer board—no separate driver needed. With the network on a UPS, the siren remains available during outages. Wire the siren through a Relay Module (normally on for high security, normally off for typical homes).

Place the siren on IO4 (for example) and share GND and 12 V with the Binary Input Module as needed.

In the app: Add New + → Gateway: SIMO.io Fleet → Type: Switch.

Defaults work for most cases. Options: invert relay logic, add slaves (linked switches), and attach button controls from any location.

Tap Save. The board restarts. Your Switch is ready—tap to activate the siren; tap again to stop.

Dimmers — easy and maintenance‑proof

Game Changer I/O ports accept modules for dimmable bulbs and devices expecting variable control (Triac, PWM or 0–10 V).

This approach is simple, modular, and maintainable. If a bulb fails, replace the bulb. If an LED strip wears out, replace the strip. If a driver fails, replace the driver. If a module fails, replace the module—no reprogramming or re‑pairing.

Example: AC Dimmer with a standard dimmable LED bulb.

Hot + Neutral: mains supply. Neutral + Load: to the bulb. Wire the circuit, power cycle safely (board off → mains on → board on).

Bulb at 100% on first power is by design. AC/DC dimmers default to normally on for resilience. For indoor lights on relays, we also recommend normally on wiring so homeowners can use breakers to control lights if needed.

In the app: Add New + → Gateway: SIMO.io Fleet → Type: AC/DC Dimmer | PWM Driver.

Useful parameters:

• Value units: %, 0–255, or device‑specific scale.
• Min / Max: range limits (e.g., 0–100%).
• Device Min/Max (%): module‑side boundaries. Many LED bulbs produce no light below ~15%—set Device Min ≈ 15% for consistent 0–100% control.
• Turn on/off times:  How quickly the bulb turns on/off
• Skew/curve: ease‑in/ease‑out response for on/off and dimming transitions.
• Slaves: Control multiple lights while this being a master.
• Controls: Use Binary Input Modules or Button objects to have button control.

Buttons and wall switches

With SIMO.io you can bind any physical button to any device on the local network. No need to hard‑wire permanent pairings up front.

If the target device is on the same board, control works even without the hub. If the button and target live on different boards, the hub must be available.

Buttons typically deliver a GND pulse to a Binary Input Module. With Neutral, Line, and GND routed across the property, a single signal wire is often enough.

Use a dedicated Button component when one button must control multiple devices, trigger automations, or target devices on other boards.

For simple same‑board control (switches, dimmers, blinds), many components accept direct port control in their own config forms.

Toggle switches work, but momentary switches unlock more control (single press on/off; hold to dim; double press to 100%).

Example: Add a momentary button for the dimmer configured above. Set the Binary Input Module pull‑up to on. Connect one wire to its IO and one to property GND.

In the app, long‑press the dimmer → Edit → Controls → Add new. Input: IO11. Button type: Momentary. Action: DOWN (we deliver GND on press).

Save and wait for the board to reload. Test: single press toggles, hold dims, double press sets 100%.

I2C sensors — cheap and simple

Game Changer boards support I2C sensors via the digital interface. A single I2C line can host many devices (up to 128 in theory — real‑world installs use fewer). Today we support temperature, humidity, and air quality; more are added over time.

For room heating control, add a temperature sensor first. Use CAT5 twisted pair and keep GND paired with SDA and SCL for signal integrity. If a motion sensor is already wired, reuse spare conductors to add an MCP9808 sensor inside the motion sensor box.

Use an I2C interface module. Follow this wiring diagram:

Insert the I2C module into IO2 and wire it accordingly.  

In the app: Add New + → Gateway: SIMO.io Fleet → Type: MCP9808 Temperature Sensor (I2C). Complete the fields and set the I2C address.

Note: MCP9808 supports 8 addresses; select via solder pads.

Save, wait for the board to reload, and temperature readings appear.

Units follow your instance setting (Celsius or Fahrenheit).

Radiator valves

With temperature readings in place, add a heating actuator. Many systems use manifold‑mounted radiator/zone valves for underfloor heating.

Valves are typically AC powered and come in normally closed or normally open variants. SIMO.io works with both via a Relay Module. We recommend normally open for resilience: if something fails, excess heat is safer than no heat. If you use normally closed valves, wire them via relay in a normally on fashion so valves stay open when power is present.

Once wired, the valve can be switched on/off from the app.

6. Putting things together

As soon as you have some devices connected to your SIMO.io instance you can start configuring actual smartness of your property, by adding various virtual components to the system. Let's see what we can do with those few components that we already have in the system.

Thermostat — full heating/cooling control

With a temperature sensor and valve added, create a thermostat to control room temperature across the day.

Add New + → Gateway: Generic → Type: Thermostat. Choose the temperature sensor. Add the radiator valve to Heaters. (You can also add cooling components.)

Modes: Dynamic (smooth response) or Static (strict target). Static keeps the valve open until the target is reached, then closes.

Bounds: set Min/Max for user adjustment. If your sensor has humidity, enable “real feel” to account for perceived temperature.

Save to add the Thermostat component.

Tap to open settings. Configure weekly/daily/hourly schedules and use the Hard override for temporary changes (e.g., vacation).

Alarm Group — extremely versatile

With a motion sensor and siren, you can build a basic alarm. Add New + → Gateway: Generic → Type: Alarm Group.

 

Add Alarming Components (the sensors this group watches). Only components assigned to an Alarm category are selectable—add your Motion Sensor.

  

Installations often include 5–30 sensors per group. You can also nest groups to build tree‑like alarm structures (e.g., whole‑home group controlling per‑floor groups).

Mark your main alarm group. Enable auto‑arm when everyone leaves. If you have smart locks, bind arm/disarm to lock state.

Notifications: when breached, send alerts to active users after an optional entry delay.

Breach events: add multiple actions at different offsets. For our demo, turn the siren on immediately on motion; turn it off on disarm.

Save. The Alarm Group appears in the Security panel. Slide to arm. If motion is active, it shows partially armed; when motion stops, it becomes fully armed.

On motion, the siren sounds and you receive a notification. Disarm to stop the siren. The app keeps a full event history.

Automatic lighting

Automatic lighting is one of the most delightful smart home experiences. SIMO.io can deliver fully automatic lighting, though we still recommend some physical buttons.

Different times call for different behaviors. SIMO.io includes a global state component that cycles through Day, Evening, Night, and Morning. Sleep, Away, and Vacation can be set manually or automatically.

Presence sensors (motion/door) are the second key element. Add ambient light conditions if desired.

Example: Add New + → Gateway: Automation → Type: Presence Lighting.

 

Use your motion sensor as the presence source. Hold time: 2 minutes (time after last motion to keep the light on).

Add an additional condition: Main State = evening.

Add your light and set it to 50% on presence.

 

You can add unlimited conditions and targets to support multiple scenarios in the same room.

Tap Save. If it’s Evening and motion is detected, the light goes to 50%. At Night the automation stops.

7. AI automations

What it does

AI reads your request and produces a working Python script bound to an AI script component. You can review, test, and edit it via the hub’s web admin.

Create your first AI script

In the app, tap Add New + → Gateway: Automation → Type: AI script.

Fill standard fields (name, category) and locate Request for AI assistant. Describe the behavior in plain language. Any language works.

Example request (English)

When Main State is Night, turn Dimable Bulb to 20% on motion.
If no motion for 2 minutes, turn them off.
Ignore triggers between 08:00–20:00.

Tap Save. Generation takes up to ~60 seconds.

Open the hub web admin to view and edit the generated Python script.

Adjust component bindings, thresholds, and timers as needed; save to apply.

Use comments in your script to document intent for future maintenance.

Tips for better results

• Be explicit about components (names/rooms) and triggers (“when motion in Hallway”).
• Include timing, bounds, and exceptions (“20% at night; off after 2 min”).
• Mention global state or schedules when relevant (“Only in Away”).

Troubleshooting

• If generation fails, simplify the request and try again.
• If behavior isn’t as expected, edit the script in web admin and retest.
• Keep a copy of working versions to roll back quickly.

8. Finish with Sentinel — one device per room

From basics to brilliance

The SIMO.io system is professional by default and happy with basic, inexpensive devices—relays, contact sensors, dimmers, thermostats. Your hub orchestrates them locally for predictable results. You can build a complete, reliable smart home this way, step by step.

If you’re willing to invest a little more per room, Sentinel is the easy all‑in‑one. It condenses a handful of devices and multiple app steps into one ceiling unit, cuts install and commissioning time, and unlocks the kind of precision—presence‑aware lighting, humidity‑aware comfort, whole‑home signals, voice that already knows your rooms—that feels like true magic.