Auke Willem Oosterhoff

> know step is call remote_start_ Transaction and then call start_Transaction to start the charger My start_Transaction works well and remote_start_Transaction can call start_Transaction, I don't know the code of...

That is a good catch! Thanks for opening the issue @jainmohit2001. It's surprising that `@after()` handlers are not executed if the `@on()` handler raises an exception. Therefore it's bad API...

Sure, go ahead. PRs are welcome. A lot of issues cover similar topics, so it makes sense to update the examples to make usage of this lib more clear. The...

@jchinnick-nuvation Thanks for your suggestion. I like the the suggestion of ChargePointHandler and ChargePoint. Do you think it makes sense to put `ChargePointHandler` and `ChargePoint` in there own namespace to...

What about the `@after()` decorator? https://github.com/mobilityhouse/ocpp/blob/fdfb5b1b33665dad13708b47226f48b56ee6b438/ocpp/routing.py#L58-L80

Can you post code snippets and/or debug logs that show what you've tried?

The `@after()` decorator is not meant for sending responses back the the peer. The `@on()` handler must be used for that The return value of the `@after()` handlers is discarded....

As I said, you should use the `@after()` decorator for that. Something like: ``` python @after('NotifyEVChargingNeeds') def after_evchargingneeds(self, charging_needs, evse_id, **kwargs): await self.call(NotifyCentralChargingNeedsRequestPayload(...)) ```

I suggest to read the OCPP specification. For OCPP v1.6 you the SetChargingProfile call is used to limit charge rate. For OCPP 2.0.1 I suggest to read section K of...

I have to check HA APIs to so if it's possible. First of all, what do you expect from the integration? How do you want to use the integration?