Old Battery level and segmentation faults for headlights and aircon

[RogerG007]

Jamie, you are doing a fantastic job here. Many thanks for this. I was able to integrate the battery level in my openhab home automation which is fantastic. However, I noticed a few things:

I need to run phevctl battery a couple of times to get the latest value. The first time I start it, it returns an old battery level.

Headlights and air-condition do not work for me. Most of the time I get a segmentation fault and even if it runs through, it sadly does not work.

RogerG

[petitjfl]

Just a side note, I also really appreciate all your work. As soon as I get up to speed, connected and working i will be glad to help you guys troubleshoot.... it just that I'm a bit behind in getting g everything working lol.... I'll catch up with you guys... ;) Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: RogerG007 <notifications@github.com> Sent: Monday, June 29, 2020 1:59:25 PM To: phev-remote/phevcore <phevcore@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [phev-remote/phevcore] Old Battery level and segmentation faults for headlights and aircon (#6) Jamie, you are doing a fantastic job here. Many thanks for this. I was able to integrate the battery level in my openhab home automation which is fantastic. However, I noticed a few things: I need to run phevctl battery a couple of times to get the latest value. The first time I start it, it returns an old battery level. Headlights and air-condition do not work for me. Most of the time I get a segmentation fault and even if it runs through, it sadly does not work. RogerG — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fphev-remote%2Fphevcore%2Fissues%2F6&data=02%7C01%7C%7Ca0e79c5e2bfe43cf8dcc08d81c562904%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637290503657320205&sdata=L8c9JhwWBXmwgxiEZvp1magtMDiiKGAR9cQgwCVtm7Q%3D&reserved=0>, or unsubscribe<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOKJCC2NFZRJZT4GJCGOK3TRZDI73ANCNFSM4OLOQGIQ&data=02%7C01%7C%7Ca0e79c5e2bfe43cf8dcc08d81c562904%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637290503657320205&sdata=rDhO5CROQVCXGQTp1LkE2FE3R2t6ai83TVfpFBJObW0%3D&reserved=0>.

[gmta]

@RogerG007 I'm seeing the same battery level issue, but that seems to be the data the car gives us - maybe the app always goes through the registers more than once before it will display the level?

[gmta]

@RogerG007 Could you test with #7 to see if that fixes your segfault issues?

[papawattu]

Sorry I've been a bit inactive on this, I think I know what the battery level issue is and is a simple fix I will push later this week when I have time.

[aerofade]

hi @papawattu - this is some truly great work - thank you for all of the effort you've put into the project! You mentioned above that you thought you knew what the battery level issue was. Did you get to the bottom of it? I note that even if i come back hours later and re-run it, it doesn't update (i.e. the car is still reporting Register 1D: 29 00 00 00 and doesn't seem to want to update it - even though i know the battery is full)

I've not had a good look at the protocol, but wonder if there's something that forces the car to do a sensor update so that it reports valid data?

If i open the smart phone app, let it sync, then disconnect and rerun "phevctl battery" it reports the correct value

Again thanks for all of your work.