Issue with mqtt and linktap

[robitsrl]

The problem

H, I have integrated a link-tap device with mqtt but I have the some error in logs saing signal_strength and seconds not using the right mesurament

There is a way to fix it ?

What version of Home Assistant Core has the issue?

2023.2.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Link-Tap

Link to integration documentation on our website

https://www.link-tap.com/#!/mqtt-and-home-assistant

Diagnostics information

config_entry-mqtt-78d4f680af0222c4b71fd1bac5092177.json (1).txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Entity sensor.dea44923004b1200_signal (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement '%' which is not a valid unit for the device class ('signal_strength') it is using; expected one of ['dBm', 'dB']

Entity sensor.165c2f27004b1200_failsafe_duration (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'seconds' which is not a valid unit for the device class ('duration') it is using; expected one of ['s', 'd', 'min', 'h']

Additional information

No response

[home-assistant[bot]]

Hey there @emontnemery, @jbouwh, mind taking a look at this issue as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `mqtt` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign mqtt` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

mqtt documentation mqtt source _{^{(message by IssueLinks)}}

[jbouwh]

A similar issue is https://github.com/home-assistant/core/issues/85519. Assumable is that the firmware should be updated to set the correct options.

[jbouwh]

Closing this one as it is a duplicate