Open goRaspy opened 5 years ago
Why don’t do that firmware side ?
I do not understand. Steve is a backend compatible with a large amount of charging stations. Not a charger side solution.
Le ven. 5 avr. 2019 à 22:09, Gior80 notifications@github.com a écrit :
Why don’t do that firmware side ?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RWTH-i5-IDSG/steve/issues/126#issuecomment-480406611, or mute the thread https://github.com/notifications/unsubscribe-auth/AJnQzHM1ZN7EJfwLmWTXEKBfRPx33PReks5vd62GgaJpZM4cfnjG .
let me better explain. Reset is already a part of ocpp protocol and already implemented in task you can run over station(as you say). what I'm saying is that if a firmware has a good ocpp implementation it should not hangs or have a good workaround routines. This is why I don't see a global reset as a way to patch bad firmwares
Sorry it is more clear for me now. I completly agree with you but it is a very theorical point of view. In real life with serious experience with différent manufacturers. I can confim the real utility of this feature.
Le ven. 5 avr. 2019 à 22:22, giorgio80 notifications@github.com a écrit :
let me better explain. Reset is already a part of ocpp protocol and already implemented in task you can run over station(as you say). what I'm saying is that if a firmware has a good ocpp implementation it should not hangs or have a good workaround routines. This is why I don't see a global reset as a way to patch bad firmwares
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RWTH-i5-IDSG/steve/issues/126#issuecomment-480410145, or mute the thread https://github.com/notifications/unsubscribe-auth/AJnQzMn4vBjLtrntlD6zUjoEpNHK6ffjks5vd7B9gaJpZM4cfnjG .
so choose right station then :)
Reset is already a part of ocpp protocol ...
it is indeed implemented and you can trigger it for multiple stations manually. as i understand, @goRaspy wants an automated process that triggers this operation at scheduled times without human intervention.
@goRaspy , leaving out a little bit from the topic, but could u share good and bad hanging experience with stations ? I mean more stable and more unstable
@giorgio80 we had multiple github issues with reports due to misbehaving stations. please take a look at them. for example, https://github.com/RWTH-i5-IDSG/steve/issues/116, https://github.com/RWTH-i5-IDSG/steve/issues/94 and later comments in https://github.com/RWTH-i5-IDSG/steve/issues/97
Yes @goekay this is that ^^
@giorgio80 , honnestly I think most of "big" manufacturers have now a mature OCCP implementation for "classic" commands. Most recent commands like charging profile still have ambiguous and exotics implementations. Only big point, it should be forbidden to sell soap charging stations by 2019.
But there is always something "bad" who can happen with an IOT online 24/7.
Ou was not knowing about this regulamentation of soap station from 2019 , it is law ? @goakay we’re making bar chats . Need to continue private ?
No it is a joke :) But there is a huge difference between SOAP and JSON.
Soap sucks 😀 I do js firmware whole life
Hi,
unfortunately we have also the problem with "ghost transactions". Some stations don't close her transactions. And after some time charging isn't possible because of too many "open" transactions. After i kill the transactions manually via web gui charging is possible again. An automatic closing feature would be great!
Question: Would a reboot of the steve server close this ghost transactions?
Regards Gero
Related to my experience it is very useful to regularly reboot stations.
I think it should be a very nice to have a feature for Steve to implement an "auto reboot" function.
In my opinion, Steve may offer a GUI to let user plan a global reboot (hard reset) of connected stations. Ideally we may be able to choose a period (every hour / day / week) and time. Obviously Steve may only reboot stations with a connector status "available" on each connector.( for some cases, reboot can fix problem related to transaction "never close" so Steve may not look at open transactions to choose concerned stations).
I hope my English is understandable ^^