SmartHomeShop Docs

Troubleshooting

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

Planned behavior. The firmware for CeilSense Pro is not written yet. The entity names and fixes on this page follow the planned firmware and can still change at release.

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 is off by default, so a dark ring tells you nothing.
  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, it is already connected to your WiFi, or it runs Ethernet firmware.

Fix:

  1. Wait 1 to 2 minutes after power-on.
  2. Check your router. If the device is there, it is already connected and needs no setup.
  3. Only WiFi firmware has a setup network. Ethernet firmware connects through the cable.
  4. Disconnect the power, wait a few seconds and connect it again.
  5. 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 the setup network 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 and, with Ethernet, the cable and the switch port.
  2. Check whether the device appears in your router.
  3. With WiFi, check the signal at the mounting spot. If it stays weak, consider Ethernet.
  4. Did your WiFi name or password change? See Network Configuration.
  5. Disconnect the power and connect it again. If the sensor is on mains, switch the circuit off and on.

Ethernet Does Not Connect

Cause: The device runs WiFi firmware, the cable or plug is not seated well, or the network gives no IP address.

Fix:

  1. Ethernet needs Ethernet firmware. See Firmware.
  2. Check the cable and try another switch port.
  3. Check that DHCP is enabled and that the device is on the same network or VLAN as Home Assistant.
  4. Look up the IP address in your router and add the device by hand.

PoE Does Not Power the Sensor

Cause: The switch or injector does not support IEEE 802.3af, PoE is off on that port, or the cable is at fault.

Fix:

  1. Check that your switch or injector supports IEEE 802.3af and that PoE is on for this port.
  2. Try another cable and another port.
  3. To rule out the sensor, test it with USB-C.

Presence

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 with LD2412 + LD2450:

  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.

Fix with LD2460:

  1. Look at Tracking Targets to see where the radar places the target.
  2. Check for mirrors, metal furniture and windows at that spot.
  3. Limit the detection range or draw an exclusion zone. See Calibration.

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, LD2450 Firmware Version or Tracking Radar Firmware. Empty means the module is not seen.
  2. Disconnect all power and reseat the module.
  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.
  • With LD2460: lower Tracking Radar Detection Distance or draw an exclusion zone.

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.
  3. With an LD2460, do the walk test before you draw zones.

Readings

First Readings After a Start Look Wrong

Cause: This is normal. The first SCD41 readings after a start are not meaningful, and VOC and NOx need runtime.

Fix: Wait until the sensors have stabilized. Give the SCD41 at least 30 minutes before you judge temperature, and the SGP41 several hours.

CO2 Looks Too High or Too Low

Cause: Automatic self-calibration is planned to be off, so the reading does not correct itself over time. Or the room really has too little ventilation.

Fix:

  1. Ventilate the room well and see whether the value drops. Fresh outdoor air is about 400 to 430 ppm.
  2. If the reading stays clearly off in fresh air, press SCD41 Calibrate Fresh Air. See Calibration.

Temperature Reads Too High

Cause: Recessed mounting and heat from electronics influence the reading. A bright LED ring adds some heat too.

Fix:

  1. Dim the LED ring or use it briefly.
  2. Recessed? Keep the cavity free of drafts.
  3. Compare with a reliable thermometer and adjust SCD41 Extra Temperature Offset. See Calibration.
  4. Use temperature mainly for trends.

Humidity Looks Wrong

Cause: The reading differs from your reference, or the sensor is still stabilizing.

Fix: Wait until the sensor has stabilized, compare with a reliable reference and adjust SCD41 Humidity Offset.

VOC or NOx Seems Unstable

Cause: These values are relative indices, not ppm, and they need runtime after a start or a move.

Fix: Allow several hours of normal operation and judge trends, not single readings. See Calibration.

BMP388 Temperature Is Much Higher Than the Room

Cause: This is normal. It is the temperature inside the device, not room temperature.

Fix: Nothing. For room temperature, use the sensors in Radar and Sensor Modules.

Light Value Differs From a Lux Meter

Cause: The sensor measures the light that reaches the ceiling, not the light where you hold the meter.

Fix: Pick automation thresholds from what Illuminance shows in your room. See Calibration.

LED Ring and Buzzer

LED Ring Stays Dark

Cause: The ring is off by default.

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: There is no built-in motion light or CO2 warning.

Fix: Build it with an automation. 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.

Speaker and Voice

No Sound From the Speaker

Cause: The volume is low, the media player gets no audio, or your automation points at the wrong entity.

Fix:

  1. Check Speaker on the device page and its volume.
  2. Test with a short spoken message before you try longer audio.
  3. Check the entity IDs in your automation. See Speaker and Voice.

Assist Does Not Respond Correctly

Cause: The language or the voice services of your assistant are not set up correctly.

Fix:

  1. Check the language of the assistant in Home Assistant.
  2. Confirm that your speech-to-text and text-to-speech services are running.
  3. Try a shorter command.

Optical Smoke Sensing

These entries are about the experimental measurement, not about your safety. If a certified smoke alarm sounds, or you see or smell smoke, act on that first. See Optical Smoke Sensing.

ADPD188BI Baseline Ready Stays Off

Cause: The warm-up is not finished. It takes at least three minutes after every start and starts over when the readings drift.

Fix:

  1. Wait a few minutes and check ADPD188BI Measurement Stable.
  2. Check ADPD188BI Sensor Problem.
  3. If the warm-up never finishes, contact support.

ADPD188BI Sensor Problem Is On

Cause: The sensor failed to start or its readings failed.

Fix:

  1. Treat every reading from this measurement as unreliable.
  2. Press Smoke Test and check Smoke Self Test Result.
  3. Press Restart Device. The warm-up then starts again.
  4. If the problem stays, contact support.

ADPD188BI Smoke Alert Turns On Without Visible Smoke

Cause: The readings may trigger falsely. A rise above the baseline does not prove smoke.

Fix:

  1. Check the room first and go by your certified smoke alarms.
  2. If the siren is on, press Smoke Alarm Silence to mute it for 10 minutes.
  3. Look at ADPD188BI Smoke Index over time to see what happened.

The Siren Stays Silent

Cause: The siren is off by default.

Fix: The siren only sounds when Smoke Siren Enabled is on. Turning it on is your choice. See Optical Smoke Sensing.

Smoke Self Test Result Shows FAIL

Cause: The sensor did not answer as expected during Smoke Test.

Fix:

  1. Press Restart Device, wait for the warm-up and run Smoke Test again.
  2. Check ADPD188BI Sensor Problem.
  3. If it keeps failing, contact support.

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 for your radar configuration.
  2. Check that the firmware matches your network choice and 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?

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