Thanks
@Mr Blue Sky and
@Filippo
Year ago I posted if someone was gotten any further:
Now that Google has gone in the IOT path, it would be nice to have a wrapper or library for Android Auto, as we are not longer only restricted to Media in Cars OS https://android-developers.googleblog.com/2023/04/expanding-options-for-building-apps-for-cars.html...
www.b4x.com
It could be great in how to interact with slave devices, back in that time Google had released that IOT things were considered as part of the ecosystem of Android Auto. I never got any further with my lack of knowledge. As I did understood by that time, the car actuates as a slave App from the phone, that requiered a special layout with the restrictions that apply for.
I faced two changes by that time:
1.- How to interact with the car "keyboard", in this case the rotary knob
2.- My App is for garage remote opening, so it was quite useful to try to give commands from the car device rather than unlocking our phones to try to interact with the garage controler. In this case what I faced, was I was not quite sure how the Location works, because in my app location is only while app is in used and is in foreground. I needed the location as there is a "safety distance" between the controler and the device to be actuated. I never found and answer if the app was considered in "Foreground" when the slave has the app working.
I´ll bookmark this post as it has been the most useful post regarding slave devices.
I think this is something very needed (Also for CarPlay) as more devices functionalities are driven ny slave devices (cars, watches, etc).