Add tariff sensors to Teslemetry #147756
Closed
Add tariff sensors to Teslemetry #147756
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add calendar entities for energy site tariff schedules, providing: - Buy tariff calendar showing energy purchase pricing periods - Sell tariff calendar showing energy sell-back pricing periods Features: - Displays current active pricing period - Shows seasonal pricing variations - Handles time-of-use (TOU) periods - Supports midnight crossing periods
- Update TeslemetryEnergyInfoCoordinator to preserve tariff structure during flattening - Fix test file to only test energy tariff calendars - Update snapshots for energy price calendar entities
Refactors the Teslemetry integration's tariff feature from a calendar entity to a sensor entity. The new sensor displays the current buy/sell tariff price. Key changes: - Removed `calendar.py` and its tests/snapshots. - Modified `sensor.py` to include `TeslemetryTariffSensor`, which calculates and displays the current tariff price and related information (season, period) as attributes. - Updated `__init__.py` to remove the CALENDAR platform. - Updated `strings.json` to move tariff entity names to the sensor domain. - Updated `test_sensor.py` to include tests for the new tariff sensors, and updated `test_sensor.ambr` snapshots accordingly. - Ensured `coordinator.py` and `helpers.py` retain necessary changes for data flattening.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
I got feedback that the tariff calandar PR (#145848) probably shouldnt be a calandar, so this PR refactors it into a sensor entity.
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: