What would you like to share?

Please choose the correct board before posting so we can review and respond faster:

  • Bugs → something is broken, incorrect, or not working as expected

  • Questions → you need help, clarification, or want to know how something works

  • Feature Requests → ideas for new features or improvements

Recording Status Indicator (LED + Haptic Feedback)

When I'm using double-tap to start/stop recordings, I have zero way to know if Omi is actually recording without digging out my phone. If it's in my pocket and I'm in the middle of an important conversation, that means unlock phone → open Omi app → pray Bluetooth is connected → check status. That's a lot of friction for something that should be instant. What I'm asking for is simple: give me a physical indicator on the Omi device. 🔴 LED light — solid or pulsing when recording is active. Red, green, whatever. Just something I can see at a glance. ⏰ Haptic/buzz pattern — a distinct buzz on start and another on stop so I can feel the confirmation on omi without looking at my omi or device. In high-value conversations — client meetings, important calls, something I know I'm going to want to remember — I need to know I'm capturing it in real time, not wonder about it afterward. Every wearable and recording device worth its salt has some version of this. It's table stakes UX. This would be a big productivity win for anyone using Omi in professional settings.

Nick K7 6 months ago

1

3.0.21 BUG CONFIRMED OnDeviceApple Transcription error: RECOGNITION_ERROR Failed to access assets Device: 839FE8E1 iOS Happens on all transcription modes Screenshot of logs attached

CRITICAL BUG 3.0.21 - No Voice, No Transcription, No Photos After updating to firmware 3.0.21 my Omi CV1 stopped working completely. Device: Omi CV1 Device ID: 839FE8E1-4F16-013F-26FA-6E17F772F076 Email: arbat77@icloud.com iOS Issues: No voice / 2-way conversation broken No transcription in any mode Photos not syncing I tested all 4 transcription modes: Omi, On Device, Cloud, Parakeet. None of them work. Screenshot attached. Error from logs: [OnDeviceApple] Transcription error: PlatformException(RECOGNITION_ERROR, Failed to access assets, null, null) Please fix ASAP! Screenshot of logs attached

ELITE BROKER 20 days ago

Bug in MCP OAuth endpoint (/v1/mcp/sse) — inconsistent Unknown OAuth client and Server not found errors

Hello, I'm trying to connect the Omi MCP server (https://api.omi.me/v1/mcp/sse) as a Custom Connector in Claude (claude.ai), following the exact guidance shown on the "Developer Settings" screen of the Omi app, which specifies using: OAuth Client ID: omi Client Secret: my MCP API key (omi_mcp_...) When attempting to connect, I receive inconsistent errors across different attempts, using the exact same configuration: {"error":"invalid_request","error_description":"Unknown OAuth client"} {"type":"error","error":{"type":"not_found_error","message":"Server not found","details":{"error_visibility":"user_facing"}},"request_id":"req_011CdNonH1Hcr24nfV1LiUEB"} I've tried recreating the connector from scratch multiple times, with different names, double-checking the URL and credentials each time — the errors persist, alternating between the two. This suggests the client_id: omi may not actually be registered/recognized on your OAuth authorization server, despite being the value indicated by the app itself. Could you please check the configuration of the /v1/mcp/sse endpoint and the omi OAuth client? Thank you.

Adriano Batista da Mota about 2 months ago

1