Sending a single inject event to a CS-req-JSON node generates multiple messages in log

[robinsmidsrod]

I have a simple flow with an inject node that sends a timestamp to two CS Request JSON nodes, and one node is configured with a TriggerMessage/MeterValues command and the other with a TriggerMessage/StatusNotification command.

I then see this in the log:

10/1/2023, 4:25:10 PM    node: OCPP Server Port 9595     type: request   data: [2, "d5671934-f188-4cf1-85f0-e6f9f3060ae2", "TriggerMessage", {"requestedMessage":"MeterValues"}]
10/1/2023, 4:25:10 PM    node: OCPP Server Port 9595     type: request   data: [2, "f771e77c-0777-4b79-8138-1fdf96681547", "TriggerMessage", {"requestedMessage":"MeterValues"}]
10/1/2023, 4:25:10 PM    node: OCPP Server Port 9595     type: request   data: [2, "726b3691-a755-473a-9276-a19f13fbfde9", "TriggerMessage", {"requestedMessage":"MeterValues"}]
10/1/2023, 4:25:10 PM    node: OCPP Server Port 9595     type: request   data: [2, "8f4c9285-12aa-457f-9dbb-4ef1b46b37cb", "TriggerMessage", {"requestedMessage":"StatusNotification"}]
10/1/2023, 4:25:10 PM    node: OCPP Server Port 9595     type: request   data: [2, "9ee6c8be-094f-4f31-b39e-3c0f5baa4842", "TriggerMessage", {"requestedMessage":"StatusNotification"}]
10/1/2023, 4:25:10 PM    node: OCPP Server Port 9595     type: request   data: [2, "9a66c4f9-b4fa-475f-8a4f-ba136c43860a", "TriggerMessage", {"requestedMessage":"StatusNotification"}]
10/1/2023, 4:25:10 PM    node: OCPP Server Port 9595     type: replied   data: [3, "726b3691-a755-473a-9276-a19f13fbfde9", {"status":"Accepted"}]

Is there a reason I see three lines of the send request for each command in the log file? I would've expected only one message per command in the log file.

It seems like the CP only responds to one of them, and doesn't respond to the rest. I'm assuming this is some kind of debounce behavior on the CP

This seems like a bug to me. Are you able to reproduce?

If it matters, I'm using a ChargeAmps Halo firmware version 169, hardware version 3 charger.

Using node-red-contrib-ocpp version 1.3.6 with Node-RED 3.0.2.

[jarylince]

I'm having exactly the same problem. The thing is that sometimes works correcly (one request is traduced to just one command in the OCPP log file). I can't reproduce the issue sistematicaly.
Additionally, I found that, if multiple command lines appers in the OCPP log file (even that just one commant request was fired through the server node) the server does not send any other message to the charger anymore (I need to restart the nodes to work again).
I'm working with node-red-contrib-ocpp version 1.3.5.
I wanted to update the version to the last one (1.3.6) but according to the previous comment, it seems that the issue also affects to the last version.
Anyone else has detected this problem?

[robinsmidsrod]

What I figured out, after a while, was that whenever I sent stuff to the charger that it didn't understand, it had a tendency to lock itself up, and power-cycling the charger was the only way to get it back to communicating properly again. Seems like the charger firmware doesn't have a lot of protection against bad input. Not sure if it is related to this issue, but I've kinda forgotten about this bug report after I got my NodeRED flow to work the way I needed.