When starting a charging session, only the safety relays will now be switched before starting delivery of power to the vehicle. The bypass relays are kept closed and will be opened if the 
charging station detects that a safety relay is welded. Note that during a boot sequence the relays are no longer switched.

Bug fixes

• Fixed an issue where data from the P1 smart meter was not parsed correctly. 
  This resolves issues with Active Load Balancing functionality in combination with a P1 DSMR smart meter.
• Fixed an issue where activating the WiFi access point caused an IP conflict with a TCP/IP energy meter and/or when connecting to the charging station with ACE Service Installer, Eve Connect or MyEve.
• Added checks to ensure that a Eichrecht public key can be recovered even when a power outage is too abrupt to properly store it. This caused Eichrecht charging sessions to be labelled as incorrect.
• Fixed an issue where an Eve Single charging station with Active Load Balancing went in safe mode and error 213 state after some time when connected to a Linky smart meter set to TIC Standard mode
• Fixed an issue where starting a session with an e-Socket (Type E) on a double socket station caused a crash.
• Added a check to ensure timely observation of opening of the S2 signal in all cases. This has caused issues with specific vehicles with strict S2 timing regime.
• Fixed an issue where enabling a Modbus TCP/IP energy meter caused a crash on specific hardware revisions
• Fixed an issue where swiping a valid RFID card would result in a return to the idle state after accepting the RFID card rather than starting a transaction
• Fixed an issue where a socket that is not reserved would go to the available state after handling a reservation on Eve Double Pro-line or Twin 4XL
• Translations for the Catalan language have been updated

Back-end communication changes

• Fixed an issue where properties of a Smart Charging Network are not updated throughout the entire SCN when changing SCN specific properties over OCPP.
• Fixed an issue where stack levels of different types of OCPP charging profiles were not taken into account
• Added checks for corrupt entries in the transaction database to ensure successful exchange of OCPP transaction related messages. If a correct entry is found this entry will be skipped in addition to new recovery methods.
• Added AuthorizationTimeout as a new configuration key as an addition to ConnectionTimeout. 
  AuthorizationTimeout specifies the timeout when a user has plugged in the cable, but has not yet authorized. The default value of AuthorizationTimeout will initially be set identical to the value of ConnectionTimeout, even if ConnectionTimeout is set to a non-default value. Setting AuthorizationTimeout to 0 means that no timeout will apply and the charging station will wait indefinitely for an authorization after plugging in the cable.
• When a charging station receives multiple RemoteStop requests for the same transaction it will only process the first request and reject any subsequent requests until the first request is successfully processed.
• Fixed an issue where charging stations with 6mA DC leakage detection reported a trip to the backoffice with a trip current of 0.0mA. Now the reported measurement to the backoffice is the highest measured trip current as opposed to trip current after relay switches off.
• Fixed an issue where a remote firmware update failed due to the charging station trying to connect to changing to a higher network profile. When a remote update is initiated the active network profile will not try to connect to a higher network profile until the firmware update is completed.
• Multiple changes are made relating to the reservation functionality of OCPP:
  • Disabled the backoffice configuration keys ReserveConnectorZeroSupported on OCPP 1.5/1.6J and NonEvseSpecific on OCPP2.0.1
  • A reservation will only be accepted if a socket is specified with the reservation request to the charging station.
  • A reservation made via OCPP is now set to resolved when a transaction is started with the token associated with the reservation.
  • When a duplicate reservation is received the latest iteration will be accepted and older ones will be cleared

Firmware update instructions
With the release of NG9xx Firmware 7.0, there is no longer the option between "A and B firmware versions", as first introduced with version 4.14.0
To update to NG9xx Firmware 7.3.0, please follow the steps according to below schedule: