You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The geo location and sun positioning appears tied to the location of the HA instance. While this makes perfect sense as a default, I'm managing a few smart devices at a remote location for my elderly parents.
Describe the solution you'd like
I've configured the remote location with it's own sun2 instance in my local HA and it would be great to be able to use this as an optional config item or to input the individual lat/long location of the cover if the geo position is used directly.
Describe alternatives you've considered
None
Additional context
None
The text was updated successfully, but these errors were encountered:
While it may appear straightforward to incorporate adjustable locations for sun positioning, the reality is more complex. The current sun positioning data is sourced from Home Assistant's core sun integration, which relies on the location settings of your Home Assistant instance. To enable location adjustments, I would need to reimplement a portion of the sun integration within this one. This seems somewhat redundant and could potentially introduce unnecessary complexity.
Checklist
Is your feature request related to a problem? Please describe.
The geo location and sun positioning appears tied to the location of the HA instance. While this makes perfect sense as a default, I'm managing a few smart devices at a remote location for my elderly parents.
Describe the solution you'd like
I've configured the remote location with it's own sun2 instance in my local HA and it would be great to be able to use this as an optional config item or to input the individual lat/long location of the cover if the geo position is used directly.
Describe alternatives you've considered
None
Additional context
None
The text was updated successfully, but these errors were encountered: