Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Get data with active Check Control messages

See original GitHub issue

At the moment we do not have any example data with active check control messages. So we cannot parse these 😭

If you have a vehicle 🚗 that currently shows check control messages (red ❗ or yellow ⚠️ warnings in your instrument cluster 🕛 🕡 : ). Please send us your data: https://github.com/ChristianKuehnel/bimmer_connected#data-contributions

The status.json should then contain some data in the field checkControlMessages.

Issue Analytics

State:
Created 5 years ago
Comments:10 (8 by maintainers)

Top GitHub Comments

1reaction

m1n3rvacommented, Oct 7, 2018

@gerard33 Thx for the data 📜!

I created 2 PRs for this:

in #90 I just added your data and created tests for CCMs
in #91 I also added a new API to parse these CCMs into Python objects. So the answer to State.check_control_messages now is List[CheckControlMessage] instead of List[Dict].

I guess this does not fit to your implementation in Home Assistant, so this would be a breaking change. Please let me know what you think of #91 and if we should merge that.

1reaction

gerard33commented, Sep 24, 2018

@m1n3rva I have some data finally 😉

"checkControlMessages": [
      {
        "ccmDescriptionLong": "You can continue driving. Check tyre pressure when tyres are cold and adjust if necessary. Perform reset after adjustment. See Owner's Handbook for further information.",
        "ccmDescriptionShort": "Tyre pressure notification",
        "ccmId": 955,
        "ccmMileage": 41544
      }
    ]

My suggestion is to show the ccmDescriptionShort on the HA card like in the screenshot below. I have now changed this is in the binary_sensor component of HA on my test version.

But the cleanest way would be to do the processing in the library of course. Can you spend some time to implement that? If not then I will change it in the HA code and can release that together with bumping the version after PR #83 is merged.

cbs_screenshot