ValueError: 0 is not a valid alternator_errorcode about hass-victron

[sfstar]

The victron modbus TCP spec sheet references only the following return codes for that register address:
12=High battery temperature;13=High battery voltage;14=Low battery voltage;15=VBat exceeds $CPB;21=High alternator temperature;22=Alternator overspeed;24=Internal error;41=High field FET temperature;42=Sensor missing;43=Low VAlt;44=High Voltage offset;45=VAlt exceeds $CPB;51-52=Battery disconnect request;53=Battery instance out of range;54=Too many BMSes;55=AEBus fault;56=Too many Victron devices;58-61=Battery requested disconnection;91=BMS lost;92=Forced idle;201=DCDC converter fail;201-207=DCDC error
Therefore, it seems that this is another instance of the documentation not matching real world modbus server implementation by victron.

[sfstar]

Hello @Next9999,

Would it be possible for you to find out the alternator status in the GX device when the errorcode 0 is returned?
So that we can implement this undocumented state into the integration.
Based on it's value I believe it might reflect an OK / no error state but I want to make sure before implementing.