Closed Chacsam closed 3 months ago
@dandelionclock can you see if you can check for this too please? It may be handled by your new PR. Probably need a .get instead of an array access.
I thought it was related to the Fleet API, so I went through all the trouble of setting up the Fleet API proxy and connecting to it from the integration but unfortunately this didn't work. It is therefore probably not API related.
Rollback to v3.22.2 confirms this issue is new in v3.23.0.
Thanks for the bug report. I'll issue a PR soon to fix the KeyError. I forgot that rear seats don't have seat coolers. It was trying to pull cooling seats settings on the rear seat hence the error.
I'm not sure if it will fix the battery sensor though. The error occurred at on June 10 but your graph only go up to 2pm June 9. Do you see a time correlation between the error and the sensor becoming unavailable?
Thanks for the bug report. I'll issue a PR soon to fix the KeyError. I forgot that rear seats don't have seat coolers. It was trying to pull cooling seats settings on the rear seat hence the error.
I'm not sure if it will fix the battery sensor though. The error occurred at on June 10 but your graph only go up to 2pm June 9. Do you see a time correlation between the error and the sensor becoming unavailable?
The error started on June 8 and was still on-going since June 9, The rest of the graph just shows missing battery. As @Sebazzz rolling back to v3.22.2 solved the issue: the sensor came back. It was still active after re-updating to v3.23.0 I have kept debug on, will let you know when I notice it's back to unavailable
I'm on my mobile now; but I read something yesterday about an unhandled task error. My guess is that the sensors are requested or processed in parallel and upon error Home Assistant cancels all executions - and with parallelism you don't always have the same code execute in the same order. I'm only guessing though.
Met vriendelijke groet, Sebastiaan Dammann
Van: Fred @.> Verzonden: Tuesday, June 11, 2024 6:01:35 AM Aan: alandtse/tesla @.> CC: Sebastiaan Dammann @.>; Mention @.> Onderwerp: Re: [alandtse/tesla] Unavailable battery sensor (Issue #996)
Thanks for the bug report. I'll issue a PR soon to fix the KeyError. I forgot that rear seats don't have seat coolers. It was trying to pull cooling seats settings on the rear seat hence the error.
I'm not sure if it will fix the battery sensor though. The error occurred at on June 10 but your graph only go up to 2pm June 9. Do you see a time correlation between the error and the sensor becoming unavailable?
The error started on June 8 and was still on-going since June 9, The rest of the graph just shows missing battery. As @Sebazzzhttps://github.com/Sebazzz rolling back to v3.22.2 solved the issue: the sensor came back. It was still active after re-updating to v3.23.0 I have kept debug on, will let you know when I notice it's back to unavailable
— Reply to this email directly, view it on GitHubhttps://github.com/alandtse/tesla/issues/996#issuecomment-2159735925, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAK4FML7O33XKAAX7B7RRM3ZGZZB7AVCNFSM6AAAAABJCU2HXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZG4ZTKOJSGU. You are receiving this because you were mentioned.Message ID: @.***>
Same problem here. Model 3 2024 (Software 2024.20.1). No battery SoC since version 3.23.0
Just updated to 3.23.0 this morning and lost battery as well. Happy to help with troubleshooting/testing.
Same problem. Battery entity is no longer being provided by the tesla_custom integration version 3.23.0
Thanks for the bug report. I'll issue a PR soon to fix the KeyError. I forgot that rear seats don't have seat coolers. It was trying to pull cooling seats settings on the rear seat hence the error. I'm not sure if it will fix the battery sensor though. The error occurred at on June 10 but your graph only go up to 2pm June 9. Do you see a time correlation between the error and the sensor becoming unavailable?
The error started on June 8 and was still on-going since June 9, The rest of the graph just shows missing battery. As @Sebazzz rolling back to v3.22.2 solved the issue: the sensor came back. It was still active after re-updating to v3.23.0 I have kept debug on, will let you know when I notice it's back to unavailable
not sure it does help anyhow, but giving the promised update: I even though I re-updated to v3.23 three days ago, my battery sensor has constantly been available so far, no new log to share
I removed the integration completely and reinstalled it (ver 3.23.0). Battery sensor still missing. Model 3 2024 („Highland“ with Software 2024.20.1). Maybe only „Highland“ is affected ?
Sensor is working again. :) Thank you
Is there an existing issue for this?
I have read about the Fleet API and understand I may need to use it
Version of the Tesla component
3.23.0
Version of the Tesla car software
2024.14.9
Model
Model 3
Current Behavior
Since several days the battery sensor is only occasionaly available. I cannot say if it's linked to a version update.
Gaps found in history:
Expected Behavior
Battery sensor to appear and remain there.
Debug logs
Anything else?
The
"battery_level":64
is the accurate value at that moment TheKeyError: 'rear center'
sounds appropriate as the M3 has no heating in center rear seat.Range still works during same period