Firmware issues - HAEdwin/homeassistant-apsystems_ecu_reader GitHub Wiki
For issues with Daily or Lifetime Energy defaulting to zero or negative values, use the utility meter integration:
utility_meter:
lifetime_energy:
source: sensor.ecu_xxxxxxxxxxxx_current_power
template:
- sensor:
- name: "Lifetime Energy (kWh)"
unit_of_measurement: "kWh"
state: "{{ states('sensor.lifetime_energy')|float(0) / 1000 }}"
Purpose of Firmware-Related Diagnostic Sensors
The APsystems ECU Reader integration includes several firmware-related diagnostic sensors to help users understand the capabilities and operational status of their ECU device. These sensors serve multiple important purposes:
1. Feature Compatibility Verification
Different ECU models and firmware versions support different features. The firmware sensors allow:
- Automatic capability detection: The integration uses firmware information to determine which features can be enabled
- Appropriate UI presentation: Only compatible options are presented in the Home Assistant interface
- Preventing unsupported operations: Commands that aren't supported by your specific ECU model are automatically disabled
2. Troubleshooting Assistance
When troubleshooting integration issues, firmware information is essential:
- Support requests: Including firmware information helps developers diagnose problems more efficiently
- Known firmware bugs: Some firmware versions have known issues that may affect integration behavior
- Version verification: Ensures you're running a compatible firmware version
3. Update Management
The firmware sensors help manage ECU updates:
- Track current version: Always know which firmware version is running on your ECU
- Update verification: Confirm successful firmware updates
- Feature rollout: Be aware when new firmware enables additional integration features
Available Firmware Sensors
| Sensor | Description | Notes |
|---|---|---|
sensor.firmware_version |
Reports the current firmware version running on your ECU | Format varies by ECU model |
ECU Model Detection
The integration uses the ECU ID format to determine the model:
- ECU-R-Pro models have ECU IDs starting with "2162"
- ECU-C models have ECU IDs starting with "215"
Combined with the firmware version, this allows the integration to precisely tailor available features to your specific hardware.
Feature Availability by Model
| Feature | ECU-R | ECU-R Pro | ECU-C | Notes |
|---|---|---|---|---|
| Basic monitoring | ✓ | ✓ | ✓ | All models support basic monitoring |
| Inverter power control | ✗ | ✓ | ✓ | Requires firmware support |
| CT sensor readings | ✗ | ✗ | ✓ | Hardware-dependent feature |
| Zero export control | ✗ | ✗ | ✓ | Hardware-dependent feature |
| ECU reboot | ✗ | ✓ | ✓ | Requires firmware support |
The firmware sensors are essential diagnostic tools that help ensure the integration works correctly with your specific ECU hardware and firmware combination.