Troubleshooting

For a controller that already responds, check missing or incorrect room-sensor readings or Auto-mode settings.

On this page

Start with the failing connection

Scroll sideways to read all columns.

What you observeStart here
Computer cannot see the boardUSB detection
No local web page or network connectionWi-Fi and connectivity
Web controls work but the app does notHome Assistant, Apple Home or Matter pairing
App connects but the unit ignores commandsIndoor-unit and CN105 control
Room reading is wrong or missingTemperature source checks
Yellow pulse or repeated restartingSafe-mode recovery

The status light is on or blinking

What the light does while you hold the button

Check the button action reference first: some holds erase pairings or Wi-Fi credentials. Pairing actions happen when you release the button, but the Wi-Fi reset happens at 10 seconds, while the button is still pressed. For planned changes, see restart and reset options.

The light is pulsing yellow

HomeKit-compatible safe mode keeps only Wi-Fi and the web interface running. Use the IP address from your router. The .local address does not work. The page shows a safe-mode banner. Update over Wi-Fi or use USB recovery.

On Matter-compatible firmware, safe mode offers only the backup setup network and cannot install an update over Wi-Fi. Reinstall the firmware over USB.

See status lights for the yellow safe-mode pulse.

If safe mode returns after reinstalling, check wiring and power and collect diagnostics for support.

Flashing and USB

Controller is not detected over USB, or no serial port appears
  1. Use a USB data cable directly to the computer. Try another known data cable or port.
  2. Use desktop Chrome, Edge or Brave. Close other serial monitors holding the port.
  3. NanoC6 and Atom S3 Lite use native USB and need no USB-to-serial driver. A DIY board with a CP210x or CH340 bridge may need its maker's driver.
  4. If still absent, enter download mode. On NanoC6, hold the top button while connecting USB. Other boards have their own procedure.

Disconnect CN105 before using USB. Follow the safe removal and reinstallation procedure.

Firmware installation fails or times out
  1. Confirm USB is the only power source. Try a short data cable directly to the computer.
  2. Close other programs using the serial port and reconnect in the flash tool.
  3. If download mode is needed, follow the board's procedure. On NanoC6, hold the top button while connecting USB.
  4. Retry. If it fails again, save the error, selected firmware and board for support.
"Browser does not support Web Serial" message

Use the flash tool in desktop Chrome, Edge or Brave. Safari and Firefox do not support USB flashing. After installation, you can continue setup on a phone.

Wi-Fi and connectivity

Web interface does not load
  1. Connect to the controller's local network and open http://<controller-ip> using its IP address from the router. Some devices and networks cannot open .local addresses.
  2. Use http://, not https://.
  3. If the controller lost its network, follow Wi-Fi recovery.

If the page opens but heat-pump readings are missing, follow CN105 checks.

Setup Wi-Fi network does not appear

A fresh Matter-compatible installation receives Wi-Fi credentials during Bluetooth commissioning. It has no setup network.

  1. On ESPHome, wait at least a minute after power-on and look for serin-XXXXXX, password serinlabs.
  2. On HomeKit-compatible firmware, wait at least a minute after power-on and look for Serin-XXXX, password serinlabs.
  3. If previously configured, check your router's device list: the controller may already be connected.
  4. If its saved network is unavailable, follow network recovery.
Controller is connected to Wi-Fi, but its IP address cannot be found
  1. Look for the controller in your router's connected-device or DHCP client list. On ESPHome, the dashboard also shows its address.
  2. Join the same local network. Guest/client isolation can block access between devices.
  3. Open http://<controller-ip>. For hostname alternatives, see Open the web interface.
Controller repeatedly disconnects from Wi-Fi
  1. Use a 2.4 GHz network. Check signal strength and whether other devices also disconnect.
  2. Metal air-handler cabinets can weaken Wi-Fi. A longer cable can allow better placement. Switch off power at the breaker before opening the unit or moving its cable.
  3. For a new router, network name or password, follow Change Wi-Fi.
  4. If disconnects continue, collect diagnostics and note whether the controller restarts or only loses Wi-Fi.
Cannot open the setup page at 192.168.4.1

For a fresh Matter-compatible installation, use Matter commissioning. The setup-network checks below apply only to a previously configured controller's backup setup network.

  1. Join the controller's setup network. Accept staying connected if your phone warns it has no internet.
  2. Enter http://192.168.4.1. Temporarily disconnect any VPN routing local traffic elsewhere.
  3. After saving Wi-Fi credentials, rejoin your home network and find the controller's new address in the router.
Change Network leaves the controller on its old Wi-Fi

The page shows no error if the new network fails. If the network name under Network · Wi-Fi has not changed after a minute, select Cancel, check the password, and try again.

The saved Wi-Fi network is no longer available

