The reported value 21.0 for entity evcharger status isn't a decobale value

[gb095666]

Describe the current behavior
Logger: custom_components.victron.sensor
Source: /config/custom_components/victron/sensor.py:191
integration: victron (documentation, issues)
First occurred: 11:28:09 (33 occurrences)
Last logged: 15:27:59

The reported value 21.0 for entity evcharger status isn't a decobale value. Please report this error to the integrations maintainer
NoneType: None

What should be updated or changed?
According to the Modbus Spreadsheet, value 21 should be "Start Charging"

0=Disconnected; 1=Connected; 2=Charging; 3=Charged; 4=Waiting for sun; 5=Waiting for RFID; 6=Waiting for start; 7=Low SOC; 8=Ground test error; 9=Welded contacts test error; 10=CP input test error (shorted); 11=Residual current detected; 12=Undervoltage detected; 13=Overvoltage detected; 14=Overheating detected; 15=Reserved; 16=Reserved; 17=Reserved; 18=Reserved; 19=Reserved; 20=Charging limit; 21=Start charging; 22=Switching to 3 phase; 23=Switching to 1 phase; 24=Stop charging

Home Assistant (please complete the following information):
Core 2025.2.4
Supervisor 2025.02.1
Operating System 14.2
Frontend 20250214.0
Victron Integration v0.4.0

Additional context
Add any other context about the request here.

[sfstar]

Issue should be resolved by #274
That PR adds all new decodeable values and registers introduced up til venus os release 3.50

[gb095666]

Issue should be resolved by #274 That PR adds all new decodeable values and registers introduced up til venus os release 3.50

Is there a timeframe for #274 being put into the live version ?

[sfstar]

I expect it to be around a couple of weeks.
Still testing it locally and troubleshooting some registers that result in the integration crashing because the register response is not returned/invallidly returned