How winemug/omnicore works
OmniCore is a mobile companion platform for monitoring and controlling Omnipod devices, with RileyLink radio support and documented closed-loop RADD capabilities. The principal runtime path visible here is the Android core service initializing persistence and the Eros pod service; radio discovery and pod setup are separate domain stages. The model contracts define the service boundaries, while the README describes broader app and automation features. Some UI, integration, and automation implementations are unsampled, so their runtime links are not asserted.
Main entry points: ErosPodService.cs Eros pod service · RileyLinkRadioService.cs RileyLink service · Interfaces Core domain contracts · DroidCoreService.cs Android core host
Components 19
Mobile client
- App interface
Client/OmniCore.Client/Views - App view models
Client/OmniCore.Client/ViewModels - Android core host
Client/OmniCore.Client.Droid/Services/DroidCoreService.cs - Platform services
Client/OmniCore.Client.Droid/Platform/CoreApplicationServices.cs
Core services
- Service composition
Configuration/OmniCore.Services - Therapy automation
Configuration/OmniCore.Services - External integrations
Configuration/OmniCore.Services
Device communication
- Eros pod service
Pod/OmniCore.Eros/ErosPodService.cs - Pod request runtime
Pod/OmniCore.Eros/ErosPodRequestProcessor.cs - RileyLink service
Radios/OmniCore.Radios.RileyLink/RileyLinkRadioService.cs - Platform BLE adapter
Client/OmniCore.Client/Platform/CrossBleRadioAdapter.cs
Domain and storage
- Core domain contracts
Model/OmniCore.Model/Interfaces - Therapy profiles
Therapy/OmniCore.Therapy/Profiles - Repository service
Repository/OmniCore.Repository.Sqlite/OmniCore.Repository.Sqlite/RepositoryService.cs - Pod repository
Repository/OmniCore.Repository.Sqlite/OmniCore.Repository.Sqlite/Repositories/PodRepository.cs - Radio repositories
Repository/OmniCore.Repository.Sqlite/OmniCore.Repository.Sqlite/Repositories - SQLite database
Repository/OmniCore.Repository.Sqlite/OmniCore.Repository.Sqlite/Entities/Entity.cs
Other components
- Mobile user
- RileyLink radio
Connections 19
- Mobile user → App interface: uses
README.md - Android core host → Platform services: resolves
Client/OmniCore.Client.Droid/Services/DroidCoreService.cs - Android core host → Repository service: initializes
Client/OmniCore.Client.Droid/Services/DroidCoreService.cs - Android core host → Eros pod service: starts
Client/OmniCore.Client.Droid/Services/DroidCoreService.cs - Service composition → Eros pod service: registers
Configuration/OmniCore.Services/CoreDataServices.cs - Service composition → RileyLink service: registers
Configuration/OmniCore.Services/CoreDataServices.cs - Eros pod service → Pod repository: loads and creates
Pod/OmniCore.Eros/ErosPodService.cs - Eros pod service → Pod request runtime: resolves
- Eros pod service → RileyLink service: uses provider
Pod/OmniCore.Eros/ErosPodService.cs - RileyLink service → Platform BLE adapter: discovers via
- RileyLink service → RileyLink radio: scans
Radios/OmniCore.Radios.RileyLink/RileyLinkRadioService.cs - RileyLink service → Radio repositories: persists radio events
Radios/OmniCore.Radios.RileyLink/RileyLinkRadioService.cs - Repository service → SQLite database: opens connection
Repository/OmniCore.Repository.Sqlite/OmniCore.Repository.Sqlite/RepositoryService.cs - Repository service → Pod repository: initializes
Repository/OmniCore.Repository.Sqlite/OmniCore.Repository.Sqlite/RepositoryService.cs - Eros pod service → Core domain contracts: implements contracts
Pod/OmniCore.Eros/ErosPodService.cs - RileyLink service → Core domain contracts: implements contracts
Radios/OmniCore.Radios.RileyLink/RileyLinkRadioService.cs - Therapy profiles → Core domain contracts: implements profiles
- Therapy automation → Therapy profiles: uses profiles
- External integrations → Core domain contracts: uses service contracts
Configuration/OmniCore.Services/CoreDataServices.cs