-
Notifications
You must be signed in to change notification settings - Fork 89
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
Unable to lock / unlock / start vehicle #937
Comments
None of those logs are related to service calls. Could you enable debug and try lock the car? Provide those logs. |
Hyundai_Integration_debug_Log.txt This is the debug log when sending a lock request. Thanks. Let me paste it here. I didn't think an attachment might not be trusted which makes sense. 2024-09-26 07:23:14.563 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None) During handling of the above exception, another exception occurred: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Any update on this by chance? My Vehicle goes unavailable pretty much daily. I just had to reload the integration as it was 19 hours showing unavailable. Thanks |
When "off" would you prefer temp to show 0 or unavailable? |
I do like to see off but it appears the API does not? I am fine with off but the message seems to indicate it is invalid so a 0 will work is we only have 0 or unavailable. Is this what is causing me all the trouble? |
Right now home assistant is setup as a temp value. Which can only be a number. I can shift it to text but then users won't be able to select units. So thinking changing the api response of off to a number. |
I see. if that gets things working that would be great. I don't want to make it so users can't do something. I'm sure I do not understand this appropriately and you will know the best route to take. Thank you again for your work on this. |
Please check Services, Known Bug / Issues and Troubleshooting over here first: https://github.com/fuatakgun/kia_uvo/blob/master/README.md
Region and Brand of car
USA Hyundai
Version of the integration
2.26.7
Describe the bug
I have been trying for a week to get my car to lock or unlock or start via HA. I can use the app, I can use the web. I can log out of the app and log back in just fine.
The app returns this when I try and do a lock / unlock from HA so the app is sending me the result.
"Remote Door Unlock unsuccessful. Please ensure your vehicle is in a good coverage area."
It is in a good area as the app and the website work just fine.
Thanks and great work on this. I love being able to have the integration in HA so much.
Debug logs if an error occurred
These appear to be the relevant logs...
2024-09-25 16:41:04.361 DEBUG (SyncWorker_6) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - Get Vehicle Location {'errorSubCode': 'HT_504', 'systemName': 'HATA', 'functionName': 'findMyCar', 'errorSubMessage': 'HATA findMyCar service failed while performing the operation FindMyCar', 'errorMessage': "We're sorry, but we could not complete your request. Please try again later.", 'errorCode': 504, 'serviceName': 'FindMyCar'}
2024-09-25 16:41:04.361 WARNING (SyncWorker_6) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - Unable to get vehicle location: {'errorSubCode': 'HT_504', 'systemName': 'HATA', 'functionName': 'findMyCar', 'errorSubMessage': 'HATA findMyCar service failed while performing the operation FindMyCar', 'errorMessage': "We're sorry, but we could not complete your request. Please try again later.", 'errorCode': 504, 'serviceName': 'FindMyCar'}
2024-09-25 16:41:04.361 DEBUG (SyncWorker_6) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - Get Vehicle Location result is None
2024-09-25 16:41:04.362 DEBUG (SyncWorker_6) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - update_vehicle_with_cached_state Location fallback {'coord': {'alt': -112.214208, 'lon': -redacted, 'type': 0.0, 'lat': redacted}}
2024-09-25 16:41:04.363 DEBUG (SyncWorker_6) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] hyundai_kia_connect_api - SOC Levels couldn't be found. May not be an EV.
2024-09-25 16:41:04.364 DEBUG (SyncWorker_6) [hyundai_kia_connect_api.HyundaiBlueLinkAPIUSA] _update_vehicle_properties filled_trips: []
2024-09-25 16:41:04.365 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 121.766 seconds (success: True)
2024-09-25 16:41:04.411 ERROR (MainThread) [homeassistant.components.sensor] Error adding entity sensor.2024_santa_fe_hybrid_set_temperature for domain sensor with platform kia_uvo
-- I also see this in the log
ValueError: Sensor sensor.2024_santa_fe_hybrid_set_temperature has device class 'temperature', state class 'None' unit '°F' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'OFF' (<class 'str'>)
To Reproduce
Try to lock or unlock or climate start the vehicle
Expected behavior
lock / unlock / start vehicle
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
hybrid 2024 santa fe. I removed my old santa fe and recently purchased this new one.
The text was updated successfully, but these errors were encountered: