That requires either an online connection to a datacenter somewhere or something that (at present time) is a fairly substantial on-board computing system, and those are things that I think are worth trying to avoid for tasks like adjusting the HVAC in a Honda.
Maybe some day.
Right now, when we do have substantial on-board computing systems, they're trying to drive the car -- not change the temperature. Adding in an additional computational timeslot for LLM voice commands seems both foolhardy and expensive.
Meanwhile: Broader dictionaries and static flows with greater breadth for voice recognition? We can do that right now.
(We can even use LLMs to help generate the static flows, along with people to evaluate and test them. Once implemented, they become cheap to run.
This is in-keeping with a fairly common theme here on HN: Don't use the bot to process the data. Instead, use the bot to write the data processor.)