What are these error messages?

[Imaginous]

The system works fine, but I see some errors I don't really understand.
I'm running 2026.2.1.

It's about the following errors:

• [setChargingLimit] INFOTAINMENT session invalid, requesting new session info...
• Received error message from domain DOMAIN_VEHICLE_SECURITY
  signed_message_fault: ERROR_INCORRECT_EPOCH
  operation_status: ERROR
• BLE RX: Message length (1182) exceeds max BLE message size

I have these messages for quite some versions now, but don't get why they are happening and how to fix them.
They happen very often as soon as there is communication between the ESP and the car.

Running on a ESP32-C6 with 4MB Flash.

[nagyrobi]

I guess what happens is that when the ESPHome node restarts, it doesn't gracefully close the connection with the car. Next time when it boots, when it tries to re-establish the connection with the car, it won't get the proper responses at first, because the car still considers the previous connection as active. These errors lead to force the initial handshake again with the car.
Probably a proper connection close before reboot would fix this, however, I don't believe anyone would respect that (manually call a disconnection routine and only reboot after that). Not sure if it could be called before OTA anyway. Plus a power cycle wouldn't even be predictable...

[PedroKTFC]

You're probably in the right ballpark. I've looked at the message handling many times and do think there are some loose ends that could be cleaned up. However, I'm very much of the "if it ain't broke, don't fix it" school!

[PedroKTFC]

That's very odd, I don't see it in my board (although I probably need to watch what happens as I move the board in and out of range to simulate the car coming and going). I wonder if it is somehow out of sync when a connection is made. You say it works fine otherwise so I'm guessing once it's synched properly it is reading the car properly.

[Imaginous]

I wonder how the RX packages can be too long, is the Model 3 Highland sending more data, or is the message crippled or not split correctly. Having 2 messages in one RX receive block?

The RX messages happen most of the time during charging of the car (while in BLE range).

It's more that I try to understand why this is happening.

[PedroKTFC]

I don't think any single message can be too long, so I think this is happening because an error condition isn't being handled correctly (eg there's a reset and there are still messages in the queue that get muddled with new messages). Does it cause you any issues?

[Imaginous]

As far as I can see everything works.
Also don't notice any real delays. I keep an eye on it.

If I find some time I will have a look at tge code.

Keep up your great work!