OpenGlucose is a volunteer, early-stage wellness/reference project. Support is best effort and does not include medical advice, emergency monitoring, sensor warranty service, or a guarantee that a device is compatible.
- Search the documentation and existing issues.
- File a bug using the bug-report form when behavior is reproducible and does not expose a vulnerability.
- File a feature proposal using the feature-request form and explain the user problem before prescribing an implementation.
- Follow SECURITY.md for security or privately disclosed product-safety problems.
Maintainers may close requests that cannot be reproduced, are outside the project scope, duplicate existing work, or ask OpenGlucose to replace clinical or manufacturer support.
Use synthetic data and redact all health and device information. Never post glucose histories, sensor serials, Bluetooth addresses, account details, location, credentials, provisioning material, or unreviewed diagnostic bundles. Prefer the smallest text excerpt needed to reproduce the problem.
Include the OpenGlucose commit or version, Flutter version, platform and OS version, whether the demo or physical sensor path was used, exact steps, expected behavior, actual behavior, and the relevant test or build result.
- Diagnosis, interpretation of glucose, medication or insulin dosing, treatment recommendations, or emergency monitoring.
- Support for a sensor manufacturer's hardware, account, consumables, warranty, or approved application.
- Recovery of data or devices altered by unofficial or unsafe administration operations.
- Guaranteed response times, compatibility, release cadence, or long-term maintenance of old versions.
For health concerns, contact a qualified clinician. For urgent risk, contact local emergency services. For sensor hardware or approved-product behavior, contact the manufacturer through its official support channel.