Skip to content
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

Charging Binary Sensor Not Working - Ariya #77

Open
RGx01 opened this issue Nov 13, 2024 · 8 comments · Fixed by #79
Open

Charging Binary Sensor Not Working - Ariya #77

RGx01 opened this issue Nov 13, 2024 · 8 comments · Fixed by #79
Assignees
Labels
bug Something isn't working

Comments

@RGx01
Copy link

RGx01 commented Nov 13, 2024

What happened?
Since release 0.7.0 Binary Sensor Charging does not report charging when charging. Also noting a high number of "Error communicating with API" in logs.

To Reproduce
Charge an Ariya and check sensor status after polling.

Expected behavior
Binary Sensor should report Charging whilst charging.

Log Output
2024-11-13 16:48:01.491 DEBUG (MainThread) [custom_components.nissan_connect.coordinator] Finished fetching Poll Coordinator data in 0.321 seconds (success: True)
2024-11-13 16:48:03.748 DEBUG (MainThread) [custom_components.nissan_connect.coordinator] Finished fetching Update Coordinator data in 2.258 seconds (success: True)
2024-11-13 16:48:09.628 DEBUG (MainThread) [custom_components.nissan_connect.coordinator] Finished fetching Statistics Coordinator data in 2.410 seconds (success: True)
2024-11-13 17:03:03.066 WARNING (MainThread) [custom_components.nissan_connect.coordinator] Error communicating with API
2024-11-13 17:03:03.067 DEBUG (MainThread) [custom_components.nissan_connect.coordinator] Finished fetching Update Coordinator data in 0.025 seconds (success: True)
2024-11-13 17:18:03.766 WARNING (MainThread) [custom_components.nissan_connect.coordinator] Error communicating with API
2024-11-13 17:18:03.767 DEBUG (MainThread) [custom_components.nissan_connect.coordinator] Finished fetching Update Coordinator data in 0.725 seconds (success: True)
2024-11-13 17:33:03.066 WARNING (MainThread) [custom_components.nissan_connect.coordinator] Error communicating with API
2024-11-13 17:33:03.066 DEBUG (MainThread) [custom_components.nissan_connect.coordinator] Finished fetching Update Coordinator data in 0.024 seconds (success: True)
2024-11-13 17:48:01.458 DEBUG (MainThread) [custom_components.nissan_connect.coordinator] Finished fetching Poll Coordinator data in 0.288 seconds (success: True)
2024-11-13 17:48:02.841 DEBUG (MainThread) [custom_components.nissan_connect.coordinator] Finished fetching Update Coordinator data in 1.383 seconds (success: True)
2024-11-13 17:48:02.844 DEBUG (MainThread) [custom_components.nissan_connect.sensor] Updating odometer state
2024-11-13 17:48:11.138 DEBUG (MainThread) [custom_components.nissan_connect.coordinator] Finished fetching Statistics Coordinator data in 1.919 seconds (success: True)
2024-11-13 18:03:02.678 WARNING (MainThread) [custom_components.nissan_connect.coordinator] Error communicating with API
2024-11-13 18:03:02.678 DEBUG (MainThread) [custom_components.nissan_connect.coordinator] Finished fetching Update Coordinator data in 0.636 seconds (success: True)

Home Assistant Version
Core
2024.11.1
Supervisor
2024.11.2
Operating System
13.2
Frontend
20241106.2

Integration Version
v0.7.0

Additional context
polling interval = 60
polling interval while charging = 15
update interval = 15
update interval for stats = 60

@RGx01 RGx01 added the bug Something isn't working label Nov 13, 2024
@dan-r
Copy link
Owner

dan-r commented Nov 16, 2024

The errors communicating with the API seems to be some sort of Nissan issue that I'm getting too.

Does the plugged in sensor update correctly?

@RGx01
Copy link
Author

RGx01 commented Nov 17, 2024

Not 100% sure as I've rolled back to v0.6.0.

My primary use case for using this sensor is to determine which utility meter bucket to put the consumed energy in as we have several vehicles. If I get time this week I'll roll back up and see if I could also use plugged in sensor to do the same job.

@adammccormack162
Copy link

Ive got the same issue...

Yes, the plugged in sensor updates correctly on 0.7 - but the charging state doesnt show

@dan-r
Copy link
Owner

dan-r commented Nov 22, 2024

I appreciate this is a bit annoying, but could one (or both) of you please install v0.7.1-beta.2 before your next charge. You'll see in the log messages like this:
2024-11-22 10:16:57.545 WARNING (SyncWorker_12) [custom_components.nissan_connect.kamereon.kamereon] FetchBatteryStatusAriya: {'lastUpdateTime': '2024-11-22T10:12:10Z', 'timeRequiredToFullSlow': 330, 'timeRequiredToFullNormal': 180, 'timeRequiredToFullFast': 90, 'batteryLevel': 92, 'batteryBarLevel': 223, 'rangeHvacOn': 196, 'rangeHvacOff': 203, 'plugStatus': 0, 'chargeStatus': 0, 'chargePower': 1, 'batteryCapacity': 40000}

If possible, can you please grab one of these messages when you are charging and one when you are not.

Thanks in advance!

@adammccormack162
Copy link

FetchBatteryStatusAriya: {'lastUpdateTime': '2024-11-22T10:50:07Z', 'batteryLevel': 77, 'batteryTemperature': 0, 'batteryAutonomy': 196, 'plugStatus': 0, 'chargingStatus': 0.0, 'chargingRemainingTime': 68, 'batteryCapacity': 63, 'batteryAvailableEnergy': 44, 'rangeHvacOn': 0, 'rangeHvacOff': 0}

FetchBatteryStatusAriya: {'lastUpdateTime': '2024-11-22T11:08:50Z', 'batteryLevel': 77, 'batteryTemperature': 0, 'batteryAutonomy': 196, 'plugStatus': 1, 'chargingStatus': 0.0, 'chargingRemainingTime': 97, 'batteryCapacity': 63, 'batteryAvailableEnergy': 44, 'rangeHvacOn': 0, 'rangeHvacOff': 0}

@dan-r
Copy link
Owner

dan-r commented Nov 28, 2024

Thats really strange - chargingStatus is what I'd expect to update but it doesnt seem to.

Do any of your logs show chargingStatus to be anything other than 0?

@adammccormack162
Copy link

I'd have to check the old version - to see what was coming out on that... (assuming thats what you meant) - but it must do - as it was updating the status to charging

@dan-r dan-r closed this as completed in #79 Dec 5, 2024
@dan-r dan-r reopened this Dec 5, 2024
@pusur333
Copy link

My does also not change. Can I be in any help with logs etc or have you seen the error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants