Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web Interface Fails to Display Multiple Transactions Across Different Connector IDs #37

Open
Tano-Coppoletta opened this issue Nov 6, 2023 · 3 comments

Comments

@Tano-Coppoletta
Copy link

Issue Description:
The web interface does not display all active transactions when multiple transactions are started across different connectors. Transactions initiated on one connector are visible, but subsequent transactions on different connectors do not appear in the interface.

Steps to Reproduce:

  1. Send a StartTransaction message using connectorId 1 and note the transaction on the web interface.
  2. Send another StartTransaction message with connectorId 2, identical in all other aspects.
  3. Observe that the second transaction is not visible in the web interface.

Expected Behavior:
The web interface should display all active transactions regardless of the connector ID, provided each transaction is distinct and properly initiated.

Actual Behavior:
Only the transaction for the first connectorId is displayed on the web interface. Subsequent transactions with different connectorIds are not shown.

Potential Impact:
This could lead to a lack of visibility for station operators, causing confusion and potential mismanagement of charging stations.

I hope this report helps in pinpointing the issue for a swift resolution.

Best regards,
Gaetano Coppoletta

@dallmann-consulting
Copy link
Owner

I can't reproduce the issue. We are using the system in a productive enviroment and our chargers behave like one chargepoint with multiple connectors. And the web UI shows all running transaction correctly.
Did you refresh the UI? There is currently no automatic refresh. The reason could also be broken transactions in the database from previous tests.

@dallmann-consulting
Copy link
Owner

I've extended the 1.6 simulator to handle two connectors. Both transactions are handled correctly on the server side and the WebUI shows the correct status of both connectors. It just needs a manual refresh in the browser.

image

Can you please double check the behavior?

@Tano-Coppoletta
Copy link
Author

In the version that you have sent me for linux, I still see the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants