How to use Claude to retrieve thermometer history
Claude Code built RoomVibe to sync Xiaomi thermometer history over Bluetooth and preserve it offline; Prodan directed the architecture and published an APK.
linkedin.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Build an Android reader for our Xiaomi LYWSD03MMC history service using the documented community protocol. Synchronize stored records over BLE into local storage, preserve them after disconnection, and chart temperature and humidity offline. Document supported firmware and connection conflicts, and present an APK for our physical-device checks.
Reach people exploring AI agents
See placements →What happened
RoomVibe downloads compatible thermometers’ stored readings and retains them for offline browsing, with an installable Android release and source repository.
Reported by Valeriu Prodan — LinkedInHow the agent did it
- Prodan identified that the sensors retained history even though the official app did not cache it locally.
- Claude Code implemented Bluetooth decoding, synchronization and permanent local storage under the owner’s architectural direction.
- The agent built charts and release tooling, and the owner published the installable open-source application.
Where a person stepped in
Prodan set product and architecture direction based on his own wall-mounted sensors; the source does not document an independent measurement-accuracy evaluation.
Valeriu Prodan owned two Xiaomi thermometers whose official app made historical readings inaccessible when the phone disconnected. The sensors already retained months of readings internally. He directed Claude Code to build RoomVibe around that existing device capability.
Prodan describes his role as architect and product owner, with Claude performing implementation. The agent decoded Bluetooth history bytes and built an Android application that synchronizes stored readings while near a sensor, then preserves them in a local database for later offline browsing. The repository credits community work on the underlying Mijia history protocol, so this was not an entirely original protocol discovery.
Claude also implemented zoomable Jetpack Compose charts, temperature-unit controls, optional backup export and release tooling. The README describes scanning for a sensor and warns that the official app may need to be stopped so it releases the Bluetooth connection. Compatibility is limited to the stated sensor families and history service.
The published result is an installable open-source app, reported as built in two days. Its practical change is retaining device history after disconnection. Prodan supplied the requirement and architectural direction; the account does not establish independent temperature-accuracy validation.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: LinkedIn · Valeriu Prodan
Frequently asked questions
Must the phone stay connected to view saved readings?
No. Previously synchronized history is stored locally.
Was the protocol invented entirely from scratch?
No. The repository credits community Mijia protocol reverse-engineering.
Why stop the official app first?
It may retain the sensor’s Bluetooth connection.
More details
About this account
Prodan identified that the sensors retained history even though the official app did not cache it locally. Claude Code implemented Bluetooth decoding, synchronization and permanent local storage under the owner’s architectural direction.
Original post and RoomVibe README opened; exact publication date read from primary JSON-LD. Two-day development and execution attribution are owner reports. Protocol credits and device compatibility qualify the reverse-engineering claim. Suggested prompt written by Agents In Use; no original task prompt was found in the verified text.
Credit: Valeriu Prodan — LinkedIn
Source published 6 Jul 2026
Source checked 14 Oct 2026
Tools and topics
Claude Code · Xiaomi LYWSD03MMC · Bluetooth LE · Jetpack Compose · Android
device protocol · offline history · Bluetooth
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.