Enhancement request: HTTP API support for PUT /api/feature

[ankohanse]

The OVMS HTTP api is great to be able to display vehicle data in other applications, in my case Home Assistant. Especially when you want to combine car data with information from wall-charger and house power-draw status.

I have a use-case to be able to set feature # 10 - 'sufficient SOC':
We often don't use our Nissan Leaf for several days but never know when we will use it next. Consequently we prefer to charge it only to 80%. But sometimes we know we have a longer trip ahead and would like to charge to 100%. I can influence this behavior in the OVMS app via the 'features' screen.

I would like my wife to also be able so influence suficient SOC before a charging session. But the OVMS app way is not very user friendly and can't display related information about the charger. It would be much nicer to influence via a dedicated button in Home Assistant.

Currently PUT /api/feature is listed in the HTTP documentation as 'not implemented'.
Are there plans to implement this in the near future? How can I upvote this?

[dexterbg]

There are currently no plans I know of to implement these HTTP API methods. The draft is really old, dating back to early V2, and there were soon after better options.

The existing remote command utilities can easily be integrated into any home automation system, and are much more versatile.

See: https://docs.openvehicles.com/en/latest/userguide/commands.html

[ankohanse]

I understand your reasoning...
However, most of the alternative access methods (ssh, mqqt) only can issue shell commands into OVMS. And I do not see a shell command that lists or sets one of the features (i.e. #10 Sufficient SOC). Or am I overlooking something?

Only alternative method that seems feasible is to go via the v2 MP protocols with commands C1 (list features) and C2 (set feature). This script seems to work to set sufficient SOC to 80:
./cmd.pl 2 10,80

But perl scripts are a huge pain to call from Home Assistant when they depend on dependency modules. Am now looking into creating a Home Assistant Addon based on the v2 MP NodeJs script.

[markwj]

The whole 'features' (and 'parameters') thing is from OVMS v2 where there was very little flash space and config storage (only room for a dozen or so simple features and parameters). This has been completely replaced in v3 by the more sophisticated config system.

There is still some very basic mapping of v2 features to v3 config:

• 8 -> MyConfig.GetParamValue("vehicle", "stream", "0");
• 9 -> MyConfig.GetParamValue("vehicle", "minsoc", "0");
• 14 -> MyConfig.GetParamValue("vehicle", "carbits", "0");
• 15 -> MyConfig.GetParamValue("vehicle", "canwrite", "0");

and perhaps some custom ones on a per-vehicle basis (look in the vehicle source file and you will see GetFeature() with the mapping). But generally deprecated and can always be set directly with 'config set ...'.

[ankohanse]

Great, you learn something every day!
Yes, I indeed found support in the Nissan Leaf code for additional mappings including for 'sufficient SOC'

So that means I should be able run an SSH command :
ssh ovms@myvehicle.local config set xnl suffsoc myvalue