pod-point-home-assistant-component icon indicating copy to clipboard operation
pod-point-home-assistant-component copied to clipboard

Cable Status sensor is unreliable since last update

Open flagshipenis opened this issue 1 year ago • 6 comments
trafficstars

I had based all of my charging automations off this sensor because it was the quickest to update and most reliable. Now this sensor can go an entire charging session without changing state from "unplugged" even if status is "charging" and it sais it is connected to the cloud

flagshipenis avatar May 26 '24 13:05 flagshipenis

I agree the sensor is now unreliable, constantly changing it's status. Below is a screenshot of the sensor. The car is plugged in .

Screenshot_20240526-185027

Sahnia avatar May 26 '24 17:05 Sahnia

I will take a look and try to recreate, I've not seen this on my pod. Its coming into the school half term this week so it will be unlikely that I will be able to take a look until next week. Was there a certain time that it started happening? Did you restart your Home Assistant instance before seeing it?

Anything to help me re-create it would be awesome

mattrayner avatar May 26 '24 18:05 mattrayner

Hi,

I have restarted home assistant a number of times and the problem continues. I am not sure how to recreate it.

Completely understand about half term. For me this issue has been on going for a while and not particularly problematic so not urgent.

Sorry I cannot be more helpful.

Sahnia avatar May 26 '24 18:05 Sahnia

I also have this issue.

willenic avatar Jun 01 '24 13:06 willenic

Another pod point with this issue. Mine in combination with a eCorsa, which only updates it's cable sensor when Stellantis can be arsed.

Screenshot_20240907-081334.png

Screenshot_20240911-114338.png

btxluke avatar Sep 02 '24 06:09 btxluke

image

It seems to me, that what is happening here is that when you switch "Charging Allowed" the cable status immediately changes to "unplugged" regardless of the actual plug status (is it renegotiating with the car?), and stays that way for about 5 minutes.

I use predbat to plan my charging slots, it refreshes every 5 minutes, so i was getting stuck in a doom loop of charging / not charging creating the behaviour you see above.

As a quick nasty fix, I created a helper that toggles according to the initial plug status, and then toggles off if the cable is reported unplugged for more than 30 minutes, and updated predbat to make decisions based on the smoothed sensor. It works, but feels nasty.

btxluke avatar Dec 30 '24 09:12 btxluke

Final update:

This confirms it, I think:

image

Everytime "Charging Allowed" is switched, Cable Status is reset for +/- 5 Minutes. If you are doing your charging programmatically, you'll need to make a sensor to smooth it out.

btxluke avatar Dec 31 '24 10:12 btxluke