SmartHomeShop Docs

Troubleshooting

Rapidly flashing red status LED on a VLAN without internet

If your UltimateSensor Mini v2 continues to report measurements but its red status LED flashes rapidly after startup, the firmware update check may be blocked by your firewall or IoT VLAN.

The local UltimateSensor Mini v2 firmware reads a small version manifest from SmartHomeShop GitHub Pages. This check only determines whether new firmware is available. It does not send sensor readings, Home Assistant data, Wi-Fi passwords or API keys to GitHub.

ESPHome's standard status LED reports errors from every firmware component. A blocked update check can therefore look like a device startup error even while UltimateSensor Mini v2 itself is working normally.

Confirm the cause

Open the UltimateSensor Mini v2 logs in ESPHome and look for http_request.update or Failed to fetch manifest. If these messages are not present, investigate power, network and sensor initialization before changing the update settings.

Disable scheduled firmware checks

  1. Open the ESPHome Device Builder app/add-on in Home Assistant. This is different from the ESPHome integration under Settings > Devices & services.
  2. Find UltimateSensor Mini v2 and select Take control or Adopt.
  3. Save a copy of the generated YAML, including its API encryption key.
  4. Select Edit and add this block at the bottom of the YAML, without extra indentation:
update:
  - id: !extend firmware_update
    update_interval: never
  1. Save the file, select Validate, and then select Install > Wirelessly.

After installation, UltimateSensor Mini v2 keeps measuring and communicating locally with Home Assistant, but it no longer performs scheduled firmware checks. You can still update it later through ESPHome or the SmartHomeShop web flasher.

ESPHome still downloads the UltimateSensor Mini v2 packages: configuration from GitHub while compiling. That request is made by the Home Assistant/ESPHome host, not by UltimateSensor Mini v2 itself.

If validation says that firmware_update does not exist, remove the block again and install a current UltimateSensor Mini v2 firmware version first. A rapidly flashing LED that remains after this change can indicate another real firmware or hardware error.

This guide covers common UltimateSensor Mini v2 issues.

mmWave Radar Issues

Standard firmware uses LD2450 for zones and target tracking. If LD2460 upgrade firmware is installed, LD2460 physically replaces LD2450. Use its target 1-5 X/Y/Distance/Angle entities with the shared Room Designer polygon and exclusion zones.

Presence Always On

Symptoms

  • Room shows occupied when empty.
  • Lights never turn off.
  • LD2412 move or still energy remains high.
  • LD2450 keeps reporting a target outside the real room.

Fix

  1. Empty the room completely.
  2. Stop fans, moving curtains and other moving objects.
  3. Run the LD2412 background calibration. The LD2412 Dynamic Background Correction button is disabled by default, so enable it first.
  4. Lower LD2412 Maximum Distance Gate if the room is smaller than the configured range.
  5. Tighten LD2450 Tracking Zone boundaries, or adjust LD2460 placement/filtering if the upgrade firmware is installed.

Detecting Through Walls

mmWave radar can detect through thin drywall, wood and some furniture.

Fix

  • Lower LD2412 maximum distance gate.
  • Tighten LD2450 Tracking Zone 1 X1/Y1/X2/Y2 boundaries.
  • Move LD2450 zone boundaries away from walls.
  • On LD2460 firmware, verify mounting height and angle, reduce the hardware detection sector and tighten Room Designer zones.

No Detection

Fix

  • Increase LD2412 Maximum Distance Gate if the range is too short.
  • Check the sensor is aimed at the monitored area.
  • Check that zones are not too small.
  • Factory reset radar settings and recalibrate if needed.

Zone Occupancy Is Wrong

Fix

  • Confirm LD2450 X/Y coordinates while walking around the room.
  • If LD2460 firmware is installed, confirm target 1-5 X/Y/Distance/Angle values and the shared Room Designer zones.
  • Set zone X boundaries left/right of the target area.
  • Set Y boundaries from near to far distance.
  • Increase occupancy off delay if the zone flickers.

CO2 and Climate Issues

CO2 Looks Wrong

Fix

  1. Ventilate the room with fresh air.
  2. Wait until readings stabilize.
  3. Press CO2 Manual Calibration. This button is disabled by default, so enable it first.
  4. Do not calibrate with people in the room.

Temperature Too High

Likely causes

  • Direct sunlight.
  • Nearby heat source.
  • Poor airflow around the housing.
  • Electronics heat inside the enclosure.

Fix

  • Move the sensor or improve airflow.
  • Compare with a reliable thermometer after 20-30 minutes.
  • For a small correction, use the Temperature Offset entity. For a permanent correction, raise the scd41_temperature_offset substitution in ESPHome and reflash: a higher value lowers the reading.

Humidity Seems Wrong

Calibrate temperature first. Humidity compensation depends on temperature accuracy. If humidity still needs a correction, use the Humidity Offset entity on the device page.

VOC or NOx Seems Unstable

SGP41 values are relative indexes and need runtime to stabilize after flashing, moving or long power-off periods. Judge trends over hours, not individual readings.

SPS30 Issues

No PM Values

  • Confirm you have the Complete variant with SPS30 installed.
  • Confirm you flashed the matching Complete firmware.
  • Wait for the sensor to initialize.
  • Check that the entities are not disabled in Home Assistant.

Network Issues

Hotspot Not Visible

  • Mini v2 fallback SSID is ultimatesensor-mini (older firmware: ultimatesensor-mini-v2).
  • Mini v2 fallback password is the same as the SSID.
  • The hotspot only appears if WiFi is not configured or connection fails.
  • Power cycle the device and wait 1-2 minutes.
  • Open http://192.168.4.1/ manually if captive portal does not open.

Ethernet or PoE Not Working

  • Ethernet requires the Ethernet firmware variant.
  • Connect Ethernet before switching to Ethernet firmware.
  • Check PoE switch/injector compatibility.
  • Check your router DHCP list for the new IP address.

Entities Missing in Home Assistant

  • Some entities are disabled by default, such as CO2 Manual Calibration, LD2412 Dynamic Background Correction, Factory Reset and the firmware update entity.
  • Open the device in Home Assistant and enable hidden entities.
  • Update firmware if expected LD2412/LD2450 or LD2460 entities are missing.
  • LD2460 entities only appear when the matching *-ld2460.yaml firmware is flashed on hardware where LD2460 replaces LD2450.
  • Re-add ESPHome integration by IP if discovery fails.

Mini v2 Feature Confusion

Mini v2 does not have:

  • Barometric pressure
  • PIR
  • Microphone
  • Speaker
  • Media player
  • Voice assistant
  • Local wake word

Use regular UltimateSensor v2 if you need voice assistant or PIR.

Related