Fix name in lovelace example to match sensor name

[js94x]

this PR is related to #3613 and fixes the sensor name in lovelace example too

[netlify]

✅ Deploy Preview for teslamate ready!

Name	Link
🔨 Latest commit	dc3ec8d
🔍 Latest deploy log	https://app.netlify.com/sites/teslamate/deploys/65e4b838fffe3900088d3f35
😎 Deploy Preview	https://deploy-preview-3718--teslamate.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[tobiasehlert]

@js94x, is there a sensor.tesla_tpms_pressure_fl for bar then?
Can't see that in the sensor.yaml file, but I don't run HA myself either so can't check.

[js94x]

Hi @tobiasehlert

yes, Teslamate is exposing tpms_pressure_* via MQTT, see here:
https://github.com/teslamate-org/teslamate/blob/master/website/docs/integrations/mqtt.md?plain=1#L70-L73

For using these in HA, there is a "mapping" from these MQTT topics to corresponding sensors in Home Assistant, see here for example: https://github.com/teslamate-org/teslamate/blob/master/website/docs/integrations/home_assistant.md?plain=1#L447

I used all the examples from the docs to display Teslamate data in HA and wondered about four "entity not found" errors in Lovelace UI, therefore I created the PR 👍

[tobiasehlert]

Thanks for clarification @js94x 👍

[tobiasehlert]

LGTM