When sending 'unavailable' to a connector while charging, it change to 'available' for a short time after charging has stopped and then goes to 'unavailable'. · Issue #809 · EVerest/libocpp · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending 'unavailable' to a connector while charging, it change to 'available' for a short time after charging has stopped and then goes to 'unavailable'.
#809
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.
CSMS sent a request to set availability to 'unavailable'
When charging stopped, the CS sent 'available' to the CSMS
After a short amount of time, 'unavailable' was sent to the CSMS.
Although the charger is going to 'unavailable' in the end, it should not go to 'available' in the first place. This might just be a problem with certification.
So if a connector is charging and unavailable is sent, it must go to unavailable as soon as the charging has ended.
To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
OCPP Version
OCPP1.6
Describe the bug
Although the charger is going to 'unavailable' in the end, it should not go to 'available' in the first place. This might just be a problem with certification.
So if a connector is charging and unavailable is sent, it must go to unavailable as soon as the charging has ended.
To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: