- Support Marstek HME cloud-managed placeholder devices (AstraMeter synthetic MAC): derive
remote_idfrom topic encryption, default missing API version to 1, disable inverse forwarding for that MAC pattern, and register HME in brokermin_versions.
- Add support for JPLS-6H and other JPLS-*H Jupiter device variants
- Add support for Venus A and Venus D
- Fixed Venus 3 devices (VNSE3) working on firmware version 139
- Fixed forwarding direction for HMB devices. (#96)
- Added retry logic with exponential backoff for Hame API calls to handle temporary server errors (#97)
- BREAKING: Username and password are now required for Home Assistant addon
- BREAKING: Removed manual device configuration from Home Assistant addon (devices are now automatically discovered via API)
- Added global
inverse_forwardingflag that flips forwarding direction for all devices when enabled. Usually you want to leave that disabled unless you know what you're doing. - Added selective inverse forwarding for HMA/HMF/HMK/HMJ devices via
inverse_forwarding_device_idsconfiguration. Only use this if you previously used Hame Relay with your B2500 in Mode 2. Don't use it for Mode 1. - Added automatic inverse forwarding for all other device types (JPLS, HMM, HMN, HME, TPM-CN, HMG)
- Added support for HMG devices with firmware version >= 154.0
- Add support for Venus 3 devices (VNSE3)
- Added Italian and Dutch translations for Home Assistant addon
- Removed
default_broker_idfrom Home Assistant addon default configuration
- Support multiple remote brokers via new
brokers.json - Added broker configuration for the new 2025 Hame cloud
- Added device types
JPLS-8HandHMG-25 - Log level can now be adjusted via the
LOG_LEVELenvironment variable - Automatically select the appropriate broker based on device firmware
- Add support for HMM-1 (Jupiter)
- Fixed device ID length validation (@seybsen)
- Added support for HMI-1 (800 W Inverter) (@seybsen)
- Fix connection to remove broker by using the correct client ID pattern
- Added health check endpoint for better monitoring and automatic recovery
- Added Docker health check configuration
- Simplify reconnect logic
- Improve message loop prevention
- Added ability to fetch device information from the Hame API using username/password
- Added message loop prevention
- Don't forward messages to Cloud when they've not previously been requested from the Cloud to reduce outbound traffic
- Rate limit outbound requests to Cloud to reduce Cloud broker traffic
- Fixed duplicate subscriptions after reconnect
- Fixed issue with non-inverse forwarding not working as expected
- Introduce device type configuration after Hame blocked subscription to wildcard topics. Make sure to update your configuration file with the new
device_typefield on each device. - Allow overriding forwarding direction per device through the
inverse_forwardingfield in the device configuration
- Fixed inverse forwarding in HomeAssistant Addon
- Fixed issue with inverse forwarding not working as expected
- Allow inverse forwarding direction from Hame to MQTT
- Fixed connection stability issues - forwarder now maintains connection indefinitely
- Added detailed connection status logging for better troubleshooting
- Initial release