You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked other issues already and found no answer
I checked the documentation and found no answer
I am running the latest version and the feature i am requesting is not implemented there
Describe the problem you are trying to solve
In StartTransaction messages, some charging stations seem to set reservationId=0 to communicate that there is no reservation reference. Actually, reservationId is nullable and therefore this attribute can be omitted from payload.
This is a charging station misbehaviour. But it can be fixed (worked around) easily without harming the integrity of the business flows. Our valid reservation ids are coming from a database sequence (PK) and start with 1 anyways. So, there is no overlap between the value ranges.
Describe the solution you'd like
Treat reservationId=0 the same as reservationId=null
Describe alternative solutions or features you've considered
Leave it as is. It does not harm the behaviour. We are just logging warnings that cause noise and might be annoying.
Additional context
...
The text was updated successfully, but these errors were encountered:
Checklist
Describe the problem you are trying to solve
In StartTransaction messages, some charging stations seem to set
reservationId=0
to communicate that there is no reservation reference. Actually, reservationId is nullable and therefore this attribute can be omitted from payload.This is a charging station misbehaviour. But it can be fixed (worked around) easily without harming the integrity of the business flows. Our valid reservation ids are coming from a database sequence (PK) and start with 1 anyways. So, there is no overlap between the value ranges.
Describe the solution you'd like
Treat
reservationId=0
the same asreservationId=null
Describe alternative solutions or features you've considered
Leave it as is. It does not harm the behaviour. We are just logging warnings that cause noise and might be annoying.
Additional context
...
The text was updated successfully, but these errors were encountered: