Closed bcutter closed 8 months ago
This issue is stale because it has been open for 90 days with no activity.
Not fixed. Will try to update HA to a newer version.
Anyway, wondering why there's not a single response after 3 months...
Interestingly, in MQTT it is correct in the device_tracker topic:
Not quite ;P took some time to really look closely, but there is a trailing space in "source_type ", messing the correct recognition up :(
Fixed with https://github.com/1technophile/OpenMQTTGateway/pull/1853
Oh great, so sometimes it's the little things right... 😄 Can you estimate when this fix will be shipped (in a stable release)?
As there are still some other issues which need addressing for the next release, a bit hard to say at the moment, but shouldn't bee too long.
Alright so definitely 2024 and probably until February (or even January)? :-)
Any update on this please? If I did not miss a release I tend to say we're still missing one, don't we? :-)
Please note I meanwhile discovered this for other devices provided by OMG/TheengsGateway too (other smart bands or a BM2 etc.) and therefore edited the title of this issue.
Describe the bug In Home Assistant (HA Core 2023.3.6) the
device_tracker.xiaomi_smart_band_7
entity's attribute hassource_type: gps
even it should besource_type: bluetooth_le
.Interestingly, in MQTT it is correct in the device_tracker topic:
To Reproduce Steps to reproduce the behavior:
BT: Publish HASS presence
switch in HAExpected behavior Attribute
source_type
should bebluetooth_le
in HA, like it is in MQTT.Screenshots
Environment (please complete the following information):
a046c8
Additional context As it is fine in MQTT but not in HA I fear you might close this issue and redirect me to... well, where?