Thanks for the details. I was just able to compile a functionally equivalent YAML under 2025.8.2. Let’s try a clean build.
Let me know if that still doesn’t work.
“3. Orient the sensor with the circuit board/text facing up”
Why mention ‘up’ specifically? I had to mount the sensor vertically because of my bed, and I wasn’t sure if it would work like that. But it seems to be fine. The sensor’s working great with the default calibration. Thank you so much for making such an easy plug-and-play solution 
After a Clean Build Files the wireless install still fails. Attempting to visit the ESP device from ESPHome results in a timeout. The device log and indeed inside Home Assistant continue to function as normal
I installed the system on a split cal king Tempur-Pedic Ergo base (motorized). The nice thing is that power can be drawn from the built in USB hub on one of the two bases. I ran the USB cable up between the bases in the middle. I put the strip across the portion of the base that does not move (as suggested) about half way down the bed. The other nice thing is that if you have the head portion even slightly elevated, the mattress will actually lift off the sensor when that person gets up and quickly go to zero. I do see pressure build over the day as the memory foam mattress densifies, but since both sides read about 95% when occupied, detected and clear seem to work well. I will update after a few days.
Just wanted to report back that the Bluetooth proxy has worked like a charm. It has allowed me to decommission a (formerly) required proxy in the bedroom that helped connect the more distant BLE devices I have.
Tremendous upgrade and allowed me to repurpose one of my m5atoms.
That has to do with explaining the default installation option (basically explaining that it hangs over the edge), but I understand how that might make you question if it works in other orientations. For clarity, the orientation of the sensor doesn’t affect the electronics in any way.
Mine arrived today and I’ve just fitted it.
Got the two-sensor with extensions kit. My bed is a European-double IKEA thing with the individually-sprung slatted base.
The slats close together and are separate units for the left and right sides, so the normal install on top of the slats in the centre wasn’t possible.
But no problem — I mounted it on the underside and ran the extensions to the top so that the sensors were mounted correctly.
Note that the extensions are simply 2-pin male-to-female DuPont connectors, so are easily made if you’re an electronics hobbyist!
I fitted the sensors with a few bits of kapton tape since I expect to be getting a new bed soonish.
I positioned them roughly a third of the way from the top of the bed, at about chest-height. At least with my mattress, this means it detects laying down, but sitting on the edge of the bed roughly in the middle doesn’t trigger. That’s ideal for me.
After a quick calibration according to the documentation, it’s working superbly.
For testing, I set up an HA automation to make Alexa in the bedroom say ‘left, right, both, clear’ in response to the sensor states.
Then I rolled around on the bed for a while like a lunatic, listening to what Alexa reported. I sleep alone, so checked that at least one side still reported occupancy no matter what angle I was laying at.
It behaved perfectly!
Now, to set up some automations!
@TomberWolf have you already bulk ordered to germany?
I am from austria and very interested in this piece of HW.
Currently running DIY FSR sensor which works good but sometimes has false positives because of wrong calibration (and you all know how time intensive calibration is with the DIY version).
@stephenp93 and customers from europe, what’s the best delivery option to choose to not have to fiddle arround with VAT/customs on arrival? (Ex.: from china i always use 4PX and pay VAT before hand)
That’s the delivery options:
What means “International Economy” Is this the usa local post?
Definitely interested in this, any feedback from anyone with a superking bed? I think that’s 180cm wide rather than 150cm for a king size. Would the king size kit work or would I need two single (or a double and a single) sets?
The sensor doesn’t need to span the entirety of the bed. As long as you get it in the middle of each persons space it will work fine.
Currently all of our international shipping options are DDU, meaning VAT/customs/etc are due upon arrival.
The International Economy option uses Asendia. They handle last-mile delivery and customs clearance via your country’s postal service.
Thx for the info.
Ordered one with International shipping and hope the local fees are not too high.
i got it also earlier this year with internal shipping to germany, i payed around 15ER für tax, import and service fee. Tax was 9,70€. Perhaps this is now slightly more, dont know. But DHL handles it 
Ronny
thx a lot.
Then it should be similar in austria here.
Cant wait to install the new sensor because one of my FSR of my DIY sensor is broken. Also knowing i have not to deal with HW calibration makes me happy
anyone have any thoughts on mounting this with a metal foundation bed like this.
i don’t think double sticky tape will hold it, so i may have to zip tie it under the slat and then bring the extension wires up to the sensor strip.
Figured i would ask here first
Use the adhesive backing and back it up with: Bed Presence for ESPHome by Elevated Sensors - #248 by tom_l
Just a information from my side of importing the sensor to austria.
I used shipping method “Int. Shipping”, which was handeld by Acendia and in my country with local post.at.
The shipping duration took 23 days (ordered on 07.10 and arrived on 30.10).
Subtotal $69.99 (~ 60,34 Euro)
Shipping $14.97 (~ 12,91 Euro)
Tax ~$20,88 (~ 18 Euro - payed on delivery)
Total ~$105,84 (~ 91,24 Euro)
= = = = = = = = = = = = = = = = = = = = = = = = = =
Before i had an DIY version and had to deal with calibration (resistor) and also sometimes adjust the trigger threshold voltage. Also the threshold was very low (0,65V), so maybe not correctly calibrated with the resistor.
It worked, okay for two years now.
My first impressions on the elevated sensors bed sensor (from an HW engineer with 20 years in this job):
NICE JOB !!
I have cloned the yaml and done my esphome device/seup myself because i have a device base yaml (with diagnostic sensors), so there where duplicates.
Would be nice if we can exclude the diagnostic.yaml with some flag/substution?
For me i have setup the delays longer, like:
standard_delayed_on: ‘1s’
standard_delayed_off: ‘60s’
because i dont need it to react fast when i go out of bed.
With default values i had ~1 second unoccupied a few times during night (while still lying in bed).
With the above values i had a night wihout (unoccupied) false positives.
With my DIY sensor i had off delay 180s & my HA automations added 10 minutes of occupied/unoccupied (blinds down, disable motion sensors…)
What i want to prevent is that the motion sensor switching on light in the night, that’s why i am choosing longer delays.
Will see how it goes.
thx for this nice project.
Is there any way to disable the Bluetooth proxy. I have this installed on a bed immediately above the sofa in my living room on the floor below. Devices tend to connect to the bed sensor rather than the proxy in the living room. I have another proxy elsewhere in the Bedroom already.
Is it just a case of adopting and setting bluetooth_proxy: false in the YAML?
Thanks!
If you adopt it, you can then just remove or hash out the proxy line like this:
packages:
remote_package:
url: https://github.com/ElevatedSensors/sensor-configs
ref: main
refresh: 1s
files:
- 'bed-presence-mk1/base.yaml'
# - 'esphome-common/bluetooth-proxy.yaml'
Thanks for the feedback, I’m glad you’re enjoying the product.
All components have an ID so that you can Extend or Remove them from your top level YAML while still using the remote packages. The IDs for each can be found in diagnostics.yaml.
For example, removing the uptime sensor would look something like this.
sensor:
- id: !remove uptime_sensor