Ecosense(Ecoqube) to MQTT

Just recently published a project, specifically just an addon to get radon readings from Ecoqube devices into Home assistant.

Project: GitHub - starsoccer/ecosense

Credit to original post that showed how to actually get data from the device, Reclaim Your Data: Freeing a Wi-Fi Sensor from the Cloud - Embedded Artistry

2 Likes

I just tried this addon with my new Ecoqube but I get an error in the Log

Setting ENV Variables
Env Set
Listing Versions!
Node Version: v22.13.0
NPM Version: 10.9.2
Starting Server
{"level":30,"time":1737249669563,"pid":21,"hostname":"22253e41-ecosense","message":"Server listening on 443"}
file:///src/mqtt.js:91
    await MQTT.publishAsync(`homeassistant/sensor/${serial_number}/radon/state`, radon_level.toString());
                                                                                             ^
TypeError: Cannot read properties of undefined (reading 'toString')
    at publish (file:///src/mqtt.js:91:94)
    at proxyRequest (file:///index.js:56:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
Node.js v22.13.0

Will reply on github on keep the discussion there

For anyone interested, I’ve created a HACS integration that pulls the data from the Ecosense cloud: GitHub - rwestergren/hass-ecosense-radon: Home Assistant cloud integration for EcoSense radon monitors

1 Like

Nice, thanks for posting this, great to have another option in case they somehow update the device and brick it working locally

I’ve tried installing, and everything went as expected, except it never ask for my credentials to authenticate with the EcoSense cloud. Is the solution still active and working? Should I remove and reinstall the integration? Any other suggestions or places I should look for clues?

Yes this should still be working. We dont need the credentials because we are proxying the request from the device. So we are just proxying the credentials and whatever information it sends to the actual api

Edit: Sorry I realized your asking about the other cloud integration which I am not familiar with.

Yes it is working for me

With inspiration from the project by starsoccer · GitHub I present a fully self hosted local-only version. (No third-party mobile app or backend required)

Project: GitHub - epicRE/ecosense-EcoQube: Self-hosted local-only EcoQube by Ecosense · GitHub

Cool, so just to confirm I understand the difference between this and my project, yours needs/has the same DNS rewrite and http server listening for updates, but yours has the ability to setup the device with BLE without ever requiring the app to be setup?

It would be great if you or someone figured out how to change the url its reporting to, or somehow get the data over BLE then we would be quite close to being able to get a native integration into Home Assistant. We might already be able to just using cloud polling, but it wouldnt be ideal.

@starsoccer: Your solution is great if someone want’s to maintain the online service/monitor via EcoQube mobile application. Since it proxies the requests from the device to the backend.

The solution I posted at epicRE doesn’t relay anything back to the manufacturer and their backend. Incoming PUT requests are converted to MQTT and pushed to HA (via docker solution).

BLE is only used to setup the device. Only by extracting and studying the device firmware would it be possible to see if any values can be extracted from the BLE channel.

Oh interesting, I wonder if there is a way we can merge work/projects somehow. Adding a switch/config to simply not relay the data to the API should be quite easy to implement. The BLE setup part I am not as sure about