Question: .o5keypair key acquisition & server/API role
Hi,
I'm building an open-source DIY closed-loop app (Flutter/Android) that communicates with the OmniPod 5 via direct BLE — using OmnipodKit as a protocol reference.
Two questions:
- How are the
.o5keypair keys obtained? Are they extracted from the official app, derived from the pairing handshake, or acquired some other way?
- What role does the server/API https://api.osaid-keymanager.org play? Is it only involved in initial pod activation, or is it required for ongoing BLE communication as well? How does /api/o5/keypair provide the keypair?
Thanks for any insight!
Question: .o5keypair key acquisition & server/API role
Hi,
I'm building an open-source DIY closed-loop app (Flutter/Android) that communicates with the OmniPod 5 via direct BLE — using OmnipodKit as a protocol reference.
Two questions:
.o5keypairkeys obtained? Are they extracted from the official app, derived from the pairing handshake, or acquired some other way?Thanks for any insight!