The thing is though, the right side sensor is no longer registering a person being on it either. The pressure value changes if I press on the sensor but it doesn’t seem to change the presence state.
It appears that your occupied and unoccupied values for the right side are both set at 0.0. That’s definitely going to cause issues when trying to calculate a trigger threshold. Try hitting the Calibrate Right Occupied with it registering pressure on the right side and verify that Right Occupied Pressure value updates.
That’s what happened after trying to redo the calibrations whilst lying on the bed. I’ll try again tonight by pressing the sensor by hand.
A quick update on this. It turns out the sensor strip had lifted partly at one point along the bed slat. I ran my finger along it to press the adhesive back down and it seems good again. Not sure how long the adhesive will keep it happy though.
Dave, you could apply some painters tape lightly in rings around the slat at each end of the sensor strip. With my previous DIY version I did this and didn’t even use the adhesive backing. Lasted years until I replaced it with the Elevated sensor.
(to aid in perspective the carpet is light grey about 30cm below).
1 Like
Thanks for the explanation. Was wondering why you mentioned you used painters tape, when your picture clearly shows you used duct tape!
2 Likes
Yeah that image messes with my eyes. It’s like one of those pictures of of the moon where all the craters look like hills because your room lighting is coming from the opposite direction to the picture lighting.
3 Likes
Got my king platform version installed today. Really love it. Seems to register changes almost instantly. I had relied on the cloud based bed occupancy sensors from two withings sleep mats until now, and there was always a problem, and even when it worked it was slow. (The sleep mats are great for sleep stats, just not much else, which to be fair, they don’t claim to be). The light under the bed finally goes on and off reliably with bed occupancy. No more slow responses, no more false triggers from a floor mounted motion detector, no more phantom bed occupancy. Really pleased. Great product. Thanks!
1 Like
I have the same bed. Did you buy the bed sensor? Does it work well?
I need to buy a USB charger for this device. What are the exact voltage and ampere requirements? I assume it needs 5V, but will 1A be sufficient or is 2A recommended?
I’ve checked the device itself, the documentation, and this thread, but couldn’t find any specs. Normally, electronic devices have an INPUT label showing required volts, amps, and watts.
I know I can just plug in any USB C charger and the thing will work, but I want to do it right since it’s goint to run 24/7 under the spot where two people sleep every night.
Thanks in advance for any help. Also, big thanks for making and selling this sensor 
1A should be sufficient. Just make sure it is a good quality 5V supply with low noise/ripple and low chance of setting your house on fire.
2 Likes
Yeap! It works super fine.
1 Like
The details are listed under “Tech Specs” on the product page. The unit draws less than 100mA @ 5V. Pretty much any USB power supply will provide that, but make sure it is an ETL/UL listed unit for fire safety.
I bought a long USB cable so that the USB power block was not under our mattress.
Oh, there it is, on the product page, not the docs. Right where it belongs. Sorry I missed that! Thank you Stephen.
I’m planning to do the same.
1 Like
We’re not suggesting you should place a power supply under your mattress. An ETL/UL listed power supply helps ensure fire safety and delivers consistent, reliable power to the Bed Presence unit. Be sure to use a long enough USB cable so the power supply is not in contact with the mattress and has plenty of ventilation.
2 Likes
That makes sense. I had a really short USB cord. Have the power supply and a high power cable under the mattress made me uncomfortable. So I got a long USB cable. Works great.
I am trying to update my 3 ESP Elevated Sensor devices to 2025.8.2 and the deployment keeps failing. All my other ESP devices update with no worries. Any ideas? Here is what is in the logs
INFO ESPHome 2025.8.2
INFO Reading configuration /root/config/bed-presence-330bc0.yaml...
INFO Updating https://github.com/ElevatedSensors/sensor-configs@main
WARNING GPIO9 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
INFO Generating C++ source...
INFO Compiling app...
Processing bed-presence-330bc0 (board: esp32-c3-devkitm-1; framework: espidf; platform: https://github.com/pioarduino/platform-espressif32/releases/download/54.03.21-2/platform-espressif32.zip)
--------------------------------------------------------------------------------
INFO Package configuration completed successfully
INFO Package configuration completed successfully
HARDWARE: ESP32C3 160MHz, 320KB RAM, 4MB Flash
- framework-espidf @ 3.50402.0 (5.4.2)
- tool-cmake @ 3.30.2
- tool-esp-rom-elfs @ 2024.10.11
- tool-esptoolpy @ 5.0.2
- tool-mklittlefs @ 3.2.0
- tool-ninja @ 1.13.1
- tool-scons @ 4.40801.0 (4.8.1)
- toolchain-esp32ulp @ 2.35.0-20220830
- toolchain-riscv32-esp @ 14.2.0+20241119
Reading CMake configuration...
-- git rev-parse returned 'fatal: not a git repository (or any of the parent directories): .git'
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- The ASM compiler identification is GNU
-- Found assembler: /root/.platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: /root/.platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc
-- Check for working C compiler: /root/.platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc - broken
-- Configuring incomplete, errors occurred!
fatal: not a git repository (or any of the parent directories): .git
CMake Error at /root/.platformio/packages/tool-cmake/share/cmake-3.30/Modules/CMakeTestCCompiler.cmake:67 (message):
The C compiler
"/root/.platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: '/root/config/.esphome/build/bed-presence-330bc0/.pioenvs/bed-presence-330bc0/CMakeFiles/CMakeScratch/TryCompile-n0PwqB'
Run Build Command(s): /root/.platformio/packages/tool-ninja/ninja -v cmTC_e6ebd
[1/2] /root/.platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc -march=rv32imc_zicsr_zifencei -o CMakeFiles/cmTC_e6ebd.dir/testCCompiler.c.obj -c /root/config/.esphome/build/bed-presence-330bc0/.pioenvs/bed-presence-330bc0/CMakeFiles/CMakeScratch/TryCompile-n0PwqB/testCCompiler.c
FAILED: [code=1] CMakeFiles/cmTC_e6ebd.dir/testCCompiler.c.obj
/root/.platformio/packages/toolchain-riscv32-esp/bin/riscv32-esp-elf-gcc -march=rv32imc_zicsr_zifencei -o CMakeFiles/cmTC_e6ebd.dir/testCCompiler.c.obj -c /root/config/.esphome/build/bed-presence-330bc0/.pioenvs/bed-presence-330bc0/CMakeFiles/CMakeScratch/TryCompile-n0PwqB/testCCompiler.c
riscv32-esp-elf-gcc: fatal error: cannot execute 'cc1': posix_spawnp: No such file or directory
compilation terminated.
ninja: build stopped: subcommand failed.
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
/root/.platformio/packages/framework-espidf/tools/cmake/project.cmake:571 (__project)
CMakeLists.txt:3 (project)
========================== [FAILED] Took 1.48 seconds ==========================
Can you share your YAML?
esphome:
name: bed-presence-330bc0
friendly_name: Bed Presence
min_version: 2024.6.0
name_add_mac_suffix: false
project:
name: ElevatedSensors.BedPresenceMk1
version: DIY
platformio_options:
board_build.flash_mode: dio
esp32:
board: esp32-c3-devkitm-1
framework:
type: esp-idf
# Enable logging
logger:
# Enable Home Assistant API
api:
# Enable wifi
wifi:
# Set up a wifi access point
ap: {}
# In combination with the `ap` this allows the user
# to provision wifi credentials to the device via WiFi AP.
captive_portal:
# Enable esphome OTA updates
ota:
- platform: esphome
################################################################################
packages:
remote_package:
url: https://github.com/ElevatedSensors/sensor-configs
ref: main
files: [bed-presence-mk1/base.yaml]
refresh: 1s
# See https://github.com/ElevatedSensors/sensor-configs/blob/c658008df9abbc817ca02c359f20c04f3a8bf0e4/bed-presence-mk1/sensor.yaml for a detailed
# description of available substitutions.
#
# substitutions:
# trigger_percentile: '0.75'
# averaging_window_samples: '5'
# fast_delayed_on: '0ms'
# fast_delayed_off: '0ms'
# standard_delayed_on: '0s'
# standard_delayed_off: '1s'
# reporting_delta: '1.0'
# reporting_interval_max: '180s'
# calibrate_100: '408000'
# calibrate_0: '276000'