Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Install a community library such as ceandre/radonreader, jdeath/rd200v2 (Home Assistant integration) or romkey/esp32-arduino-ble-radoneye-rd200 — the protocol is unofficial and reverse-engineered, not published by Ecosense/FT Lab.
Scan for BLE devices advertising the RadonEye GATT service and connect using service UUID 00001523-1212-efde-1523-785feabcd123.
Write byte 0x50 to write characteristic 00001524-1212-efde-1523-785feabcd123 to request the current reading, then read the value from the paired notify characteristic.
Pick the fork matching your exact hardware revision (RD200 v1 vs v2 vs v2b) since byte layouts differ between them.
Only run one BLE client at a time against the device — the official RadonEye app and a third-party library cannot hold a connection simultaneously.
Known gotchas
This protocol is explicitly undocumented/unguaranteed by the vendor; a firmware update can break any of these libraries without notice.
Confirm your RD200 hardware revision before choosing a library — a UUID/byte layout documented for one revision may not decode correctly on another.
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?