reproviding the remote service history #383
-
Hi, thanks for your work on new api. i am using your work, to get data into the smarthome "IP-Symcon" (a solution in germany) i have a question: with the new api, the old call it disfunctional - as expected. in the vehicle-data is a item isRemoteHistorySupported an in the original BMW-app there ist a item "Remote-Verlauf" (in Germany), would be call "remote history" - in the App, i can see the data. Thanks a lot |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 6 replies
-
Hi demel, thats actually on my todo list, however I am not fully certain how I want to implement it (i.e. if & where to store it on a vehicle object). The URL called is basically With the latter, you could implement a workaround like blow (not tested ;) ): for vehicle in account.vehicles:
account.send_request(
BASE_URL + "/eadrax-vrccs/v2/presentation/remote-history/{vin}".format(server=account.server_url, vin=vehicle.vin),
brand=vehicle.brand
) |
Beta Was this translation helpful? Give feedback.
-
Hi rikoe, thanks a lot, it works. |
Beta Was this translation helpful? Give feedback.
-
Hi rikoe, your Information was a good help. in the old api, there where information about the battery (battery_size_max, socMax)an some efficiency hint's and info about the last trips. any additional information would be a great help |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, I haven't seen any other API endpoints that have socMax available. There was a discussion that a login against the old API's On my tries I at least was not able to get any data back (403 forbidden response from server). |
Beta Was this translation helpful? Give feedback.
-
Yes, I have heard that regarding charging/just plugged in as well. If your car supports all that fancy new stuff and you have an rooted android phone lying around, I can help setting you up to be able to to MITM against the current app again. |
Beta Was this translation helpful? Give feedback.
Hi demel,
thats actually on my todo list, however I am not fully certain how I want to implement it (i.e. if & where to store it on a vehicle object).
I'm currently not quite happy how some attributes are accessed from the
vehicle
, some fromvehicle status
(or directly from the vehicle), etc., so I am thinking about taking a step back and fully-designing the library.The URL called is basically
/eadrax-vrccs/v2/presentation/remote-history/{vin}
. How are you accessing the library?Via CLI or from Python?
With the latter, you could implement a workaround like blow (not tested ;) ):