V1.5.0

What's changed

This release brings a major internal refactor of the API layer and improves compatibility with the current EU5 FusionSolar web login flow.

Internal API refactor

The previous monolithic API implementation has been split into a modular package structure with dedicated mixins for:

• authentication
• station handling
• battery data
• inverter data
• social contribution
• energy balance
• installation flow parsing

This refactor does not change the public behavior of the integration, but it makes the codebase much easier to maintain and prepares it for future expansion, such as additional device domains.

Installation flow restructuring

The installation-level logic was separated from the main API class into a dedicated installation domain. This includes:

• realtime flow retrieval
• flow node and link parsing
• device DN discovery
• installation-level sensor output building
• installation device creation

The result is a much smaller and clearer main API class.

Inverter domain cleanup

Inverter-specific discovery and metadata loading were moved into the inverter domain, improving separation of responsibilities and keeping inverter logic grouped together.

Improved EU5 login compatibility

The EU5 login flow has been updated to better match the current FusionSolar browser login process.

This includes:

• support for service-aware login URLs
• service-aware validateUser requests
• preserved fallback to the legacy login flow for backwards compatibility

This should improve compatibility for users whose credentials work on the FusionSolar website but previously failed in Home Assistant with:
Login response did not include redirect information
or
errorCode=406

Notes

• Existing entity names and unique IDs are preserved
• Existing coordinator behavior is unchanged
• Existing working installations should continue to work thanks to the legacy fallback path