Add dual-sensor support for simultaneous Power and Energy uploads#4
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces the ability to configure an optional secondary solar sensor, allowing users to push both Power (W) and Energy (Wh) data to PVOutput simultaneously.
What Changed:
Added an optional secondary_entity_id to the config_flow schema and const.py.
Updated the init.py payload logic to dynamically evaluate both selected sensors. It automatically assigns the correct v1 (Energy) and v2 (Power) parameters based on their units.
Added a safety net to detect if a user accidentally selects two sensors of the same type (e.g., two Watt sensors), gracefully ignoring the duplicate and logging a warning.
Updated all translation files (English, German, Spanish, Japanese, Traditional/Simplified Chinese) with markdown-formatted UI instructions explaining "Smart Detection" vs. "Maximum Accuracy."
Details:
Previously, users could only provide a single generation sensor, forcing PVOutput's backend to mathematically estimate the missing metric (which can cause graph lag or inaccuracies on cloudy days). By uploading both the exact live power curve and the exact daily yield at the same time, this update provides the "gold standard" for dashboard accuracy.
Because the new field is optional, this change is 100% backwards compatible for existing users.
Example Logs
With a single (total energy generated) sensor configured:
With both total energy generated and power sensors configured:
Issue: #1