๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Myron ๐Ÿ“โšก๏ธ
@CyberAmped
Healthcare entrepreneur | Builder | Failure Isn't an Option | Tesla & Energy owner | Autonomy advocate | Community Driven โšก๏ธ Electrified Together
๊ฐ€์ž… April 2009
761 ํŒ”๋กœ์ž‰ ์ค‘    532 ํŒฌ
Hey @Tesla, two things immediately come to mind that would make the Fleet API even more powerful. Expose the active Driver Profile. This would allow applications to accurately log who was in control of the vehicle, improve fleet auditing and compliance, personalize automations, and provide much richer reporting for shared vehicles. Support multiple waypoints in the Route Planner API. Many commercial and enterprise use cases require multi-stop routing, including healthcare transportation, field service, inspections, deliveries, and future autonomous operations. Sending one destination at a time limits whatโ€™s possible. Both additions would significantly expand whatโ€™s possible for developers building on the Tesla ecosystem.
๋” ๋ณด๊ธฐ