Determine whether Ecosense RadonEye or EcoQube devices expose any cloud/developer API before building an integration
domain: ecosense.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check Ecosense's own RD200 FAQ, which states plainly that 'RadonEye has no cloud or server services and does not have access to customer location information' — there is no public cloud REST API for RadonEye.
Confirm RadonEye data is retrieved only via the RadonEye mobile app pairing directly to the device over Bluetooth LE; exported readings save as local .txt files on the phone, not a vendor cloud.
For the Wi-Fi EcoQube line, note the only documented third-party integration path is IFTTT, not a published developer/REST API.
If you need EcoQube automation, build IFTTT applets (e.g. radon-level-based webhook triggers) rather than expecting JSON endpoints.
If you need RadonEye automation instead, use the community-reverse-engineered BLE protocol (separate route) since Ecosense publishes none.
Known gotchas
RadonEye (BLE-only) and EcoQube (Wi-Fi + IFTTT-only) are different products with different, non-overlapping integration surfaces — don't assume 'Ecosense API' means the same thing for both.
No official SDK, credentials, or terms of service exist for third-party cloud access to either device; treat any claimed 'Ecosense API key' as unverified.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?