- A soon-to-be rewrite of wire-pod.
- See the other MDs for implementation details.
- Token server
- Jdocs server
- Chipper server
- sorta
- STT interface
- Should implement:
Name stringInit() errorProcess(data []int16, data []byte) (string, error)MultiLanguageSupport bool- If true, define SupportedLanguages. That could be a struct containing language, link to model, and accuracy notes
- Should implement:
- Better VAD
- Use same library, just handle more edge cases
- Better voice filtering
- wire-pod's voice filtering seems to slow things down...
- Websocketed API
- Configuration
- Bot settings
- Maybe just use websockets for robot control
- Flutter UI
- Inbuilt BLE with go-ble
- Detect a dev OS. If dev, download logs for SSH key (after trying Anki ssh_root_key) and implement correct vic-cloud and server config
- Handle OTA updates. Consider uploading the OTA to a GitHub release and including an HTTPS->HTTP proxy in Hotwire
- Make connchecks work
- Handle IP changes (both robot and Hotwire server)
- Use combo of multicast and mDNS?
- Easy-to-use "get GUID" API endpoint
- Configurable intent utterances
- Involves a list of commands and descriptions
- Knowledge graph
- Better StreamingKGSim function which actually handles errors
- More LLM commands
- Make conversations happen more
- Weather
- More configurable weather and knowledge graph
- Use interfaces to swap in APIs
- Gemini?
- Test API keys on interface
- Interface should redirect user to API provider login and get API keys via a more correct way
- Security (username/password)?
- Have Bot Settings be its own project which can be directed towards a different server?
- Allow importing data from wire-pod
- Windows
- macOS ARM and x86
- Android
- a better app which creates a foreground service
- Debian/Ubuntu
- Docker (w/ storage and mDNS instructions)
- HA addon
- iOS??
- AUR
- Copied in token, jdocs, and chipper servers from cavalier
- Very broken. This only contains ideas and experiments