audi_connect_ha
audi_connect_ha copied to clipboard
All entities are listed as none.*
Per screenshot, all of the entities this integration created are called none.[something] Seems like the documentation suggests they should be something like, "sensor.audi_sq7_oil_level" vs "sensor.none_oil_level"
Is this WAI and I should manually rename the entities or an indication something is off?

Use the official audi app to (re)set you car name. Then remove and add the integration.
No change. I went into the MyAudi App (Android), clicked the pen in the upper right and changed it from "Your Car" to "A6", exited the app, deleted the integration via HA, added the integration back and then restarted Home Assistant. I'm still seeing the exact same thing as above.
Also, I have another thread open, I can not figure out any way to issue the lock/unlock command. I've tried calling the service with my pin in dev tools and via a lovelace button card to no effect. No idea what's wrong here.
Try remove, restart, add
Still no. I went as far as to delete the custom config folder/HACS install as well, restarted Home Assistant, copied the audiconnect files from the audi_connect_ha-login_app-v4_6/custom_components/audiconnect folder from the zip of github into the config/custom_components/audiconnect folder on HA, restarted again, and then installed the integration from configuration...
Same as before. All sensors are "none" and nothing I do makes the car lock/unlock.
On Thu, Feb 24, 2022 at 1:51 PM René Klomp @.***> wrote:
Try remove, restart, add
— Reply to this email directly, view it on GitHub https://github.com/arjenvrh/audi_connect_ha/issues/126#issuecomment-1050157335, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB74P7DPLNRBYBEUES4LVDLU4Z42JANCNFSM5PE573EQ . You are receiving this because you authored the thread.Message ID: @.***>
-- Lee Milstein | @.*** | 917-509-9237
Than I dont know. Changing the name in the Audi app solved it for me.
I had been using the wrong pin, which is now fixed, but still having this issue. Anyone know what else I could try?
This issue is stale because it has been open for 60 days with no activity. Are you still experiencing this issue?
Issue has been open for 2 years with no activity. API has changed many times. Closing this issue. If you have any persistent issues from this, please submit a new issue.