Lock Type Error

[Trodfoot]

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 Canada / Sante Fe Version of the integration v2.5.8

Describe the bug A clear and concise description of what the bug is. First bug shows up on startup, right after the upgrade that just happened. I only installed the addon last night and it may have been there. I didn't log as everything went ok.

Second error shows up when It showed I had not locked my doors when I had gotten back. I had but thought what the heck and hit the unlock to lock it. Debug logs if an error occurred

2023-02-01 17:33:05.758 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: kia_uvo

2023-02-01 17:36:07.335 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139973520050208] HyundaiKiaConnectLock.async_unlock() got an unexpected keyword argument 'entity_id' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 200, in handle_call_service await hass.services.async_call( File "/usr/src/homeassistant/homeassistant/core.py", line 1787, in async_call task.result() File "/usr/src/homeassistant/homeassistant/core.py", line 1824, in _execute_service await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)( File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service await service.entity_service_call( File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 681, in entity_service_call future.result() # pop exception if have File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 968, in async_request_call await coro File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 721, in _handle_entity_call await result File "/usr/src/homeassistant/homeassistant/components/lock/init.py", line 105, in _async_unlock await entity.async_unlock(**service_call.data) TypeError: HyundaiKiaConnectLock.async_unlock() got an unexpected keyword argument 'entity_id'

' Logger: homeassistant.components.websocket_api.http.connection Source: components/lock/init.py:105 Integration: Home Assistant WebSocket API (documentation, issues) First occurred: 6:50:17 PM (1 occurrences) Last logged: 6:50:17 PM

[140341996844080] HyundaiKiaConnectLock.async_unlock() got an unexpected keyword argument 'entity_id' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 200, in handle_call_service await hass.services.async_call( File "/usr/src/homeassistant/homeassistant/core.py", line 1787, in async_call task.result() File "/usr/src/homeassistant/homeassistant/core.py", line 1824, in _execute_service await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)( File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service await service.entity_service_call( File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 681, in entity_service_call future.result() # pop exception if have File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 968, in async_request_call await coro File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 721, in _handle_entity_call await result File "/usr/src/homeassistant/homeassistant/components/lock/init.py", line 105, in _async_unlock await entity.async_unlock(**service_call.data) TypeError: HyundaiKiaConnectLock.async_unlock() got an unexpected keyword argument 'entity_id'

To Reproduce

Expected behavior Should have locked the doors Screenshots If applicable, add screenshots to help explain your problem.

Additional context Also now it shows my engine running, doors unlocked, front and back heaters on but it is parked in the driveway off. Hope this helps

[cdnninja]

What version of HACS?

[Trodfoot]

Sorry about that....

1.30.1

On Wed, Feb 1, 2023, 8:07 p.m. cdnninja @.***> wrote:

What version of HACS?

— Reply to this email directly, view it on GitHub https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/584#issuecomment-1413087493, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBLK6CRYVR6T4IXOGRSHTWVMQHVANCNFSM6AAAAAAUOODMSM . You are receiving this because you authored the thread.Message ID: @.***>

[pos-ei-don]

Same here...

[cdnninja]

What version of home assistant?

[pos-ei-don]

2023.2.0

[Trodfoot]

Home Assistant 2023.2.0 Supervisor 2023.01.1 Operating System 9.5 Frontend 20230201.0 - latest HACS Version: 1.30.1

For shits and giggles I went to get you the Version number for your integration and the Service Info shows no Version info just Integration by someone's name So I go to HACS integrations and it shows v2.5.8 for Kia Uvo / Hyundai Bluelink interrogation And On integration. HA Kia/Hyundai. V1.7.1

I am enclosing the debug info from the log since I turned it on and did a restart. Hope this helps, it has me already... the info is showing my battery is never higher than 58 percent and now only 50 percent.. gotta call the dealer. Also I renamed the vehicle to Sante Fe so on the dashboard it says Sante Fe Doors Unlocked. Instead of Hercules(which I must have given it when I first got it) because. Hercules Doors Unlocked meant nothing to my girlfriend. You might point this out in the install so others don't have to change it to understand it like I did. When I did this I had to remove the info from the dashboard and put it back, as of course it was looking for Sante Fe and getting Hercules. Just to let you guys know.

2023-02-02 09:14:57.491 DEBUG (SyncWorker_5)

[hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Get Vehicles Response {"responseHeader":{"responseCode":0,"responseDesc":"Success"},"result":{"vehicles":[{"vehicleId":"Gib29YMYLkq/yCm4z3PIRw==","nickName":"Hercules","modelCode":"SA4SAA24B200","modelName":"SANTA FE","modelYear":"2020","fuelKindCode":"G","trim":"Ultimate -","engine":"","exteriorColor":"ST2","dtcCount":0,"subscriptionStatus":"A","subscriptionEndDate":"20230630","mileageForNextService":5864.9,"daysForNextService":"20230719","overviewMessage":"","defaultVehicle":true,"enrollmentStatus":"4","genType":"G1","valetParkingModeOn":1,"vin":"5NMS5CAAXLH148695"}]}}

2023-02-02 09:14:58.606 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20230202132753', 'airCtrlOn': False, 'engine': False, 'doorLock': True, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '00H', 'unit': 0}, 'defrost': False, 'lowFuelLight': False, 'acc': False, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 0, 'sideBackWindowHeat': 0, 'dte': {'value': 184.0, 'unit': 1}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 50, 'sjbDeliveryMode': 1, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': False, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'engineRuntime': {}}}}

2023-02-02 09:14:58.607 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Old Vehicle Last Updated: None

2023-02-02 09:14:58.607 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - last_updated_at - before 20230202132753

2023-02-02 09:14:58.607 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - last_updated_at - after 2023-02-02 13:27:53+00:00

2023-02-02 09:14:58.607 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Current Vehicle Last Updated: 2023-02-02 13:27:53+00:00

2023-02-02 09:14:59.171 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 11739.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20230119', 'imatServiceOdometer': 17739.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20230719', 'currentOdometer': 11874.1, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 6000.0, 'serviceDaysDuration': 180, 'serviceMonthsThreshold': 6}}}

2023-02-02 09:14:59.741 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Received Pin validation response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'pAuth': 'QFZLgVfgZJLLKyRtBlAOMIDsKgYRvHKc'}}

2023-02-02 09:15:29.647 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Get Vehicle Location {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'head': 176, 'coord': {'lat': 50.06870555, 'lon': -110.78118333333333, 'alt': 748.0, 'type': 0}, 'accuracy': {'hdop': 6, 'pdop': 11}, 'time': '20230202132728', 'speed': {'value': 0, 'unit': 0}}}

2023-02-02 09:15:30.062 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 33.958 seconds (success: True)

2023-02-02 09:15:30.113 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.VehicleManager] hyundai_kia_connect_api - Time differential in seconds: 10057.113735

2023-02-02 09:15:30.691 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20230202132753', 'airCtrlOn': False, 'engine': False, 'doorLock': True, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '00H', 'unit': 0}, 'defrost': False, 'lowFuelLight': False, 'acc': False, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 0, 'sideBackWindowHeat': 0, 'dte': {'value': 184.0, 'unit': 1}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 50, 'sjbDeliveryMode': 1, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': False, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'engineRuntime': {}}}}

2023-02-02 09:15:30.692 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Old Vehicle Last Updated: 2023-02-02 13:27:53+00:00

2023-02-02 09:15:30.692 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - last_updated_at - before 20230202132753

2023-02-02 09:15:30.692 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - last_updated_at - after 2023-02-02 13:27:53+00:00

2023-02-02 09:15:30.692 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Current Vehicle Last Updated: 2023-02-02 13:27:53+00:00

2023-02-02 09:15:31.176 DEBUG (SyncWorker_1) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 11739.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20230119', 'imatServiceOdometer': 17739.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20230719', 'currentOdometer': 11874.1, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 6000.0, 'serviceDaysDuration': 180, 'serviceMonthsThreshold': 6}}}

2023-02-02 09:15:31.372 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 1.267 seconds (success: True)

[cdnninja]

Are you saying it is working now?

Also the 1.7.1 version is another integration not this one. Two Kia Hyundai integrations exist. The other is a fork of this one.

[Trodfoot]

Yes it is. I can not understand what made it work but I am not looking a gift horse in the mouth. Oh thanks for the heads up that there was a second integration. Yours was working before I removed that one. So I do not believe it was the problem.

The door unlock/lock is not working. I still get this for both lock and unlock.

Logger: homeassistant.components.websocket_api.http.connection Source: components/lock/init.py:105 Integration: Home Assistant WebSocket API (documentation, issues) First occurred: 2:20:55 PM (2 occurrences) Last logged: 2:33:29 PM

[140581516003648] HyundaiKiaConnectLock.async_unlock() got an unexpected keyword argument 'entity_id' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 200, in handle_call_service await hass.services.async_call( File "/usr/src/homeassistant/homeassistant/core.py", line 1787, in async_call task.result() File "/usr/src/homeassistant/homeassistant/core.py", line 1824, in _execute_service await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)( File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service await service.entity_service_call( File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 681, in entity_service_call future.result() # pop exception if have File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 968, in async_request_call await coro File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 721, in _handle_entity_call await result File "/usr/src/homeassistant/homeassistant/components/lock/init.py", line 105, in _async_unlock await entity.async_unlock(**service_call.data) TypeError: HyundaiKiaConnectLock.async_unlock() got an unexpected keyword argument 'entity_id'

On Thu, Feb 2, 2023, 1:23 p.m. cdnninja @.***> wrote:

Are you saying it is working now?

Also the 1.7.1 version is another integration not this one. Two Kia Hyundai integrations exist. The other is a fork of this one.

— Reply to this email directly, view it on GitHub https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/584#issuecomment-1414328511, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBLK27ZEMSDCWDKLLKB7TWVQJUBANCNFSM6AAAAAAUOODMSM . You are receiving this because you authored the thread.Message ID: @.***>

[cdnninja]

For some reason it looks like your call is passing an argument. Are using the dashboard or calling the service via an automation? I see how to adjust this and will test it doesn't break anything for me but I don't understand what is different on your end.

[cdnninja]

Could you try go into hacs and "Redownload" and when offered a version select "master"?

[Trodfoot]

I am calling from the dashboard right now. I am just finishing getting it set up to use it too lock the doors if not locked for 15 minutes at home.

On Thu, Feb 2, 2023, 3:50 p.m. cdnninja @.***> wrote:

For some reason it looks like your call is passing an argument. Are using the dashboard or calling the service via an automation? I see how to adjust this and will test it doesn't break anything for me but I don't understand what is different on your end.

— Reply to this email directly, view it on GitHub https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/584#issuecomment-1414478464, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBLK5VJJTFCMYMJNCCGHLWVQ24DANCNFSM6AAAAAAUOODMSM . You are receiving this because you authored the thread.Message ID: @.***>

[Trodfoot]

Sorry didn't see this email before answering last one. Ok I did that and it went to Version 99c2b9c and I did the restart and hit the button and no error but thee new update was waiting to be done. Did the update/reboot and back to error.

On Thu, Feb 2, 2023, 3:56 p.m. cdnninja @.***> wrote:

Could you try go into hacs and "Redownload" and when offered a version select "master"?

— Reply to this email directly, view it on GitHub https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/584#issuecomment-1414482923, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBLK752URGU5ZCWXTBSHLWVQ3TFANCNFSM6AAAAAAUOODMSM . You are receiving this because you authored the thread.Message ID: @.***>

[cdnninja]

Go back to the master. Was the new update reverting to the released version?

[Trodfoot]

Ok went back to master and straight away it wants to update v2.5.8 So I got you the logs in hopes something shows. I did the redownload/reboot and then tried the button to unlock. Nothing. I even replaced the dashboard widget, nope. It is still waiting for me to do update. Next idea?

2023-02-02 23:36:08.455 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Get Vehicles Response {"responseHeader":{"responseCode":0,"responseDesc":"Success"},"result":{"vehicles":[{"vehicleId":"Gib29YMYLkq/yCm4z3PIRw==","nickName":"Hercules","modelCode":"SA4SAA24B200","modelName":"SANTA FE","modelYear":"2020","fuelKindCode":"G","trim":"Ultimate -","engine":"","exteriorColor":"ST2","dtcCount":0,"subscriptionStatus":"A","subscriptionEndDate":"20230630","mileageForNextService":5864.9,"daysForNextService":"20230719","overviewMessage":"","defaultVehicle":true,"enrollmentStatus":"4","genType":"G1","valetParkingModeOn":1,"vin":"5NMS5CAAXLH148695"}]}} 2023-02-02 23:36:09.435 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20230203045339', 'airCtrlOn': False, 'engine': False, 'doorLock': True, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '00H', 'unit': 0}, 'defrost': False, 'lowFuelLight': False, 'acc': False, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 0, 'sideBackWindowHeat': 0, 'dte': {'value': 184.0, 'unit': 1}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 50, 'sjbDeliveryMode': 1, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': False, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'engineRuntime': {}}}} 2023-02-02 23:36:09.435 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Old Vehicle Last Updated: None 2023-02-02 23:36:09.436 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - last_updated_at - before 20230203045339 2023-02-02 23:36:09.436 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - last_updated_at - after 2023-02-03 04:53:39+00:00 2023-02-02 23:36:09.436 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Current Vehicle Last Updated: 2023-02-03 04:53:39+00:00 2023-02-02 23:36:09.966 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 11739.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20230119', 'imatServiceOdometer': 17739.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20230719', 'currentOdometer': 11874.1, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 6000.0, 'serviceDaysDuration': 180, 'serviceMonthsThreshold': 6}}} 2023-02-02 23:36:10.515 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Received Pin validation response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'pAuth': 'KcUNqRaCbgCnrzSBWgcIOdfHTJqiOgvV'}}

2023-02-02 23:36:39.735 DEBUG (SyncWorker_0) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Get Vehicle Location {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'head': 176, 'coord': {'lat': 50.06870555, 'lon': -110.78118333333333, 'alt': 743.0, 'type': 0}, 'accuracy': {'hdop': 6, 'pdop': 10}, 'time': '20230203045315', 'speed': {'value': 0, 'unit': 0}}} 2023-02-02 23:36:40.235 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 33.374 seconds (success: True) 2023-02-02 23:36:40.971 DEBUG (SyncWorker_3) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20230203045339', 'airCtrlOn': False, 'engine': False, 'doorLock': True, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '00H', 'unit': 0}, 'defrost': False, 'lowFuelLight': False, 'acc': False, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 0, 'sideBackWindowHeat': 0, 'dte': {'value': 184.0, 'unit': 1}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 50, 'sjbDeliveryMode': 1, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': False, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'engineRuntime': {}}}} 2023-02-02 23:36:40.971 DEBUG (SyncWorker_3) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Old Vehicle Last Updated: 2023-02-03 04:53:39+00:00 2023-02-02 23:36:40.971 DEBUG (SyncWorker_3) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - last_updated_at - before 20230203045339 2023-02-02 23:36:40.971 DEBUG (SyncWorker_3) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - last_updated_at - after 2023-02-03 04:53:39+00:00 2023-02-02 23:36:40.972 DEBUG (SyncWorker_3) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Current Vehicle Last Updated: 2023-02-03 04:53:39+00:00 2023-02-02 23:36:41.423 DEBUG (SyncWorker_3) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 11739.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20230119', 'imatServiceOdometer': 17739.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20230719', 'currentOdometer': 11874.1, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 6000.0, 'serviceDaysDuration': 180, 'serviceMonthsThreshold': 6}}} 2023-02-02 23:36:41.626 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 1.334 seconds (success: True)

On Thu, Feb 2, 2023, 10:15 p.m. cdnninja @.***> wrote:

Go back to the master. Was the new update reverting to the released version?

— Reply to this email directly, view it on GitHub https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/584#issuecomment-1414990686, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBLK7CLN4LU6L4FBCAPCDWVSIAJANCNFSM6AAAAAAUOODMSM . You are receiving this because you authored the thread.Message ID: @.***>

[cdnninja]

Yes it will want you to update until I release the code for mass usage. Do you have any errors? The above looks clean. If all works fine on master we have fixed this.

[Trodfoot]

Sorry for not getting back yesterday. It was just one of those days here.

ok, I would say 95 percent is fixed. There are no error codes. But the actual action of the button is not working correctly. If I hit the word unlock on the widget the only thing i see happen is work is highlighted nothing else.

Then I hit the word unlock and the icon and up pops the info popup for the lock/unlock button. It has info, history, settings and related tabs on the top. Below that is the lock icon and the words unlock and lock.

I hit unlock. nothing. I hit unlock and lock icon (on pop up) nothing and then for giggles i hit lock and it unlocked the vehicle.

There is something in the code the lock/unlock that is out. For one thing when you get the door unlocked, the icon on the main widget changes to show unlock but the word stays to unlock instead of changing to lock. Same for the other way. I should not have to hit unlock, then the lock icon and the hit lock to open the doors. That popup shouldn't even show up.

Hope this helps, I tried so many combo's and i check each time by doing a forced refresh on my phones Bluelink app to see the vehicle status.

At least the errors are gone and it is getting data.. as for the part I want...lol... i will be here if you need something tried out.

Ken

On Fri, Feb 3, 2023, 3:53 p.m. cdnninja @.***> wrote:

Yes it will want you to update until I release the code for mass usage. Do you have any errors? The above looks clean. If all works fine on master we have fixed this.

— Reply to this email directly, view it on GitHub https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/584#issuecomment-1416499937, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBLK6GNO53RAVTDOPPRPLWVWD6DANCNFSM6AAAAAAUOODMSM . You are receiving this because you authored the thread.Message ID: @.***>

[nickjth]

Just re-read this thread and can see i am experiencing the same issue. This is via dashboard unlock button.

[140339603047664] HyundaiKiaConnectLock.async_unlock() got an unexpected keyword argument 'entity_id' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 200, in handle_call_service await hass.services.async_call( File "/usr/src/homeassistant/homeassistant/core.py", line 1787, in async_call task.result() File "/usr/src/homeassistant/homeassistant/core.py", line 1824, in _execute_service await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)( File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service await service.entity_service_call( File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 681, in entity_service_call future.result() # pop exception if have File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 968, in async_request_call await coro File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 721, in _handle_entity_call await result File "/usr/src/homeassistant/homeassistant/components/lock/init.py", line 105, in _async_unlock await entity.async_unlock(**service_call.data) TypeError: HyundaiKiaConnectLock.async_unlock() got an unexpected keyword argument 'entity_id'

[cdnninja]

@nickjth is this running master manually updated?

[cdnninja]

Sorry for not getting back yesterday. It was just one of those days here.

ok, I would say 95 percent is fixed. There are no error codes. But the actual action of the button is not working correctly. If I hit the word unlock on the widget the only thing i see happen is work is highlighted nothing else.

Then I hit the word unlock and the icon and up pops the info popup for the lock/unlock button. It has info, history, settings and related tabs on the top. Below that is the lock icon and the words unlock and lock.

I hit unlock. nothing. I hit unlock and lock icon (on pop up) nothing and then for giggles i hit lock and it unlocked the vehicle.

There is something in the code the lock/unlock that is out. For one thing when you get the door unlocked, the icon on the main widget changes to show unlock but the word stays to unlock instead of changing to lock. Same for the other way. I should not have to hit unlock, then the lock icon and the hit lock to open the doors. That popup shouldn't even show up.

Hope this helps, I tried so many combo's and i check each time by doing a forced refresh on my phones Bluelink app to see the vehicle status.

At least the errors are gone and it is getting data.. as for the part I want...lol... i will be here if you need something tried out.

Ken

On Fri, Feb 3, 2023, 3:53 p.m. cdnninja @.***> wrote:

Yes it will want you to update until I release the code for mass usage. Do you have any errors? The above looks clean. If all works fine on master we have fixed this.

— Reply to this email directly, view it on GitHub https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/584#issuecomment-1416499937, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBLK6GNO53RAVTDOPPRPLWVWD6DANCNFSM6AAAAAAUOODMSM . You are receiving this because you authored the thread.Message ID: @.***>

Can you try test when unlocked? Typically unlocking as a remote command works but never shows as the car auto relocks a minute or so later.

[nickjth]

Updated to master, clicking unlock on the dashboard button now does unlock the car but doesn't report status back afterwards.

[cdnninja]

Yes. Expected since the car relocks quickly. To confirm status works start with the car unlocked via fob. Then lock via home assistant.

[Trodfoot]

What I am getting now. It works to unlock the doors by pushing the button. It does not indicate they are unlocked. Unlock with keyfob, my bluelink shows unlocked, ha does not. Start vehicle and leave doors unlocked, bluelink shows unlocked, ha does not.

I went in to history and there wwas no indications of the door being unlocked all day, even when I did a refresh for today only.

On Sun, Feb 5, 2023, 1:52 p.m. cdnninja @.***> wrote:

Yes. Expected since the car relocks quickly. To confirm status works start with the car unlocked via fob. Then lock via home assistant.

— Reply to this email directly, view it on GitHub https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/584#issuecomment-1418261592, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBLKY2IQXAIL6N2K7KA4DWWAHI7ANCNFSM6AAAAAAUOODMSM . You are receiving this because you authored the thread.Message ID: @.***>

[Trodfoot]

Just for giggles after I just sent the msg I hit the lock icon on the dashboard which brings up the entity info and I hit lock on there. It changed the icon to unlocked. red icon. I checked bluelink and damn it, it loccked the doors. Remember this is after I ran the engine and just closed the doors. So the addon did do the job but something is still not right with icon indications.

On Sun, Feb 5, 2023, 1:52 p.m. cdnninja @.***> wrote:

Yes. Expected since the car relocks quickly. To confirm status works start with the car unlocked via fob. Then lock via home assistant.

— Reply to this email directly, view it on GitHub https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/584#issuecomment-1418261592, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBLKY2IQXAIL6N2K7KA4DWWAHI7ANCNFSM6AAAAAAUOODMSM . You are receiving this because you authored the thread.Message ID: @.***>

[cdnninja]

Okay so sounds like the lock unlock functions fine. This is purely a status issue.

This change our next steps. We need to see what data the api is giving us. If the app is showing correctly then we would think it's an us issue. Once you get it in a spot where it doesn't match between mobile app and home assistant take a look at the "data" sensors attributes in home assistant. Let me know what that shows for lock status. Ideally run a cached update from services prior to looking.

[Trodfoot]

Sorry to have to say this but I won't be able to help on this for a while. I somehow attracted some unwanted person who hacked me. Took both my main and backup servers and wiped them good. Luckly my pc is on its own vlan. When I get to where I was and I can still help I will. But that is going to take a while.

On Sun, Feb 5, 2023, 5:30 p.m. cdnninja @.***> wrote:

Okay so sounds like the lock unlock functions fine. This is purely a status issue.

This change our next steps. We need to see what data the api is giving us. If the app is showing correctly then we would think it's an us issue. Once you get it in a spot where it doesn't match between mobile app and home assistant take a look at the "data" sensors attributes in home assistant. Let me know what that shows for lock status. Ideally run a cached update from services prior to looking.

— Reply to this email directly, view it on GitHub https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/584#issuecomment-1418319179, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBLK4RHIWK5HHIEM4TIHTWWBAY5ANCNFSM6AAAAAAUOODMSM . You are receiving this because you authored the thread.Message ID: @.***>

[wipeout666]

Also have the same issue after updating from HA 2022.11.4 to 2023.2.5:

Lock.async_unlock() got an unexpected keyword argument 'entity_id'

[cdnninja]

@wipeout666 what version of the integration?

[wipeout666]

1.8.5. Looking at the changelog, seems it was fixed in 2.5.9 two weeks ago. Sorry I overlooked that. I'll update and report back.

Thanks

[cdnninja]

That a big change in version. As a note it is a breaking change to go from 1.x to 2.x.

[cdnninja]

The initial issue is resolved. Closing this ticket.