Releases: SpanPanel/span
v1.3.1
🐛 Bug Fixes
-
Fix reload loop when circuit name is None (#162, @NickBorgers): Fixed infinite reload loop that caused entity flickering when the SPAN panel
API returns None for circuit names.
Thanks to @NickBorgers for correctly analyzing a solution. @cayossarian. -
Fix spike cleanup service not finding legacy sensor names (#160, @mepoland ): The
cleanup_energy_spikesservice now correctly finds sensors regardless of naming pattern (friendly names, circuit numbers, or legacy names withoutspan_panel_prefix).
Also adds optionalmain_meter_entity_idparameter allowing users to manually specify the
spike detection sensor when auto-detection of main meter fails or that sensor has been renamed.
@cayossarian.
🔧 Improvements
- When a user has customized an entity's friendly name in Home Assistant, the integration skips reload request for that entity. @cayossarian
v1.30
🔄 Changed
Bump span-panel-api to v1.1.14: Recognize panel Keep-Alive at 5 sec, Handle httpx.RemoteProtocolError defensively, Thanks to
@NickBorgersOnLowSecurityNode - Addresses Issue #156
v1.30b2
Merge pull request #159 from SpanPanel/1_30 Handle httpx.RemoteProtocolError
v1.30b1
Full Changelog: v1.29...v1.30b1
v1.29
Removed Decreasing Energy Protection: Reverted the TOTAL_INCREASING validation that was ignoring decreasing energy values that were thought to occur a limited number of updates but turned out to be permanent under-reporting of SPAN cloud data that manifested during firmware updates. The bug is on the SPAN side and can result in spikes in energy dashbaoards after firmware updates. See the Trouble-Shooting section of the README.md for more information.
Energy Spike Cleanup Service: New span_panel.cleanup_energy_spikes service to detect and remove negative energy spikes from Home Assistant statistics caused by panel firmware updates. Includes dry-run mode for safe preview before deletion.
Firmware Reset Detection (Beta): Monitoring of main meter energy sensor to detect errant (negative energy reports over time). Sends a persistent notification when detected, guiding users to adjust statistics if desired.
v1.2.8
- Fix total increasing sensors against receiving data that is less than previously reported as can occur when the panel upgrades
- Fix feedthrough sensor types now set to TOTAL instead of TOTAL_INCREASING
1.2.7
What's Changed
- fix don't call simulation listener, not in sim mode by @cayossarian in #145
- Fix grace period restoration on restart by @cayossarian in #149
- ci(deps): bump actions/checkout from 5 to 6 by @dependabot[bot] in #148
- Fix energy restore attr error by @cayossarian in #150
Full Changelog: v1.2.6...1.2.7
v1.2.6
- Panel Level Net Energy: Add net energy sensors for main meter and feed-through (consumed - produced)
- Net Energy Config Options: Added separate config options to enable/disable panel, circuit, leg-based net energy. Disabling circuit net energy can help
resource constrained installations since the sensors are not created or updated - Circuit Naming Logic: Fixed logic for circuit-naming patterns to ensure proper entity ID generation and panel prefixes (fresh installs only)
- Entity ID naming Choices: Restored the ability to change entity ID naming patterns in live panels (circuit tab-based sensors only, not panel)
- Panel Friendly Name Sync: Fixed regression in panel circuit name synchronization. A new install will sync all friendly names once on the first refresh and
anytime a user changes a name in the SPAN App changes the name in the mobile/SPAN App. - API Optimization: Removed unnecessary signal updates to improve performance and reduce overhead
- API Dependencies: Updated span-panel-api OpenAPI package to version 1.1.13 to remove the cache
- Resolve Cache Config Entry Defect: Fixed an issue where a 1.2.5 config entry could attempt to set up a cache window in the underlying OpenAPI library that
was invalid
v1.2.5
- Circuit Based Naming: Circuit based entity_id naming was not using both tabs of a 240V circuit in the name. Existing entity_id's are unchnaged except fresh installs.
- Switches and Selects Naming: were creating proper friendly ID's but not looking up migration names that night have been customized in 1.2.4
Full Changelog: v1.2.4...v1.2.5