-
Notifications
You must be signed in to change notification settings - Fork 42
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
Comments
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. |
Submitted a corresponding issue to OnStarJS. For now, I'm doing additional conversions to compensate. |
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. 👎 |
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, |
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. 😄 |
Noticed this too, but looks to be back to normal now. |
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.
The text was updated successfully, but these errors were encountered: