-
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
No vehicles returned - RAM #56
Comments
I am having the same issue. Jeep Grand Cherokee, works on both Connect app and Jeep site but as op says there's nothing to control my vehicle, it links to the Mopar site for all the start/lock/etc. commands. Log below. s6-rc: info: service legacy-cont-init: starting |
I'm having the same issue with Jeep, I'm getting the following [10:00:22 DBG] { Any Help? |
Still seeing it on my 2019 Ram 1500 as well. |
hmm something tells me this is going to take longer than we thought! |
I also have the same issue with Jeep USA. [13:08:10 DBG] { |
Adding myself to this list. Get the same issue with my Jeep Grand Cherokee as everyone above. Says it's connecting successfully to both the Fiat server and to MQTT but I get no devices or entities in the MQTTBroker FiatChamp Debug Log: s6-rc: info: service fix-attrs: starting MQTTBroker Log: 2024-02-26 01:10:53: New client connected from 172.30.33.2:57858 as FiatChamp (p2, c1, k15, u'mosquitto-admin'). |
Same issue for me with Jeep. |
Trying to get this up and running with a RAM 1500.
No errors in the debug log, but this does show up
I can logon to https://connect.ramtrucks.com/ and see the commands I've issued from the app, however there is nothing on that site that allows me to control my truck, outside of setting up a PIN for alexa/google.
The text was updated successfully, but these errors were encountered: