-
-
Notifications
You must be signed in to change notification settings - Fork 373
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
Comments
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 |
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? |
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. |
Checklist
Specifications
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
I
m using user
s 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 :/ )
The text was updated successfully, but these errors were encountered: