There is an issue with Charge Mode change in both the original firmware and 3.1.003 OTA firmware. When changing from Standard mode to any other charge mode the car will change to the selected mode but the change is apparently not confirmed back to the server. The app never reflects the change and still shows Standard mode which results in no way to set the car back to Standard mode since the app doesn't send a duplicate Standard mode request. This has been tested with both the IOS app and the Android app.
See this issue:
https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/39
This will be addressed in firmware 3.1.004 (not yet released).
I had seen that issue listed but was not seeing that type of problem. A friend and I have since tested this on his Tesla Roadster 2.5 and on my TR 1.5. The problem still occurs using the latest build which has the timing fix.
The cars are reliably and consistently switching to range mode, performance mode or storage mode as selected from the app. The issue is that the app never reflects this change and since the app is still indicating that the car is in standard mode it will not send a standard mode change request to the car. Thus there is no way to set the car back to standard mode remotely.
Can you try 3.1.004 (main), or 3.1.003-52-g8cde1a4 (edge), or later?
This is a little tricky (with the CAN bus message being different on v1.x vs v2.x cars). We think we've fixed it, but need confirmation.
New OTA works perfectly on my 2.5 and friends 1.5.
J
Thanks for the feedback!