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

Connector status is not updating #1302

Open
maybeshaed opened this issue Nov 17, 2023 · 4 comments
Open

Connector status is not updating #1302

maybeshaed opened this issue Nov 17, 2023 · 4 comments

Comments

@maybeshaed
Copy link

maybeshaed commented Nov 17, 2023

Checklist

  • [x ] I checked other issues already, but found no answer/solution
  • [x ] I checked the documentation and wiki, but found no answer/solution
  • [x ] I am running the latest version and the issue still occurs
  • [x ] I am sure that this issue is about SteVe (and not about the charging station software or something unrelated to SteVe)

Specifications

SteVe Version     :  3.6.0
Operating system  : Debian 11
Database          : mariadb

Hello everyone, I discovered an error in the operation of the server, the fact is that when the status of the charging port changes in any way, the status in the database is updated (screenshot), but in the panel and in the API itself it remains the same. screenshot

Additional context

Im using users branch that allows more API (idk if it`s the reason of trouble)

upd: looks very weird, after time all works fine i literally didnt touch anything, any ideas guys? (i dont restart server or something, it just works now :/ )

@maybeshaed
Copy link
Author

And i found one more issue, in case of changing availability of both connectors (if I leave the field blank meaning both ports here) the station is indicated by connector ID 0 like here, but if i unlock one of the connectors here, it shows just one connector info (i think it mean station availability) here, so i loosing right information about two connectors, i think it is issue to combine connector id 1 and 2 in one id = 0, it will be better if connector id stays 1,2 without 0

@maybeshaed
Copy link
Author

maybeshaed commented Nov 19, 2023

UPD:
My DC station totally doesnt works with status
Here i reserved it
[INFO ] 2023-11-19 20:38:15,255 de.rwth.idsg.steve.ocpp.ws.WebSocketLogger (qtp1706099897-2291) - [chargeBoxId=EV0070, sessionId=c5136ce7-599c-d6ee-cc06-15b208f2dc14] Sending: [3,"8DA7EDEA-871B-11EE-871B-11EE95EAB103",{"currentTime":"2023-11-19T20:38:15.253Z"}]
[INFO ] 2023-11-19 20:38:22,016 de.rwth.idsg.steve.ocpp.ws.WebSocketLogger (SteVe-Executor-3) - [chargeBoxId=EV0070, sessionId=c5136ce7-599c-d6ee-cc06-15b208f2dc14] Sending: [2,"bc3840ed-f0f1-4682-99f9-88d0a2858898","ReserveNow",{"connectorId":1,"expiryDate":"2023-11-20T00:00:00.000Z","idTag":"0E4E1EA","reservationId":26}]
[INFO ] 2023-11-19 20:38:23,131 de.rwth.idsg.steve.ocpp.ws.WebSocketLogger (qtp1706099897-2291) - [chargeBoxId=EV0070, sessionId=c5136ce7-599c-d6ee-cc06-15b208f2dc14] Received: [3,"bc3840ed-f0f1-4682-99f9-88d0a2858898",{"status":"Accepted"}]
[INFO ] 2023-11-19 20:38:23,350 de.rwth.idsg.steve.ocpp.ws.WebSocketLogger (qtp1706099897-2272) - [chargeBoxId=EV0070, sessionId=c5136ce7-599c-d6ee-cc06-15b208f2dc14] Received: [2,"947BC2E0-871B-11EE-871B-11EE95EAB103","StatusNotification",{"connectorId":1,"errorCode":"NoError","info":"Plug reserved to a concrete user","status":"Reserved","timestamp":"2023-11-19T20:38:22Z","vendorId":"CIRCONTROL"}]
[INFO ] 2023-11-19 20:38:23,356 de.rwth.idsg.steve.ocpp.ws.WebSocketLogger (qtp1706099897-2272) - [chargeBoxId=EV0070, sessionId=c5136ce7-599c-d6ee-cc06-15b208f2dc14] Sending: [3,"947BC2E0-871B-11EE-871B-11EE95EAB103",{}]
[INFO ] 2023-11-19 20:38:23,541 de.rwth.idsg.steve.ocpp.ws.WebSocketLogger (qtp1706099897-2291) - [chargeBoxId=EV0070, sessionId=c5136ce7-599c-d6ee-cc06-15b208f2dc14] Received: [2,"949A5818-871B-11EE-871B-11EE95EAB103","StatusNotification",{"connectorId":2,"errorCode":"NoError","info":"Socket locked by controlling plug","status":"Unavailable","timestamp":"2023-11-19T20:38:22Z","vendorId":"CIRCONTROL"}]

And connector status is not updating here
image

When im triying to trigger statusnotification - i got right info but it doesnt updating indisde my server too, only reconnect to the server helps to got right status inisde the server

@goekay
Copy link
Member

goekay commented Feb 2, 2024

Hello everyone, I discovered an error in the operation of the server, the fact is that when the status of the charging port changes in any way, the status in the database is updated (screenshot), but in the panel and in the API itself it remains the same. screenshot

when rendering the status of a connector, steve always selects the status with the latest timestamp.

pls look at the rows from the database again. you will see that for connector_pks 89 and 90 the status available at 14:07 is the most recent. and the screenshot from web page renders that. why do you think there is a problem?

@goekay
Copy link
Member

goekay commented Feb 2, 2024

UPD:
My DC station totally doesnt works with status
Here i reserved it
...

the status values you sent from logs are from 2023-11-19T20:38:22Z. the webpage shows the status from 22:36. notice that 22:36 is more recent than 20:38. apparently, within these 2 hours things happened and the station sent more status updates.

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