Forecast.Solar has always assumed that solar panels stay where they were installed. On 21 October 2026 a change was merged into Home Assistant's development branch that drops that assumption, so it is lined up for the 2026.11 release. The integration can now follow Home Assistant's home location and read the tilt and direction of each panel group from sensors.

The pull request was written for people who run Home Assistant on a camper, caravan, boat or car with panels on the roof. Until now the only way to get a forecast for a new spot was to delete the integration and add it again. The issue asking for this dates back to January 2023.

Location: fixed or following the home

Setup now has two steps. In the first you pick where the location and the angles come from. For the location there are two choices: "Enter fixed coordinates", which works as before, or "Follow the Home Assistant location, for homes that move such as campers or boats", which needs no coordinates at all.

An entry that follows the home location refreshes when it moves, but at most once per update interval. That is deliberate: if a GPS tracker keeps moving the home location, the integration won't burn through the Forecast.Solar API rate limit. The integration only follows the home location. Something else in the setup still has to update it.

Angles from a sensor

Declination (tilt) and azimuth (direction) can each be a fixed number or a sensor, for example a compass on a panel that turns. Sensors are read on every forecast update. The tilt sensor has to report 0 to 90. The direction sensor can use 0 to 360 or -180 to 180, and neither has to use degrees as its unit.

The form checks a sensor when you pick it. A sensor that doesn't exist or reports something that isn't a number in range is refused. One that is unavailable or unknown at that moment is accepted.

If a sensor stops answering while the integration is running, it keeps the last reading and logs a single warning. That reading is not kept across a restart or reload. After one, the entry keeps retrying until every sensor has a value.

Less re-adding, fewer API calls

  • The location can be changed later by reconfiguring the entry, and each panel group's angles and sensors by reconfiguring that group.
  • The entry reloads only when a value that feeds the forecast changes. Renaming a group costs no API request, and renaming a sensor doesn't trigger a reload either.
  • A group named after a sensor shows its entity ID and follows a rename. A title you set yourself is kept.
  • Diagnostics now say whether the location is fixed or follows the home, instead of showing redacted coordinates.

The matching documentation update was still waiting for review at the time of writing.