I’ve purchased a sizeable batch of BTS MP1 / EYE Sensors and want to protect that investment: when units aren’t deployed, I need to hibernate them so the batteries aren’t drained sitting on the shelf, keeping the sensors usable for years. This isn’t a hobby experiment — it’s about not wasting hardware I’ve paid for.
Doing it one unit at a time in the EYE app doesn’t scale, so I’m writing my own BLE central (Python/bleak on a Raspberry Pi) to hibernate them in batches. Wake-by-magnet already works. Using the published GATT table I can connect, authenticate with the PIN (e61c0008), and read/write config characteristics fine.
The one thing I can’t find documented is the exact write the EYE app issues when you tap “Send device to sleep.” Could you confirm which of these it is:
- A write to the
e61c0018“Manufacturer sleep (Hibernate mode)” characteristic — if so, what value, and is anything else required (e.g. a flash-commit0x0010or a reset afterward)? - Or an opcode to the command register
e61c0007that isn’t in the published list (flash/boot/reset/get-voltage/keep-alive/restore-defaults) — if so, what opcode and byte order? - Any firmware floor (I see ≥ 1.2.9.R.8 for hibernate support) and does the write have to be PIN-authenticated first?
A characteristic UUID plus the exact bytes (and any required commit/reset sequence) is all I need to get this working. Thanks very much.
-T