Add wakeup to OVMS vehicles

[stumbaumr]

Is your feature request related to a problem? Please describe.
Wakeup is still missing on the Smart EQ (vehicle 1)

[site  ] INFO 2025/03/17 12:14:17   vehicles:
[site  ] INFO 2025/03/17 12:14:17     vehicle 1: range ✓ finish ✓ status ✓ climate ✓ wakeup ✗
[site  ] INFO 2025/03/17 12:14:17     vehicle 2: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓

Describe the solution you'd like
There is a command in the OVMS shell wakeup... that wakes the CAN bus up...

me li xsq.v.bus.awake
xsq.v.bus.awake                          no

wakeup
Vehicle has been woken

me li xsq.v.bus.awake
xsq.v.bus.awake                          yes

Describe alternatives you've considered
Live without wakeup - don't know what it does anyway... just that it is missing ;-)

Additional context

[stumbaumr]

....just one more thing...
CC @PanNwt und @Tailer67

[andig]

There is a command in the OVMS shell wakeup

We'd need an api call

[caveman99]

per https://docs.openvehicles.com/en/latest/userguide/commands.html#europe-dexters-web-de you can send any command to the module for execution, if it is provisioned on dexters-web, which most of the european cars are. - in this case the command to send would be 'wakeup'

[caveman99]

@andig i can reliably wake up the car for charging in the middle of the night by including this call "wakeup" in a messaging script. I use the local Wifi API but the call is the same over the server. Problem is that only dexter's server has this extended API. Maybe make the URL configurable so the user can select which route to go. In the end both are vanilla REST Get calls.

local: http://carname.local/api/execute?apikey=modulepassword&command=wakeup
server: https://dexters-web.de/api/ovms/cmd?fn.vehicleid=carname&fn.carpass=serverpassword&fn.cmd=wakeup

with carname being the vehicleid. serverpassword and modulepassword CAN be the same but don't have to be the same! The currently configured API password in the integration is the serverpassword.

(Note: the documentation for OVMS on https://docs.openvehicles.com/en/latest/userguide/commands.html#europe-dexters-web-de is wrong, the first & needs to be a ? like in any GET URL)

[dexterbg]

Correct, thanks for the fix!

[andig]

Happy to take a PR. Dexter is recognizable via the server name.

[caveman99]

@dexterbg can i leave out the vehicle password if i have a valid cookie auth from the standard REST API or are the two API's independent of each other?

[stumbaumr]

Asked Dexter if he could provide something like that...

[dexterbg]

See the user guide on remote command execution:
https://docs.openvehicles.com/en/latest/userguide/commands.html

As the vehicle to be controlled will normally be in the home Wifi network (?), I'd suggest doing a direct command call via HTTP or SSH:

• https://docs.openvehicles.com/en/latest/userguide/commands.html#module-http-server
• https://docs.openvehicles.com/en/latest/userguide/commands.html#module-ssh-server

Regards,
Michael

[stumbaumr]

Nope, the WiFi of my OVMS is only active for two hours after a reboot - it is just too unstable to have cellular active and then also WiFi running all the time - which is the recommendation in the Smart Emotion Forum.
Is there no possibility to send the wakeup command via https://dexters-web.de/f/simpleclient.htm ???

[dexterbg]

I've got Wifi & cellular active all the time without any issues. I've heard about this advice originating at the Smart forum. No other OVMS users ever had issues with runnig Wifi & cellular in parallel, that's what the OVMS framework was desiged to do. Maybe the Smart forum OP came to this conclusion based on some misinterpretation, possibly having the module at the edge of the router range without actually checking the signal strength, and without taking tuning the signal thresholds or adding a repeater into account. Or maybe the OP was running the beta test firmware a couple of weeks ago, which had a bug with network transitions.

Nevertheless, the available APIs are all described in the manual. Command execution via the V2 server's builtin HTTP API is not yet possible, but you've got plenty of other options, e.g. using the V2/MP perl or nodejs client, or (if you're on my server) use the HTTP API I provide via the web frontend, or use the MQTT connection.

[Tailer67]

I have Wi-Fi and mobile network enabled in the OVMS without any problems. EVCC always correctly recognizes the vehicle at the wallbox, and charging runs smoothly.

OVMS has adjustable update intervals for updating the values ​​on the V2 server (default: every 60 seconds when connected, every 600 seconds when idle). The evcc update interval should be configured accordingly.

I don't know why we would need a wake-up.

[VW eUp with OVMS Firmware: 3.3.003-662-gaa28a289]

[stumbaumr]

Just yesterday after plugging in the Smart EQ would not charge. Normally I would go out again and unplug-plugin again.
But a simple wakeup in the OVMS shell did the trick... so yes, having wakeup sometimes would be nice.

[stumbaumr]

Or maybe the OP was running the beta test firmware a couple of weeks ago, which had a bug with network transitions.
Smart EQ OVMS users are dirty and edge users by definition, as longs as EQ integration was still going on.

I am deactivating the power management two hour WiFi uptime after reboot to see if it is stable by now...