Releases: koenhendriks/ha-eplucon
Releases · koenhendriks/ha-eplucon
v1.2.2
v1.2.1
v1.2.0
Added
- All missing sensors from the API output:
- Operation Mode
- Seasonal Performance Factor (SPF)
- Position Expansion Ventil
- Number of Starts
- Heating Mode
- Warm Water
- Alarm Active
- Current Heating Pump State
- Current Heating State
v1.1.0
1.1.0 - 2024-09-02
Added
- Homeassistant device info to map entities per device in the integration.
- Debugging logs for API calls to be able to trace received data.
- CI using GitHub Actions including HACS validation.
- Missing Binary sensors (as reported by killer8):
- Active WW request
- Direct Outlet (DG1)
- Mixture Outlet (SG2)
- Mixture Outlet (SG3)
- Mixture Outlet (SG4)
Changed
- Checking for existing value of entity is now stricter on entity value instead of global device
realtime_info
Removed
- Device name from default entity name
v1.1.0 Beta
1.1.0 - 2024-09-01
Added
- Homeassistant device info to map entities per device in the integration.
- Debugging logs for API calls to be able to trace received data.
Removed
- Device name from default entity name
v1.0.0
1.0.0- 2024-08-28
Added
- Initial release of the Eplucon Home Assistant Integration.
- Support for retrieving real-time device information from the Eplucon API.
- Added
DeviceDTO
,RealtimeInfoDTO
, andCommonInfoDTO
for structured data management. - Integration with Home Assistant's sensor platform.
- Automatic sensor entity creation based on Eplucon devices and their real-time data.
- Configuration via Home Assistant's UI, including token-based authentication.
- Data fetching and update mechanism using Home Assistant's
DataUpdateCoordinator
. - Error handling and logging for API errors and data fetching issues.
Fixed
- Issues with sensor entity registration on restart.
- Corrected handling of DTO conversion from API responses.
- Addressed bug with entity setup causing entities to be marked as "no longer provided" after restart.
Known Issues
- Some device data may be returned as empty lists (e.g.,
heatpump
data) due to API response inconsistencies. - Minor delays in data updates may occur depending on API response time.