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

Data not updating, only values from initial adding are available #416

Closed
kosch104 opened this issue Oct 30, 2023 · 9 comments
Closed

Data not updating, only values from initial adding are available #416

kosch104 opened this issue Oct 30, 2023 · 9 comments

Comments

@kosch104
Copy link

kosch104 commented Oct 30, 2023

Since the API change I have the issue, that data is only fetched when initially adding my car after I entered my login details. This happened with all past versions, still with 1.60. I can only force refresh the values by removing and re-adding the integration. (UK & Europe)

Also I can't find any service called "fordpass.refresh_status" or anything similar to manually update, as written in the readme.

@tobox
Copy link

tobox commented Oct 30, 2023

I have the same problem. I managed to call "fordpass.poll_api" and "fordpass.refresh_status" using developer tools -> services, but no value was updated.

The SoC ist still an old value and the logbook shows now entries for fordpass.

EVCC running in parallel gets updates from the API correctly, so my account is not suspended.

Running 1.61 Beta 3

@itchannel
Copy link
Owner

Can you please check your logs for any errors generated.

@tobox
Copy link

tobox commented Oct 30, 2023

The output is very verbose, but I don't see any real errors. Since the whole log contains sensitive information, I could send it directly if you are interested.

In the log I found this:
... 'xevBatteryStateOfCharge': {'updateTime': '2023-10-30T01:46:45Z', 'oemCorrelationId': '28553', 'value': 95.5},...

The SoC in the Ford App says 95%.

But in Home Assistent, I only see sensor.fordpass_elveh with attribute "Battery Charge: 88.5".

Does this help? At which sensor/attribute should the current SoC end up?

@SquidBytes
Copy link
Collaborator

You can provide your json data, with sensitive information redacted, by following: https://github.com/itchannel/fordpass-ha/wiki/AutonomicData-Tutorial

For any error logs, you will still need to provide any error logs returned from HomeAssistant.

For clarification:
fordpass_elVeh "Battery Charge" attribute is returning the value of xevBatteryStateOfCharge in the json - that attribute should be the High Voltage Battery %. If you are charging, or recently drove, and your HomeAssistant API polling is long - it won't match exactly in the FordPass app because the HA integration may not have updated yet.

Regarding the Data not updating, when you initially setup the integration you should have setup a polling time. That time is what will update the information in the integration. Some sensors and attributes change more frequently.
If you go for a drive, and the odometer is not updating, then we would need your logs to see if there is an error somewhere.

@CptFry
Copy link

CptFry commented Oct 30, 2023

I had this earlier too. After I installed the repo, added the card it did work. I then noticed it wasn't updating.
After restarting HA it updated and has since been updating as per the service interval set.

@tobox
Copy link

tobox commented Oct 31, 2023

Even after a whole night and driving to work this morning, all displayed sensor values remained at their old values.

Polling time was set to 900 seconds.

Then I rebooted home assistant and all values were updated!

Strange.

@itchannel
Copy link
Owner

If you are still experiencing issues after updating to 1.61 can you please follow the below tutorial to provide me with your logs so we can diagnose the issue:
https://github.com/itchannel/fordpass-ha/wiki/Obtaining-Integration-Logs

@tobox
Copy link

tobox commented Nov 1, 2023

With 1.61 (release) it seems to be working properly.

@SquidBytes
Copy link
Collaborator

Sounds good. Going to close this issue.
If something happens, feel free to open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants