Decide long-term Emporia data source strategy #12
Labels
No labels
bug
decision
docs
enhancement
integration
ops
security
tech-debt
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/BatteryStorageCalculator#12
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Item 2 of the Recommended Next Implementation Slice in
docs/implementation-audit.md: Decide whether to build a user-provided Emporia adapter later or keep CSV as the long-term import path.Current state: Emporia publishes no customer API. The backend has a full adapter framework - per-home settings, channel maps, sync intervals, backfill and incremental job queueing, dedup by home/source/timestamp - but no adapter behind it. CSV import is the only live path.
Options: build against the unofficial API (breakage risk, credential storage), support user-provided credentials/adapters, or accept CSV permanently and remove the unused framework.
Gates the live-pull issue in this milestone. Worth resolving explicitly - the framework is carrying cost today for a capability that may never arrive.
Code:
backend/src/integrations/emporia.js,backend/src/jobs.js