Skip to content

Known Limitations and Roadmap

Jump to bottom
Chris Nighswonger edited this page Apr 2, 2026 · 2 revisions

Known Limitations and Roadmap

This page summarizes current limitations and near-term evolution themes based on repository code and docs.

Current Limitations

Multi-hardware drivers are in testing

The driver abstraction layer (StationDriver ABC) is in place and the Davis legacy serial driver is stable. Drivers for Davis Vantage, WeatherLink Live, WeatherLink IP, Ecowitt, Ambient Weather, and WeatherFlow Tempest are implemented and awaiting hardware validation — see Supported Hardware for status and issue links. Contributors with matching hardware are welcome to help test.

Single-node SQLite architecture

SQLite is appropriate for self-hosted single-instance deployments, but requires operational care for long-term retention and backup discipline.

Security model is LAN/self-host oriented

Built-in session authentication and API key support protect all admin endpoints. However, Kanfei does not include TLS — HTTPS should be provided via a reverse proxy for any non-trusted-LAN deployment. See Security and Networking.

External dependency sensitivity

Optional capabilities depend on third-party services and network availability:

  • NWS/forecast data
  • AI nowcast provider API
  • WU/CWOP uploads

Feature maturity varies

Core polling/dashboard paths are mature relative to some optional advanced workflows.

Roadmap Signals in Repo Docs

Repository docs indicate active/planned work around:

  • hardware validation and community testing for new drivers
  • network station configuration UI improvements
  • operational and documentation expansion

Notable references:

  • docs/DRIVER_ROADMAP.md — full hardware driver roadmap with protocol details
  • docs/HARDWARE_TEST_PLAN.md — field testing checklist for new drivers
  • Hardware testing issues: #1 (Vantage), #2 (Ecowitt), #3 (Tempest), #4 (Ambient), #5 (WL Live), #6 (WL IP)

Practical Guidance for Operators

  • Treat optional integrations as additive, not required for core station logging.
  • Use backups and runbook practices before major upgrades.
  • Keep a staging test path for higher-risk changes.

Practical Guidance for Contributors

  • Verify feature claims against code paths before documenting.
  • Keep wiki updates synchronized with API/config changes.
  • Prioritize test coverage for protocol parsing and critical service behaviors.
  • New hardware drivers should implement the StationDriver ABC and follow the test plan in docs/HARDWARE_TEST_PLAN.md.

Change Management Note

Given active development, prefer "as implemented" wording in docs and avoid assuming roadmap completion without matching code evidence.

Clone this wiki locally