Closed zadigre closed 1 year ago
What does the attributes of your data sensor show at this time? This may be what the car is reporting.
I apparently had my logs set to warn only. I set the integration to debug. I'll report back later.
Debug logs may not be needed. The data sensor has attributes which contains this raw data.
Debug logs may not be needed. The data sensor has attributes which contains this raw data.
You mean in the log or somewhere else? Log was set to warn… so no data in the log.
numeric state is really at 127%
History screen shot here. I’ll try to catch the data in the log if I see it… I added automation to alert me as soon as it’s above 100%
here's the log... it received 127... which is weird. Car was running at that time. But if I do a manual force update, it will update properly.
2023-01-20 07:40:40.155 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20230120120529', 'airCtrlOn': False, 'engine': False, 'doorLock': False, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '00H', 'unit': 0}, 'defrost': False, 'acc': False, 'evStatus': {'batteryCharge': False, 'batteryStatus': 91, 'batteryPlugin': 0, 'remainTime2': {'etc1': {'value': 0, 'unit': 1}, 'etc2': {'value': 0, 'unit': 1}, 'etc3': {'value': 0, 'unit': 1}, 'atc': {'value': 0, 'unit': 1}}, 'drvDistance': [{'rangeByFuel': {'gasModeRange': {'value': 0.0, 'unit': 1}, 'evModeRange': {'value': 384.0, 'unit': 1}, 'totalAvailableRange': {'value': 384.0, 'unit': 1}}, 'type': 2}]}, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 0, 'sideBackWindowHeat': 0, 'dte': {}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 83, 'batState': 0, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': True, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'vehicleMovementHis': False, 'engineRuntime': {'value': 0, 'unit': 3}}}}
2023-01-20 07:40:40.156 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Old Vehicle Last Updated: 2023-01-19 22:38:51+00:00
2023-01-20 07:40:40.156 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - last_updated_at - before 20230120120529
2023-01-20 07:40:40.156 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - last_updated_at - after 2023-01-20 12:05:29+00:00
2023-01-20 07:40:40.156 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Current Vehicle Last Updated: 2023-01-20 12:05:29+00:00
2023-01-20 07:40:40.916 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 48081.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20220819', 'imatServiceOdometer': 60081.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20230219', 'currentOdometer': 57323.1, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 12000.0, 'serviceDaysDuration': 184, 'serviceMonthsThreshold': 6}}}
2023-01-20 07:40:41.499 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiCA] hyundai_kia_connect_api - Received get_charge_limits: {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': [{'plugType': 0, 'level': 127, 'dte': {'rangeByFuel': {'gasModeRange': {'value': 0.0, 'unit': 1}, 'evModeRange': {'value': 384.0, 'unit': 1}, 'totalAvailableRange': {'value': 384.0, 'unit': 1}}, 'type': 2}}, {'plugType': 1, 'level': 127, 'dte': {'rangeByFuel': {'gasModeRange': {'value': 0.0, 'unit': 1}, 'evModeRange': {'value': 384.0, 'unit': 1}, 'totalAvailableRange': {'value': 384.0, 'unit': 1}}, 'type': 2}}]}
2023-01-20 07:40:41.501 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 2.187 seconds (success: True)
without me doing anything, it went back to my regular values around 12h15pm. last update at is set to 21h... thus not sure why or when it updated to the correct value. no force refresh starts is 14 stops is 12.
Has this returned or been good? Debating if we add defensive logic on this.
yes it has returned on a few occasions... but not today for some reason even if I had the old version. last 7 days:
I just installed 2.5.7... I'll report back in a few days.
2.5.7 doesn't impact anything around this. I can put in some defensive logic for this. The zeros are something I won't be able to help with though.
Great waiting for the next update. Im fine for the zero. I’m not sure why it’s doing this… but it’s not staying there for very long.
Could you update from master and let me know if the values over 100% are gone?
so far, it didn't go over 100% on the master branch.
Still fine after 3 days. I guess we can mark this as closed
Canada Kona Electric 2021
Version 2.5.4
With regular updates, charge limits are showing 127%. After force update, correct values are shown. I don’t know exactly when it started…
my integration is set to no force refresh hour 14h to 12h. Scan interval set to 60 Force refresh set to 150.
I have an automation running that force a refresh at 5h. Also force refresh when my wife arrives home. I don’t care avoir force refresh during the day. But if it has to do it, I want this to happen only between 12 and 14h.
I can share log if needed (I cannot now as I’m posting this from my cell phone).
see attached screenshot.