-
Notifications
You must be signed in to change notification settings - Fork 118
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
Openevse shows GUI shows manual after sending DELETE override #654
Comments
what gui version do you have v1 ( old interface green one ) or v2 ( new interface, blue one ) ? ( firmware file ending by _gui-v1 or _gui-v2 ) |
V2 |
Can you post a screen ? I don't get it |
If you talk about the little tag on the bottom left of the status bar, it doesn't always means there's a manual override. If it is the default state, it will also display it is manual, if there's nothing else that control automatically the evse state. ( I could fix that and display somehting like "Default" ) If you want to check the claims/override go in monitoring/commands tab and you will see if there's one running. |
The strange thing is, I used to have the 3rd middle button looking like a robot, where I could choose to have openevse automaticly decide what to do. Using powershell gives me the following error: Browsing to the url http://192.168.1.8/override shows: |
as you can see in your Monitoring screenshot there's no "state" property set by "manual" so no manual override. Everything is allright. Are you sure you are not using the current dev build ? And you have set the /config/EVSE/ Default State to Active ? |
Also if robot icon appears, it means you have either some timers set or selfprod | ocpp enabled. Shaper is working in the backgrnd of all charge tasks, it won't activate alone the evse, but it will disable it if there's not enough power left in the powerwall. It is not really part of an automation but a safety |
I'm not using the dev build at the moment. Where do I set the defaut state? There is indeed no state propery set by manual in my monitoring, yet the display on my openevse unit shows manual override. |
I get it now. Disable the charger shows manual override on the display, Enabling the charger shows manual override on the display, Deleting manual override remove manual override on the display, but doesn't really do anything in the gui. It gives you the idea that manual override is still enabled. It would be better indeed if it shows something like 'Default' when the manual override is deleted. |
Default state is only on current build, but forget my question, I forgot default state is actually to Active. You will be able to set that on next release ( or current dev build ) for you display problem, perhaps it's just a bug with lcd. I got some frozen line on some other situations, like in #597 |
You should forget the manual override term, with V2 gui there's no such thing. UX has changed. If you use any property in an /override , not only "state" one, I think it display manual_override on the lcd, it also always report "manual_override: 1" on /status & mqtt. This property has no much sense now ( and should probably be deleted ). The complete /override should be fetched at version change. |
I understand now, thank you for the explanation! |
you're welcome. |
It might make sense, the UI still has to interact with the override as the front panel button will do the same as the V1 UI, IE toggle override on/off so we either need to change that behaviour or handle it in the UI. IMHO it should be in 'auto' mode by default even if there aren't any special features setup |
yes, I have changed this in current master. I was not a fan of the Auto button popping in/out of nowhere. Looks more consistant now, and keep the logic everywhere. |
OpenEVSE | 7.1.3
OpenEVSE Wifi | v4.2.2
Hello,
I'm trying to remove the manual mode by sending an powershell command to remove the manual mode. I can see on the screen that the manual mode dissapears, but the GUI still shows manual mode enabled. How can I remove the manual mode?
$response = Invoke-WebRequest -Uri 'http://192.168.1.8/override' -Method DELETE
The text was updated successfully, but these errors were encountered: