André

I am also experiencing this issue :/

Was really that value that you have used? Because if so, you have misspelled "Temperature" ```python #"Current.Import,Energy.Active.Import.Register,Power.Active.Import,SoC,Voltage,Temperture") ```

Hey @nickbedbury did you have a chance to check Aukes comment? Cheers

I will leave it to you if you want to modify this PR or close it and open a new one for 2.0.1

I understand, but the version is no longer supported by OCA and the files are no longer available to download, so I dont think it makes sense to support it...

Besides there is the OCPP 2.0 and then the OCPP 2.0 errata. The errata was created to solve issues found in 2.0 and 2.0.1 was created to officially solve those...

> > just support the official released versions. > > I think I agree with that. But OCPP 2.0 is an officially released version. It was released in April 2018....

I would back you up 100% on this one if OCA didnt have deleted OCPP 2.0 from their public download server and if we had already chargers/csms in the market...

I think this is a good suggestion and the enhancement should not be too hard as we only need to pass the response to the handler here: https://github.com/mobilityhouse/ocpp/blob/efc8f081d063bb43680fd8f2b8c861a71356d784/ocpp/charge_point.py#L221 To not...

> Assume for now, return value of the @on() handler is passed down to the @after() handler. Modifying the response and trying return it won't send the modified response to...