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

Tire pressures are being converted incorrectly #269

Closed
jerry-knight opened this issue Apr 19, 2023 · 6 comments
Closed

Tire pressures are being converted incorrectly #269

jerry-knight opened this issue Apr 19, 2023 · 6 comments

Comments

@jerry-knight
Copy link

I think sometime recently the reported tire pressures in PSI are now showing values that are actually in kPa. All of my PSI values in homeassistant/sensor/[VIN]/tire_pressure/state are now in the ~260 range, and 260 kPA is about 38 PSI. The standard non-PSI values are in the ~1800 range, so it really seems like all of the pressure values are getting an extra PSI-to-kPA conversion.

I don't see any open issues in OnstarJS, so I'm not sure whether I should submit this here or there. I see some unit conversions in the onstar2mqtt source, but it could be that OnstarJS is reporting the wrong units.

I'm currently running the latest docker image that reports version 1.5.5 in the logs.

@BigThunderSR
Copy link
Contributor

I'm getting wonky values for the tire pressures since last night and it is the same issue even when using OnStarJS directly without OnStar2MQTT.

@jerry-knight
Copy link
Author

Submitted a corresponding issue to OnStarJS.

OnStarJS Issue #219

For now, I'm doing additional conversions to compensate.

@BigThunderSR
Copy link
Contributor

It's not a direct kPa conversion either. They (GM) seem to have discombobulated the tire pressure outputs from the car on purpose to drive us nuts. 👎

@BigThunderSR
Copy link
Contributor

I put a fix into my latest build at https://github.com/BigThunderSR/onstar2mqtt for now.

If the change stays persistent from OnStar over the next week, I'll submit a PR here for the same fix,

@BigThunderSR
Copy link
Contributor

Looks like GM fixed the issue on their side, so I reverted the changes in my build.

On the flip side, I figured out a solution for #178 while staring at the code to implement the previous workaround, so it wasn't a complete waste. 😄

@michaelwoods
Copy link
Owner

Noticed this too, but looks to be back to normal now.

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

3 participants