Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Voltage and Current displayed in Overview > Solar Yield #1883

Closed
SenH opened this issue Jan 30, 2025 · 3 comments
Closed

No Voltage and Current displayed in Overview > Solar Yield #1883

SenH opened this issue Jan 30, 2025 · 3 comments
Assignees
Milestone

Comments

@SenH
Copy link

SenH commented Jan 30, 2025

Overview > Solar Yield

Image

Voltage/Current is displayed in Settings > Devices > Solar

Image

I updated today to Venus v3.54 but this has never been displayed since GUIv2 was introduced.

@blammit blammit added this to the Version 1.1.0 milestone Jan 31, 2025
@blammit
Copy link
Contributor

blammit commented Jan 31, 2025

This can be tested on installations with a single-phase PV inverter.

May be related to #1713.

@chriadam chriadam self-assigned this Feb 5, 2025
@chriadam
Copy link
Contributor

chriadam commented Feb 5, 2025

According to https://github.com/victronenergy/venus/wiki/dbus#pv-inverters the /Ac/Current and /Ac/Voltage paths are deprecated, and presumably systemcalc isn't publishing appropriate values there, but we use those in PvInverter.qml. For single-phase inverters, we can just find and use the appropriate per-phase data e.g. /Ac/L1/Current and /Ac/L1/Voltage directly, however for multi-phase systems I am not sure what we can do (voltage cannot be summed, and summing separate phases of AC current makes no sense either). Well, I will fix the single-phase case now, and we can discuss the multiphase case further in issue 1713.

chriadam added a commit that referenced this issue Feb 5, 2025
The /Ac/Current and /Ac/Voltage paths for pvinverters are
deprecated / no longer valid.

Instead, determine whether there is a single valid phase
available for a given pvinverter, and if so, export that
phase's current and voltage as properties.

(If multiple valid phases exist, we cannot export valid
aggregate values for current or voltage, so return NaN.)

Contributes to issue #1883

Contributes to issue #1713 in the case where only a
single valid phase exists in the pvinverter device.
chriadam added a commit that referenced this issue Feb 5, 2025
The /Ac/Current and /Ac/Voltage paths for pvinverters are
deprecated / no longer valid.

Instead, determine whether there is a single valid phase
available for a given pvinverter, and if so, export that
phase's current and voltage as properties.

(If multiple valid phases exist, we cannot export valid
aggregate values for current or voltage, so return NaN.)

Contributes to issue #1883

Contributes to issue #1713 in the case where only a
single valid phase exists in the pvinverter device.
chriadam added a commit that referenced this issue Feb 17, 2025
The /Ac/Current and /Ac/Voltage paths for pvinverters are
deprecated / no longer valid.

Instead, determine whether there is a single valid phase
available for a given pvinverter, and if so, export that
phase's current and voltage as properties.

(If multiple valid phases exist, we cannot export valid
aggregate values for current or voltage, so return NaN.)

Contributes to issue #1883

Contributes to issue #1713 in the case where only a
single valid phase exists in the pvinverter device.
chriadam added a commit that referenced this issue Feb 17, 2025
The /Ac/Current and /Ac/Voltage paths for pvinverters are
deprecated / no longer valid.

Instead, determine whether there is a single valid phase
available for a given pvinverter, and if so, export that
phase's current and voltage as properties.

(If multiple valid phases exist, we cannot export valid
aggregate values for current or voltage, so return NaN.)

Contributes to issue #1883

Contributes to issue #1713 in the case where only a
single valid phase exists in the pvinverter device.
chriadam added a commit that referenced this issue Feb 18, 2025
The /Ac/Current and /Ac/Voltage paths for pvinverters are
deprecated / no longer valid.

Instead, determine whether there is a single valid phase
available for a given pvinverter, and if so, export that
phase's current and voltage as properties.

(If multiple valid phases exist, we cannot export valid
aggregate values for current or voltage, so return NaN.)

Contributes to issue #1883

Contributes to issue #1713 in the case where only a
single valid phase exists in the pvinverter device.
chriadam added a commit that referenced this issue Feb 18, 2025
The /Ac/Current and /Ac/Voltage paths for pvinverters are
deprecated / no longer valid.

Instead, determine whether there is a single valid phase
available for a given pvinverter, and if so, export that
phase's current and voltage as properties.

(If multiple valid phases exist, we cannot export valid
aggregate values for current or voltage, so return NaN.)

Contributes to issue #1883

Contributes to issue #1713 in the case where only a
single valid phase exists in the pvinverter device.
chriadam added a commit that referenced this issue Feb 18, 2025
The /Ac/Current and /Ac/Voltage paths for pvinverters are
deprecated / no longer valid.

Instead, determine whether there is a single valid phase
available for a given pvinverter, and if so, export that
phase's current and voltage as properties.

(If multiple valid phases exist, we cannot export valid
aggregate values for current or voltage, so return NaN.)

Contributes to issue #1883

Contributes to issue #1713 in the case where only a
single valid phase exists in the pvinverter device.
@chriadam
Copy link
Contributor

Merged PR#1892 to resolve this issue. Closing as fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants