- MQTT: Add support for scheduled battery heating. Payload is JSON with startTime and mode (on or off)
- HA: Expose scheduled battery heating
- HA: Expose some switches as sensors as well to ease automations
- MQTT: Add support for battery heating. True means ON, False means OFF
- HA: Expose battery heating as an ON-OFF switch
- MQTT: Add support for heated seats control on both front left and front right seats. Values range from 0-3 on some models, 0-1 on others. 0 means OFF
- HA: Expose heated seats control as either a select with 4 states (OFF, LOW, MEDIUM, HIGH) or as a ON-OFF switch depending on the reported car feature set
- Align some vehicle control commands to their actual behavior on the official app
- Door closing command should be more reliable now
- The new option
SAIC_PHONE_COUNTRY_CODE
can be used to specify the country code for the phone number used to login
- Gateway was not logging-in properly after a logout
- Config option
SAIC_REST_URI
now points to the new production API endpoint by default
- Config option
SAIC_REGION
is used to select the new API region - Config option
SAIC_TENANT_ID
is used to select the new API tenant
Both values default to the EU instance production values
- Drop config option
SAIC_URI
as it is no longer relevant
- Typo in check_for_new_messages() fixed
- Configurable messages-request-interval
- Switch to saic-python-client-ng library (New SAIC API)
- blowing only command fixed
- Whenever a chargingValue is received that is different from the last received value, a forced refresh is performed
- The socTopic is an optional field in the charging station configuration
- Detection of battery type
- Remove special characters from username to generate valid MQTT topics
- Setting ha_discovery_enabled to False had no effect
- Docker image based on python:3.11-slim
- Force refresh by charging station only if charging value has changed
- MQTT connection error logging
- Front window heating enables "Blowing only"
- Binary string decoding issue fixed in saic-python-client 1.6.5
- Error message decoding issue fixed in saic-python-client 1.6.4
- Previous fix corrects dispatcher message size for V2 messages. Now it is also fixed for V1 messages.
- Previous fix works only for messages without application data. Those are typically error messages that are provided with wrong dispatcher message size
- Calculate dispatcher message size and use the calculated value if it differs from the provided API value
- Control charge current limit
- Dynamic refresh period during charging
- Force polling around scheduled charging start
- Further A/C enhancements
- Generic charging station integration (OPENWB_LP_MAP argument is deprecated now)
- TLS support
- Keep polling for a configurable amount of time after the vehicle has been shutdown
- Battery (SoC) target load
- Start/Stop charging
- Enhanced A/C control
- Turn off message requests when refresh mode is off
- Home Assistant auto-discovery
- Vehicle and charging status updates stop after a while
- Inconsistent topic name for battery management data (BMS) removed
- docker support for architecture linux/arm/v7
- Using new saic-ismart-client (version 1.3.0)
- Feature: transmit ABRP data even if we have no GPS data
- empty environment variables are ignored
- Driving detection fixed
Vehicle control commands are finally working
- Turn front window defroster heating on or off
- Turn A/C on or off
- Configurable re-login delay
- Using new saic-ismart-client (version 1.2.6)
- Environment variable to configure log level
- environment variable overwrites the predefined default value
- MQTT commands documented in README.md
- Wait 15 seconds (average SMS delivery time) for the vehicle to wake up
- Using new saic-ismart-client (version 1.1.7)
- Improved parsing for configuration value mappings
- Make force command more reliable