Troubleshooting

Each entry below gives the symptom, the likely cause and the fix. Start with the section that matches your problem.

The radar entries are written for LD2412 + LD2450, the configuration of the current firmware. Advice for the LD2460 and the LD6002B follows with their firmware.

Setup and Network

Device Not Found in Home Assistant

Cause: The device is not on your network yet, it is on a different network or VLAN, or discovery is blocked.

Fix:

1. Check the power. The LED ring shows a rainbow during start-up, so a ring that stays dark points to a power problem.
2. Look for the device in your router's list of connected devices.
3. Make sure the device and Home Assistant are on the same network or VLAN, with mDNS and port 6053 allowed.
4. Add it by hand: go to Settings > Devices & services > Add integration, choose ESPHome and enter the IP address.

WiFi Setup Network Does Not Appear

Cause: The device has not finished starting, or it is already connected to your WiFi.

Fix:

1. Wait 1 to 2 minutes after power-on. The rainbow can already be gone by then. That is normal.
2. Check your router. If the device is there, it is already connected and needs no setup.
3. Disconnect the power, wait a few seconds and connect it again.
4. With USB-C, use a supply of 5 V and at least 1 A.

Captive Portal Does Not Open

Cause: Your phone or laptop stays on its other connection, or does not show the portal.

Fix:

1. Turn off mobile data on your phone.
2. Stay connected to CeilSense Mini Setup if your phone warns about no internet.
3. Try a different phone or a laptop.

Device Is Offline

Cause: The power or network dropped, the WiFi signal at the ceiling is weak, or your network changed.

Fix:

1. Check the power.
2. Check whether the device appears in your router.
3. Check the WiFi signal at the mounting spot.
4. Did your WiFi name or password change? See Network Configuration.
5. Disconnect the power and connect it again.

Ethernet or PoE Does Not Work

Cause: The current firmware is WiFi only. Ethernet and PoE firmware is planned for release.

Fix:

1. For now, use WiFi and power the sensor from USB-C. See Firmware.
2. Once that firmware is available, check that your switch or injector supports IEEE 802.3af and that PoE is on for this port.
3. Check the cable and try another switch port.
4. Check that DHCP is enabled and that the device is on the same network or VLAN as Home Assistant.

Presence

Presence Shows unknown

Cause: Presence stays unknown until both radars have reported. Right after a start that is normal. If it stays that way, a radar is not seen.

Fix:

1. Wait a moment after a start.
2. Check LD2412 Firmware Version and LD2450 Firmware Version. Empty means the module is not seen.
3. Follow the steps under Radar Entities Are Empty below.

Presence Stays On in an Empty Room

Cause: The radar sees something: a moving object, a reflection, activity behind a thin wall, or a background it has not learned yet. An LD2412 can also stay on with a high still energy.

Fix:

1. Check which radar keeps Presence on: LD2412 Presence or LD2450 Presence.
2. If LD2412 Still Energy stays high in an empty room, press LD2412 Restart.
3. Remove or stop moving objects such as pets, fans and curtains, and check for reflections.
4. Run the dynamic background correction with the room empty.
5. Lower LD2412 Maximum Distance Gate to the size of the room and check LD2412 Presence Timeout.

No Presence, or Someone Is Missed

Cause: The radar module is not fitted firmly, the person is outside the coverage, or the settings are too narrow.

Fix:

1. Check that the firmware entity of the radar has a value: see the next entry.
2. Disconnect all power and check that the module sits firmly in its socket. A loose module can miss someone.
3. Check the coverage for your ceiling height. Sitting still has a smaller reach than moving.
4. Raise LD2412 Maximum Distance Gate and check LD2412 Minimum Distance Gate.
5. Check that your zones are not too small.

Radar Entities Are Empty

Cause: The module is not seen, or the firmware does not match the radar in the device.

Fix:

1. Check LD2412 Firmware Version and LD2450 Firmware Version. Empty means the module is not seen.
2. Disconnect all power and reseat the module. See Radar and Sensor Modules.
3. Check that the firmware matches the radar configuration. See Firmware.
4. Never combine modules that cannot be combined. See Radar and Sensor Modules.

Detection Through a Wall or From the Next Room

Cause: mmWave can pass through thin walls and doors.

Fix:

• With LD2412: lower LD2412 Maximum Distance Gate.
• With LD2450: use zones with LD2450 Zone Type.

Pets or Fans Trigger Presence

Cause: mmWave can notice small moving objects such as pets, fans and moving curtains.

Fix:

• Aim for the area where people are, with zones if your radar has them.
• Lower the maximum range to the part of the room you need.
• With a ceiling fan that stays on, run the dynamic background correction with the fan at its usual speed.

Zones Do Not Match the Room

Cause: The zone coordinates do not match where the radar places people.

Fix:

1. Walk through the room and watch the X and Y entities.
2. Set the zone around the coordinates you see, not around what you measured with a tape.

Readings

Light Value Differs From a Lux Meter

Cause: The firmware applies no correction for the housing, and the light of the LED ring can play a part.

Fix: Turn the LED ring off, and pick automation thresholds from what Illuminance shows in your room. See Calibration.

There Are No Climate Entities

Cause: This is normal. The Mini measures presence and light. It has no climate sensors and no air pressure sensor.

Fix: Nothing. For CO2, temperature and humidity, see CeilSense V2 and CeilSense Pro.

CPU Temperature Is Much Higher Than the Room

Cause: This is normal. It is the temperature of the processor, not room temperature.

Fix: Nothing. The Mini does not measure room temperature.

LED Ring and Buzzer

LED Ring Shows a Rainbow at Every Start

Cause: This is normal. The ring shows a rainbow during start-up and fades out at most about 20 seconds after power-on.

Fix: Nothing. The current firmware has no setting to switch it off. If the rainbow runs for about the full 20 seconds, WiFi or the light sensor was not ready in time. See Network Configuration.

LED Ring Stays Dark When You Connect the Power

Cause: The device gets no power, or the supply is too weak.

Fix:

1. Check the cable and the connection on the ceiling side.
2. With USB-C, use a supply of 5 V and at least 1 A.
3. Try another cable.

LED Ring Stays Dark After Start-Up

Cause: After the rainbow, the ring is off until you use it.

Fix:

1. Switch on LED Ring on the device page.
2. Check the brightness.
3. Check whether an automation turns the ring off.

LED Ring Does Not Show a Warning

Cause: The current firmware has no built-in motion light or warning.

Fix: Build it with an automation. See LED Ring and Buzzer.

An LED Effect Is Missing

Cause: The current Mini firmware has one effect: Rainbow. The other effects from the V2 firmware are not in it.

Fix: Use a color and brightness in your automation instead. See LED Ring and Buzzer.

Buzzer Stays Silent

Cause: The buzzer is silent unless you use it.

Fix:

1. Press Buzzer Test under Diagnostic on the device page.
2. Check that your automation uses button.press on the right entity. See Usage.

Entities and Firmware

An Entity Is Missing

Cause: The entity depends on your radar configuration and firmware, or it is disabled by default.

Fix:

1. Compare with Sensor Definitions.
2. Check that the firmware matches your radar configuration.
3. Look under Diagnostic and Configuration on the device page, and check hidden or disabled entities.

Your Automation Stopped After a Firmware Change

Cause: Entity names can change until release, and different radar configurations have different entities.

Fix: Check the entity IDs in your automation against the device page.

Still Stuck?

• FAQ
• Support portal
• Discord
• Contact

See Warranty and Support for what to include in your request.