2 Commits

Include renames

Author	SHA1	Message	Date
tliu93	e49a6ad963	M5(design): generic modbus_device + JSON readings; YAML profiles; Accordion config; manual CLI/MQTT testing ... Rework the M5 design doc data model and add manual-testing surface: - Two-layer model: rename energy_meters/energy_readings -> generic modbus_device + modbus_reading; readings become a JSON payload blob instead of a wide fixed-column table (aggregation via SQLite json_extract, generated-column index as a future lever). - Protocol knowledge moves to read-only YAML profiles (data+functions, no OOP inheritance); deployment/config (friendly_name, unit_id, host) stays on the device row; multiple devices share one profile. - UUID = stable internal identity, also anchors HA discovery unique_id (Z2M rename model); device metadata for HA derived from the profile. - Naming scheme C: modbus_* / /api/modbus/devices at the data+API layer, 'Energy' as the first domain view in the frontend. - New task M5-T01B: ConfigPage Accordion sectioning (avoids a second in-page side nav conflicting with the T01 app sidebar). - Manual testing: read-only modbus_cli 'probe' subcommand (FC03/04 only, no register writes); mqtt/test now publishes a test message viewable in MQTT Explorer; no MQTT CLI (manual verification via UI + HA).	2026-06-22 11:55:39 +02:00
tliu93	0cb94d85ec	docs(design): plan M4 login-hardening (first) + M5 IoT/energy ... - Add docs/references/SDM120-Modbus-Protocol.md extracted from the SDM120 PDF - M4 login hardening: brute-force exponential backoff, CLI escape hatch (reset-password/unlock/disable-totp), optional TOTP 2FA - M5 IoT/energy: Modbus-TCP SDM120 polling + energy tables, MQTT/HA Discovery expose framework, frontend sidebar + energy view - Add manual acceptance walkthroughs (M4 lock/unlock; M5 energy_cli read) - Index both milestones in docs/design/README.md	2026-06-21 20:46:12 +02:00