-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ram Trucks _authApiKey and _authUrl update #76
Comments
yes thx very good info 👍 but im sorry i cannot update it right now. development is on hold until i find new motivation to work on it and im driving my fiat again. |
@Bart738 You have yours working? I forked and I see it get a 200 when connecting, but don't see it returning any vehicles. [08:11:21 DBG] { Can you point me at the API docs? I can only find the location tracking one. |
Yes, making only the change above everything works. Prior to making the change, everything worked except for the advance commands requiring the PIN. |
Thanks, I just re-purchased the add on, so it might take time to update to show the vehicle. |
Were you able to get this to work @Combatchuck ? I tried your repo in Home Assistant but it's still not pulling any of my vehicles. I get the same as you posted above: "Vehicles": [] Also, when I add your repo url, the url in the manage add-on repositories screen still says https://github.com/wubbl0rz/FiatChamp |
I realized that my 19 was not available via that api. |
My 20 may not be available either. I can start my truck through homebridge and the homekit integration but I can't lock it. |
connect.ramtrucks.com shows my truck on the top, but if I want to view it, it redirects me to www.mopar.com |
I was able to pull this info during testing on my RAM, would we be able to update FiatClient.cs with the following info for RAM?
The text was updated successfully, but these errors were encountered: