Before you file
What problem are you trying to solve?
The sun position, cloud cover, and shading visualization appear to be based on the Home Assistant instance's configured home zone (zone.home). This works fine when the HA instance is physically co-located with the PV installation being monitored, but breaks down for a use case that's becoming more common with energy-sharing schemes (e.g. Belgium's "energiedelen"): monitoring a family member's PV installation remotely, where their production data is shared into your own HA instance as part of an energy-sharing arrangement.
In this scenario, the PV entity in HA correctly reflects their production, but the card's sun arc, incidence ray, and cloud cover reflect the location of my HA instance, not the actual site of their installation. The visual layer ends up showing the wrong sun position/weather for the panels it's supposedly illustrating, even though the underlying production numbers are accurate.
Proposed solution
Add optional latitude and longitude config fields to the card. When set, use these coordinates for the solar position, weather fetch, and map center instead of falling back to zone.home. This would let a single HA instance host multiple correctly-located Helios cards — one for the local installation, and others for any remote installations whose production is shared in (e.g. via energy-sharing/net-metering arrangements). When left unset, keep the current default behavior for backward compatibility.
Alternatives considered
No response
Before you file
What problem are you trying to solve?
The sun position, cloud cover, and shading visualization appear to be based on the Home Assistant instance's configured home zone (zone.home). This works fine when the HA instance is physically co-located with the PV installation being monitored, but breaks down for a use case that's becoming more common with energy-sharing schemes (e.g. Belgium's "energiedelen"): monitoring a family member's PV installation remotely, where their production data is shared into your own HA instance as part of an energy-sharing arrangement.
In this scenario, the PV entity in HA correctly reflects their production, but the card's sun arc, incidence ray, and cloud cover reflect the location of my HA instance, not the actual site of their installation. The visual layer ends up showing the wrong sun position/weather for the panels it's supposedly illustrating, even though the underlying production numbers are accurate.
Proposed solution
Add optional latitude and longitude config fields to the card. When set, use these coordinates for the solar position, weather fetch, and map center instead of falling back to zone.home. This would let a single HA instance host multiple correctly-located Helios cards — one for the local installation, and others for any remote installations whose production is shared in (e.g. via energy-sharing/net-metering arrangements). When left unset, keep the current default behavior for backward compatibility.
Alternatives considered
No response