How to handle responses from the Backend

I’m sorry if this sounds like a stupid question, but I’m just a hobby developer and kind of stuck here.

Regarding the classic example from the protocol (Authorize, StartTransaction, Authorize, StopTransaction), how can I handle the .conf responses from the charging stations ?

I have two seperate scripts as in the examples. The .req from the CP side works perfectly, but how can I handle the answer from the Charging Station ?

I initially thought on using @on(Action.BootNotification) to catch the call_result.BootNotification on CP side, but nothing happens.

[OrangeTux]

The @after() is a post request hook. It’s triggered by requests, not responses. Similar to the @on() decorator, that is only triggered by requests too, not responses. Therefore, the suggestion from @proelke doesn’t work.

Your code, @c0nr3f , works and makes sense to me. Although I suggest a small change: replace asyncio.create_task(self.send_authorize()) with await self.send_authorize().

Using a fire and forget strategy of tasks using asyncio.create_task() is dangerous. Errors raised during it’s execution don’t bubble up to the caller.

[c0nr3f]

But then we are back at the question, how to handle the response from the backend. How would you code an Authorize call as a reaction to the BootNotification.conf ?