Oh that’s great news, so just change the yaml as such?:
- platform: mitemp_bt
whitelist:
- 'A4:C1:38:7B:BB:B3'
Still not seeing the device, Flashed it but can’t get the info even when using https://atc1441.github.io/TelinkFlasher.html. probably other problem that doesn’t have to do with HA directly (getting “Detected custom Firmware” but no info passed). I’ve opened an issue about this on the developers project page.
thanks again.
So,
With the latest version of mitemp_bt (6.13) that supports the Telink custom firmware, you only need to
This is getting much better and quite easy to setup
Thanks @Magalex for this improvement
6.13 was released yesterday, which adds support for the custom firmware, as you guys already noticed. No need to change the sensor.py code yourself. As I understood, you can remove the encryptor key, when using the custom firmware.
Credits should be given to @karto (at least I assume he is the same as benkarro on github), based on the code in his post here in the forum. I’ve used his code in the 6.13 release. Instructions are also updated with links to the custom firmware.
Hi Aleksey,
I am facing same problem, my log is filled with this error
´´´
2020-10-14 14:20:57 ERROR (Thread-84) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-10-14 14:21:12 ERROR (Thread-85) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-10-14 14:21:27 ERROR (Thread-86) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-10-14 14:21:42 ERROR (Thread-87) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-10-14 14:21:57 ERROR (Thread-88) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-10-14 14:22:12 ERROR (Thread-89) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-10-14 14:22:27 ERROR (Thread-90) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-10-14 14:22:42 ERROR (Thread-91) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-10-14 14:22:57 ERROR (Thread-92) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-10-14 14:23:12 ERROR (Thread-93) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
2020-10-14 14:23:27 ERROR (Thread-94) [custom_components.custom_mitemp_bt.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
´´´
I am quite sure this is not a HW issue as i changed to another pi and i still get the same error
I don’t know exactly when this started but I discovered it today.
I am running the beta version of HASSIO on a Raspberry Pi. Here are the system details:
´´´
| arch | armv7l |
|---|---|
| chassis | embedded |
| dev | false |
| docker | true |
| docker_version | 19.03.11 |
| hassio | true |
| host_os | HassOS 4.14 |
| installation_type | Home Assistant OS |
| os_name | Linux |
| os_version | 4.19.127-v7 |
| python_version | 3.8.5 |
| supervisor | 247 |
| timezone | Europe/Copenhagen |
| version | 0.116.2 |
| virtualenv | false |
´´´
and i am running the latest version of your mitemp_bt component that supports custom Telink firmware
Hope you can help
I think I am in the same situation as @ghassan.
Migrating from a Pi4 (supervised install) to HassOS on Proxmox. It seems hci is not installed, instead it is using bluetoothctl.
So a bluetoothctl scan results in some mac codes;
Can these be used? Does the tool need other changes to work?
[edit]
It seems to have just started. Not made any changes other than the scan mentioned above, deleting the integration and starting to configure the builtin integration, several reboots/restarts and I suddenly noticed hci events in the log. Reinstalled this integration and seems to be working.
Bit odd really. Seems it is impossible to determine which bluetooth receivers are connected to the system and their hci numbers.
Underneath the logger config I have
logger:
default: info
logs:
custom_components.mitemp_bt.sensor: debug
that tells me what is going on.
HTH
I rolled back to version 4.13 by leaving the beta channel and the error disappeared. 
@Magalex you should look into compatibility with version 4.14 so that it doesn’t break it for every body when it is released officially
Thanks
/Ghassan
Would this sensor be able to work with your component?
I’ve released a new version 0.7.2, which is based on 0.6.13 and has a new option to apply sensor names via configuration.yaml.
0.7.2 release notes
sensor_names option. Note that when you use or change this option, it will create new entities. This means that you will have to update your lovelace cards, automations and/or scripts that use the entity_id . Note that you can still rename sensors afterwards from the UI. After the change, you can manually delete the old entities from the Developer Tools.mi_sensortype_mac (e.g. sensor.mi_temperature_A4C1382F86C) (default) or mi_sensortype_sensor_name (e.g. sensor.mi_temperature_livingroom) (with sensor_names option). Your current sensors with the short naming (e.g. mi_t_A4C1382F86C ) or manually modified names won’t be renamed, unless you use the sensor_names option.Probably not, it isn’t an xiaomi device, so changes are small that the component talks the same language as the component is expecting.
Hello, I can’t get this integration with HACS.
Here’s my config file:
sensor:
- platform: mitemp_bt
rounding: True
decimals: 1
period: 60
log_spikes: False
use_median: False
active_scan: False
hci_interface: 0
batt_entities: False
encryptors:
'24:FC:E5:5E:0F:AF': '217C568CF5D22808DA20181502D84C1B'
report_unknown: False
whitelist: False
I’m using custom firmware (atc) and I can’t find the device in Mi Home app, do I have to link it ?
LYWSD03MMC device
ty for any help
If you have the custom firmware, there is no need to use an encryption key, I think
Same here:
Logger: custom_components.mitemp_bt.sensor
Source: custom_components/mitemp_bt/sensor.py:139
Integration: mitemp_bt (documentation)
First occurred: 20:45:33 (3 occurrences)
Last logged: 20:47:34
HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
There is an issue opened here
You have to put random key otherwise config file is not valid for me
Did you also remove the line with encryptors:?
I have to keep it if I want to put MAC adress no ?
No, you can remove it. If you only want to receive this specific device, you can use the whitelist option.
What HassOS version are you running?
I was running the beta version hassOS 4.14 and this was the reason for the same issues i experienced. Leaving the beta program and rolling back to 4.13 everything works fine again.
can explain how to downgrade to 4.13, thnks