Data Broadcast & Widgets Keeps connection open

[Alco4998]

Issue

When enabling the Enable data broadcast to Other Apps or Creating an OVMS Widget
a connection remains between the vehicle and the Mobile

Background

When working on my unreleased version for my Ioniq 38Kwh, to mitigate excessive 12V Drain I look to see if there are any connections present.
Being a fan of KWGT have the External Data Broadcast on so i can have a custom widget for my phone.

While debugging the remaining drain i found the bug above.

Considerations

If this is expected behavior then would be an associated warning. (Inside the App).
If this was expected maybe a network friendly alternative would be to store the connection and reduce the frequency of polling.

Questions

Is this Intentional?
Should this be resolve on Vehicle's side or the Mobile's side?

[dexterbg]

The data broadcast option does not imply or require the connection service, but doesn't make much sense without for most cases.

On widget creation, the "foreground" service is enabled automatically. This was intended behaviour when there was only the SOC widget, as that doesn't make any sense without a persistent data connection. You're right, at least with the new command widget, this should no longer be done without user info & consent.

The App's foreground service also does not poll, it's an open TCP channel to the server waiting for messages from the car and ready to send commands. But you're welcome to implement an option for periodic short server connects alternatively to the persistent channel. A starting point could be the WorkManager job scheduling framework.

Excessive 12V drain on the vehicle side isn't normally caused by data updates sent to the server, but by the OBD polling keeping ECUs alive when the car would normally put them to sleep. If you need to query PIDs to determine if the car is awake: some ECUs/PIDs normally can be polled without keeping the ECUs alive, possibly needing a reduced poll frequency.

A better option for determining the vehicle state is to listen for process data frames that do not require polling, if the Ioniq sends any. As a fallback if there is no other way, you can monitor the 12V level. The vehicle framework emits events vehicle.aux.12v.* derived from the 12V level. Be aware this may need a 12V calibration on the user side.

Regards,
Michael