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

v1.2.4

What's Changed

• Performance: Revert to native sensors (non-synthetic) to avoid calculation engine for simple math. Features like net energy, OpenAPI, simulation
  are still present. We may reintroduce the synthetic engine later in a modified form to allow users to add attributes, etc.
• Fix sensor circuit-based naming: For new installations with circuit naming provide consistent behavior where all circuits, other than panel have
  circuit names related to the tab (120V) or tabs (240V). We do not modify entity ID's so if an installation had faulty names from a previous release those
  must be renamed manually
• Fix Faulty Legacy Single Panel Config: Provided a repair for a pre-1.0.4 upgraded release where the config entry was missing the device unique ID (serial
  number) causing the new migration for normalized unique keys to fail. This repair only works for single panel installs because we derive the serial number
  from the entities and if more than one serial number is found we cannot determine which config the serial number would match.
• Fixed Unmapped Tab Behavior for Offline Panel: Unmapped tab sensors reported erroneous values when the panel was offline

Full Changelog: v1.2.2...v1.2.4

v1.0.10

Fix

Panel level sensors for generic entity ID mode (new installs) did not have device name

Feature

Add options for selecting the style of entity ID naming and migrating entities

Full Changelog: v1.0.9...v1.0.10