For HomeKit-compatible or previously configured Matter-compatible firmware:

  1. After five minutes without its saved network, the controller opens a backup setup network named Serin-XXXX.
  2. Join that network with password serinlabs, then open http://192.168.4.1.
  3. Enter the new network name and password.

On ESPHome, the standard configuration opens a fallback network named serin-XXXXXX, password serinlabs, when it cannot connect. Join it and open http://192.168.4.1. See Wi-Fi settings for a customized configuration.

After reconnecting, return your phone to the home network and check control. A newly flashed Matter controller receives Wi-Fi details during app pairing.

Home Assistant and ESPHome

Controller does not appear as "Discovered" in the ESPHome dashboard
  1. Confirm the controller is in your router's Wi-Fi device list.
  2. Check that Home Assistant and the controller can reach one another. Discovery uses mDNS. Guest or client isolation can block it.
  3. Follow adoption and integration. The ESPHome dashboard and Home Assistant's ESPHome integration are separate setup tasks.
  4. If discovery still fails, collect the device IP, firmware and logs before reinstalling.
Installation fails or times out after selecting "Adopt"
  1. For a compile failure, check available Home Assistant/ESPHome resources and the reported configuration error. The first build can take several minutes.
  2. For an upload failure, confirm the controller is reachable at its IP and no firewall or guest isolation blocks it.
  3. After replacing a configuration, compare its device name, API key, OTA password and Wi-Fi secrets with your backup. See credential preservation.
Climate entity is marked "unavailable" in Home Assistant
  1. Try the web page or ESPHome logs. If neither opens, restore network access.
  2. Check Home Assistant's ESPHome integration. If credentials changed, restore the configuration and credentials.
  3. If the device is online but heat-pump readings are missing, follow CN105 checks.
  4. Capture the failure in logs for support.
Wireless firmware update fails in ESPHome
  1. Save the error and identify whether compilation or upload failed.
  2. For upload problems, check the controller's IP, OTA password and network reachability.
  3. Follow ESPHome update instructions for your configuration.
  4. If unreachable, use USB recovery. Read its settings-reset warning first.

Apple Home and HomeKit

Controller does not appear in Apple Home during pairing
  1. Put the controller and phone on the same local network and open the controller's web interface.
  2. Check pairing status under HomeKit. For an existing pairing, use Manage app pairings. Otherwise, follow the setup-code instructions.
  3. Check that your router allows local discovery. Guest or client isolation can block it.
"Accessory Not Found" or pairing fails
  1. Check Wi-Fi access to the controller.
  2. Use the installed firmware's code. HomeKit and Matter codes differ. Apple Home supports both routes.
  3. If previously paired, follow the pairing reset procedure, including removing the old thermostat from the app.
  4. Retry. If pairing still fails, collect diagnostics.

Matter apps

The app cannot find the controller during Matter setup
  1. Check your app's hub requirements. Enable local IPv6 and keep your phone near the controller for Bluetooth commissioning.
  2. Use the Matter QR code or 11-digit code from the flash tool. HomeKit codes will not work.
  3. If already paired to another app, use Open Pairing Window.
  4. For a missing code, follow code recovery. A missing browser record does not require erasing the controller.
The app warns that the Matter accessory is uncertified

The Matter-compatible firmware is not certified. Your app may ask you to accept an uncertified accessory before continuing. See your app's setup instructions.

Matter pairing finishes, but the indoor unit does not respond

Try a mode or target-temperature command in the web interface. If that also fails, follow CN105 control checks. Missing fan or vane controls are a separate app capability limit.

Indoor unit and temperature

CN105 is connected, but no data appears or the climate entity is unavailable
  1. Confirm the indoor unit has power and supports CN105. CN110 is not a substitute.
  2. Switch off power at the breaker before touching connectors. Check both ends against the wiring reference. Replace the cover before restoring power.
  3. Check logs for serial errors. Some units, including SEZ-KD ducted units outside North America and PEA-RP ducted units, need 9600 baud. On HomeKit-compatible or Matter-compatible firmware, use Device → Advanced → CN105 Baud Rate. On ESPHome, set baud_rate in the UART block. If the rate change does not establish a connection, power-cycle the indoor unit at the breaker.
  4. For a DIY cable, check pin mapping and connections, or test with a known-good assembled cable.
  5. If readings remain absent, collect diagnostics with model and board details.
Temperature readings are incorrect or missing
  1. Check the selected temperature source. A sensor visible in an app is not automatically used for control.
  2. Check that the remote source has a fresh reading. For an ESPHome source forwarded by Home Assistant, check its entity, source selection and °C/°F setting. See sensor setup.
  3. Compare sensors at the same location before calibrating. Ceiling return-air temperature can differ from the occupied room. See temperature control.
  4. If the indoor unit's own reading is missing, follow CN105 checks. Some units report 0°C until the compressor first runs. Note when readings are missing.
