Regarding connection issue between kuksa databroker and databroker python sdk

[rahulallure]

Hello all,
I am working on transmitting data between automotive API and kuksa databroker and kuksa databroker client(python sdk). Can we use grpc between automotive API and databroker and websocket between kuksa databroker and kuksa databroker client(python sdk)? I tried using websocket between databroker and kuksa client, connection is established, but Vehicle Speed data is still null, though data is being transferred from AAPI and databroker. May I know how to resolve this?

[SebastianSchildt]

A small explanation/sketch of your setup would help to understand better what you are trying to achieve

Generally:

Can we use grpc between automotive API and databroker and websocket between kuksa databroker and kuksa databroker client(python sdk)?

That "should" work, but we recommend using GRPC with Python SDK as well (that would be with the examples https://github.com/eclipse-kuksa/kuksa-python-sdk/blob/main/docs/examples/sync-grpc.md or https://github.com/eclipse-kuksa/kuksa-python-sdk/blob/main/docs/examples/async-grpc.md .
The websocket support in the threaded API is much slower, and is there for historic reason when an earlier version fo KUKSA only supported websockets. However, it should basically work. (For example we often see the websocket part used when people are building GUIs for VSS with HTML5/Javascript.

How do you know "data is being transferred from AAPI and databroker", can you see the data if you acutally subscribe it with databroker-cli for example? In that case it should also be available in VISS.

Likewise, if you use databroker-cli to publish Vehicle.Speed can you see it on your Python side?