3 Commits

Include renames

Author	SHA1	Message	Date
tliu93	682e06d256	modbus: add explicit cascade delete (device + readings + toggles + HA cleanup) ... A disabled device with historical readings still cannot be deleted by default (409 guard stays, to prevent accidental data loss). A new explicit opt-in lets the user remove it for real: - DELETE /api/modbus/devices/{uuid}?cascade=true removes the device's readings and exposed_entity_toggle rows, then the device, in one transaction (FK order: readings before device). Best-effort clears the HA discovery configs first (MQTT not connected -> no-op, never blocks the delete). Default (no cascade) unchanged. Returns 200 with deletion counts. - Frontend: a 'Force Delete (all data)' button appears only after the 409, with a red irreversible warning; cascade is sent only on that explicit action. - Also corrected a stale comment: FK RESTRICT IS enforced at runtime now.	2026-06-24 17:38:52 +02:00
tliu93	68165f0e01	M5-T07: add latest-reading cards and Recharts trend charts; readings return most-recent rows	2026-06-22 14:17:59 +02:00
tliu93	702a1cec00	M5-T05: add Modbus JSON API (device CRUD, readings, metrics, test)	2026-06-22 13:37:48 +02:00