Commands are sent, but the indoor unit does not respond
  1. Try a supported mode or target change from the local web interface. If it works, investigate the app or integration.
  2. If local control also fails, check heat-pump connection status and readings. Follow CN105 checks for a missing connection.
  3. Check available modes and vane settings. Firmware cannot add a missing mode or vane motor.
  4. Check if a remote, app or automation changes the setting back. Record a repeatable command and reported state for support.

Room sensors and settings

Room-sensor readings are missing or incorrect

Scroll sideways to read all columns.

What you seeWhat to check
The Bluetooth scan finds nothingCheck the battery and insulation strip, bring the sensor near the receiver, and confirm its exact model is supported. In the controller web interface, enable remote sensors and repeat the scan after it finishes. Already-added sensors appear in the source list rather than as new scan results. In Home Assistant, check that the Bluetooth adapter or controller proxy is present.
Several identical sensors appearAdd one powered thermometer at a time, note its Bluetooth address, and rename it before adding the next. Signal strength alone does not identify a room.
The thermometer is listed but the room reading does not follow itSelect its row in Single mode or include it in Average. With ESPHome, check the configured temperature entity ID and unit. If a Room Temperature Source selector is present, select Home Assistant or the intended Link.
A source is stale or the controller keeps falling backCheck battery, reporting age, and reception at its final location. For the Home Assistant route, also check Home Assistant and the controller's connection to it. Confirm the timeout allows for the sensor's reporting interval.
The temperature is wrongCheck the selected source and °C/°F setting first. Compare two thermometers side by side before adding an offset. In Average mode, inspect every checked source and its correction.
The sensor stopped after replacing the ESPHome YAMLConfirm the sensor's entity ID, unit, and source selection. Re-enable Home Assistant Bluetooth proxy if it receives the thermometer, and retain Serin Link sensor support if you use the Link.

If these checks do not resolve it, collect diagnostics or ESPHome logs and include the thermometer model, firmware version, chosen source, reporting age, and timeout in your support request.

Check that the built-in sensor takes over when a thermometer stops reporting

To check fallback, note the configured timeout, temporarily remove power from the selected thermometer, and watch the controller through that interval. With one remote source, the controller returns to the built-in sensor. In an average, other fresh sources continue to contribute. Restore the battery and confirm the source resumes. For ESPHome, use the remote_temperature_timeout in the installed YAML. The web-interface timeout belongs to HomeKit-compatible and Matter-compatible firmware.

The target temperature or mode changes back

If a target or mode changes back, temporarily pause schedules and automations and check other apps, a paired Serin Link, and the handheld remote for competing commands. Repeat the change from one control. If the unit still does not respond in a fixed mode, use the control checks and inspect any reported error.

Updates and repeated restarts

OTA update fails or the controller does not respond
  1. If reachable, reload the web page and check the installed version. Save any update error.
  2. Follow the update guide for your firmware and install method.
  3. For safe mode, use safe-mode recovery. If unreachable, use USB recovery.
  4. If the problem returns, check power and cable connections and collect diagnostics.
The version did not change after an update
  1. Reload the web page to refresh the Installed version.
  2. If unchanged, the upload may be incomplete or the controller may have rolled back after a startup failure.
  3. Follow the update procedure again, keeping the page open and phone awake until completion.
  4. If repeated, send the update result and Copy Diagnostics to support.
The Versions menu fails
  1. Couldn't reach the release server. Check your phone or computer's internet connection, then select Try again. The browser fetches the list when you open Versions. The controller does not need internet access.
  2. No published builds for this board. No release is available for your board. Custom builds may have no Versions button.
  3. Use a suitable build with manual upload or the flash tool. Save other errors if retrying fails.
Install failed or Upload failed appears in the web interface

If the controller refuses the file, the message after "Upload failed:" gives the reason:

Scroll sideways to read all columns.

MessageWhat to do
Not an app imageUse an application file for your board, not a complete flash image.
Firmware is for a different chipThe file is for another board. Download the file for your board.
Firmware is a different applicationHomeKit-compatible and Matter-compatible firmware cannot replace each other over Wi-Fi. Use the flash tool to switch firmware.
Upload stalledThe Wi-Fi connection dropped during the upload. Try again.

Looking for a maintenance task?

How to reset the controller to factory settings

Compare reset options before proceeding. A factory reset erases Wi-Fi credentials, app pairings and settings. Network or pairing resets preserve the rest. On HomeKit-compatible and Matter-compatible firmware, the control is Device → Advanced → Factory Reset… in the web interface. ESPHome has no factory reset in its web interface. Use USB recovery for a clean start.

How to switch between firmware versions

For a newer version of the same firmware, use Update firmware. To change between ESPHome, HomeKit-compatible and Matter-compatible firmware, follow Switch firmware and USB recovery.

Contact support

Collect diagnostics, then contact Serin Labs or ask in Discord. Include the indoor-unit model, board, firmware and checks you tried.

Last updated

Browse the manual ↑