Does kuksa-can-provider support Databroker v2 Actuate(...) flow

[dorelad]

Hi Kuksa team 👋

I'm using kuksa-can-provider together with the new kuksa-databroker (v2), along with a custom CLI client that uses the v2 gRPC API.
I'm currently trying to implement actuator control — for example:
'actuate Vehicle.Body.Trunk.Rear.IsOpen true'

This sends a request via the new Actuate(...) method on the Databroker.

From my understanding of how this flow should work in v2:

• Actuate(...) requires a provider to be registered for the target VSS path
• A provider must register via the OpenProviderStream(...) bidirectional stream (specifically sending ProvideActuationRequest request on startup)
• Without a provider, the databroker returns to the client an error such as:
  "Error actuating: status: Unavailable, message: "Provider for vss_id 74 does not exist", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Wed, 16 Jul 2025 07:52:10 GMT", "content-length": "0"} }"

When I run the dbc_feeder.py with the following command:
python3 dbcfeeder.py --server-type kuksa_databroker --dbcfile Model3CAN.dbc --mapping mapping/vss_4.0/vss_dbc.json --canport vcan0 --val2dbc --use-socketcan

From my understanding and debugging the can-provider:

• It subscribes to actuator targets via Subscribe(...)
• But it does not register as a provider using OpenProviderStream(...)
• And it does not handle incoming ActuateRequests

As a result, the actuator paths are mapped and appear in the VSS tree, but cannot be controlled via the Actuate(...) API.

Question
Does the current version of kuksa-can-provider support Databroker v2 — specifically for handling actuator control via the Actuate(...) API?
If so, how should a user configure it to register as a provider using OpenProviderStream?
If not, is this on the roadmap?

Thanks again for your work on Kuksa — it's a great project! 🙏

[lukasmittag]

Hey @dorelad, no the kuksa-can-provider currently does not support v2 per sé. Thats because it heavily relies on the kuksa-python-sdk. It is somehow on our roadmap to update this but currently the core team is occupied with a lot of non kuksa related topics and we act in a state of "maintenance only". So I would see no not in the near future (>3 months). However if you are interested in the project and want to update the python-sdk yourself (it has already support for publish and subscribe of kuksa.val.v2) we would happily review and test your code and hopefully get it in a mergable state :)