You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently picked my personal project up and have been using this library a lot more. I have managed to aggregate every other piece of data linking to the 13 cars on my holding account. My one issue relates to the one Model X we have in the fleet. I was wondering if anyone had had a chance to pull the vehicle config for a Model X and had noticed any different variables in the JSON response? The two tells for me seem to be the
vehicle_config[rear_seat_type] == (returns an 8 for my Model X 5 seat)
vehicle_config[third_row_seats] == (none)
variables.
My issue is that, I have no problem differentiating between a 5 seat and a 6&7 seat due to the third row seat variable, however no method of automatically differentiating between 6 and 7 seat models.
Has anyone looked into this before? or would anyone be able to pull the vehicle_config for a 6 or 7 seat Mx and compare those two variables?
Amazing library Mark! - Thanks
J
The text was updated successfully, but these errors were encountered:
I recently picked my personal project up and have been using this library a lot more. I have managed to aggregate every other piece of data linking to the 13 cars on my holding account. My one issue relates to the one Model X we have in the fleet. I was wondering if anyone had had a chance to pull the vehicle config for a Model X and had noticed any different variables in the JSON response? The two tells for me seem to be the
variables.
My issue is that, I have no problem differentiating between a 5 seat and a 6&7 seat due to the third row seat variable, however no method of automatically differentiating between 6 and 7 seat models.
Has anyone looked into this before? or would anyone be able to pull the vehicle_config for a 6 or 7 seat Mx and compare those two variables?
Amazing library Mark! - Thanks
J
The text was updated successfully, but these errors were encountered: