Troubleshooting
This guide covers common issues with the CeilSense and how to resolve them.
mmWave Radar Issues
Constant Detection / 100% Movement Energy When Room is Empty
This usually means the sensor needs to be calibrated for your specific room.
Symptoms:
- Presence always shows "detected" even with nobody in the room
- Movement energy shows 100% constantly
- Still energy shows high values continuously
- Lights never turn off because presence is always detected
Causes:
- Sensor not calibrated after installation
- Radar detecting through walls into adjacent rooms
- Ceiling fans or moving objects in detection zone
- HVAC airflow moving curtains or plants
- Pets in the detection area
- Background noise not filtered out
Solution:
Run Dynamic Background Correction (most important!)
- Completely empty the room — no people, no pets
- Turn off ceiling fans, close windows
- In Home Assistant, press "Start Dynamic Background Correction"
- Wait for the process to complete
Reduce Maximum Distance Gate
- Lower the max gate to match your room size
- Each gate ≈ 0.75m, so for a 3m room, set max gate to 4-5
Increase thresholds for problem gates
- Enable Engineering Mode to see energy per gate
- Increase Move/Still thresholds for gates showing constant high energy
👉 See the Calibration Guide for detailed step-by-step instructions.
No Detection / Presence Never Triggers
Symptoms:
- Sensor never detects presence
- Movement energy always shows 0%
- Lights don't turn on when entering the room
Causes:
- Thresholds set too high
- Maximum distance gate set too low
- Sensor mounted too high or at wrong angle
- Physical obstruction blocking the sensor
Solution:
Lower the thresholds
- Decrease Move Threshold and Still Threshold values
- Lower values = more sensitive
Increase Maximum Distance Gate
- Ensure max gate covers your room size
Check mounting
- Recommended height: 2-4 meters
- Ensure sensor lens is not obstructed
Factory Reset and recalibrate
- Press Factory Reset button
- Run Dynamic Background Correction with empty room
Detecting Through Walls (Adjacent Room Triggers)
Symptoms:
- Sensor detects presence when someone is in the next room
- False triggers from hallway or adjacent spaces
Solution:
- Reduce Maximum Distance Gate to limit detection range
- Increase thresholds for far gates (gate 8-13) to reduce sensitivity at distance
- Consider sensor placement — move away from thin walls if possible
Ceiling Fan Causes Constant Detection
Symptoms:
- Detection works fine until ceiling fan is turned on
- Constant movement detection when fan is running
Solution:
- Run Dynamic Background Correction with fan ON at your typical speed
- Increase Move Threshold for gates where the fan is detected
- Reduce detection range if fan is at the edge of detection zone
Wi-Fi / Connectivity Issues
For detailed network setup and troubleshooting, see the Network Configuration guide.
Not Discovered in Home Assistant
Solution:
- Check that CeilSense is connected to your Wi-Fi network
- Try adding the ESPHome integration manually by IP address
- Ensure Home Assistant and CeilSense are on the same network/VLAN
Cannot Connect to CeilSense Hotspot
Solution:
- Look for SSID:
CeilSense(password:ceilsense) - If no hotspot appears, the device may already be connected to Wi-Fi
- Try power cycling the device (unplug and replug)
- If captive portal doesn't open, browse manually to
http://192.168.4.1/
Frequent Disconnections
Solution:
- Check Wi-Fi signal strength at ceiling level
- Consider using Ethernet/PoE for more reliable connection
- See Network Configuration for how to switch
Ethernet Issues
For Ethernet-specific issues (device offline after switching, not discovered, etc.), see the Network Configuration Troubleshooting section.
Environmental Sensor Issues (Complete Only)
Temperature Readings Too High
Causes:
- LED ring generating heat
- Poor airflow in ceiling cavity
- Well-insulated ceiling trapping heat
Solution:
- Reduce LED brightness or usage
- Apply a temperature offset in ESPHome YAML
- See Calibration Guide for details
CO₂ Readings Inaccurate
Causes:
- Sensor not yet calibrated (ABC needs time)
- Room never gets fresh air
Solution:
- Wait 1-2 weeks for Automatic Baseline Calibration (ABC) to stabilize
- Ensure room gets fresh air regularly (open windows occasionally)
- Run manual CO₂ calibration in fresh outdoor air
- See Calibration Guide for details
CO₂ Never Drops Below 600 ppm
Cause:
- ABC algorithm hasn't seen fresh air baseline
Solution:
- Ventilate the room thoroughly (open windows for 20+ minutes)
- Run manual calibration if ABC doesn't correct after a few days
LED Ring Issues
LEDs Not Working
Solution:
- Check power supply (LEDs require adequate power)
- Verify LED entity is enabled in Home Assistant
- Check brightness setting is not at 0%
LEDs Affecting Sensor Readings
Cause:
- LED ring generates heat that affects temperature/humidity/CO₂ sensors
Solution:
- Reduce LED brightness during continuous operation
- Use cooldown periods between LED effects
- Apply calibration offsets to compensate
Firmware Issues
Cannot Flash Firmware
Solution:
- Use a USB-C data cable (not charge-only)
- Try a different USB port
- Close other applications that might use the serial port
- Use Chrome or Edge browser for web flasher
Device Not Responding After Flash
Solution:
- Wait 30 seconds for device to boot
- Power cycle the device
- Device may need to be re-adopted in Home Assistant
Still Having Issues?
If you've tried the solutions above and still have problems:
- Check the FAQ for additional answers
- Visit the Calibration Guide for detailed tuning instructions
- Join our Discord community for support
- Contact us via our contact page