5 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	d7f0731d1c	ha_discovery: publish state/availability under home_automation prefix ... Follow the standard MQTT Discovery split: discovery config stays under the HA discovery prefix (homeassistant/.../config, required), but the actual state and availability are published under our own prefix (default home_automation/). The config payload's state_topic/availability fields point at the new prefix so HA reads state from there. - new config ha_state_topic_prefix (default home_automation). - build_discovery_payload + all publish_* split discovery_prefix (config topic) from state_prefix (state/availability). energy-cost still omits availability; modbus availability structure unchanged. Tests updated.	2026-06-24 16:21:15 +02:00
tliu93	7e61b0a938	HA Discovery fix: energy-cost sensors are always-available ... The energy-cost device has only sensors (no online/offline heartbeat), but the discovery config still declared an availability topic that nothing ever publishes 'online' to — so Home Assistant marked every energy-cost entity 'unavailable' even though the state topic was being published (visible in MQTT Explorer). - DeviceInfo gains provides_availability (default True, keeps Modbus behavior). - _energy_cost_provider sets provides_availability=False. - build_discovery_payload only emits availability/availability_mode for devices that publish a heartbeat; HA treats the rest as always-available. - Test asserts energy-cost configs omit availability.	2026-06-24 11:54:49 +02:00
tliu93	35cdc7f22a	M5: use DB-merged runtime settings for MQTT/discovery; add MQTT test button; move Expose panel into config accordion	2026-06-22 20:11:54 +02:00
tliu93	35b95f5c88	M5-T11: add HA discovery and state publishing wired to polling	2026-06-22 15:32:43 +02:00