custom-components/ble_monitor

BLE monitor for passive BLE sensors

ble_monitor's Issues

Variables are overwritten with update

Updating with HACS will overwrite the variables in sensor.py. These should be moved to configuration.yaml.

I will work on this coming days.

@Magalex2x14 can you let me know what can be taken as constants and what you want in configuration.yaml? I think the limits do not have to be in configuration.yaml, am I right?

The sensor stops updating after some time and requires a restart of the server

Hi,

I have been using this custom component for the past week as the official one stopped reporting data after a couple of hours after each restart.

The custom component works really well for me but usually, after running HA for 2-3 days the sensor stops updating as well. I am running HA in a docker container on my Raspberry Pi 3.

If I connect to my docker container and run hcitool lescan --duplicates and a hcidump --raw I can still see some data in my terminal.

For now, my only temporary solution is to restart my docker container to get the sensor to update itself again. Is there anything else I could do, or any command I could run to make the sensor work again without restarting?

Ben

Entity not getting created

So I have successfully been running this component on a few different hassio versions until recently .

In order to debug some errors related to miio components I uninstalled this component and reinstalled it again on Hassio 0.102 .

Since then it has never worked again and although I can see the component is loading in the logs no entity is being created anymore !

Tried to follow the installation steps all over again but no luck .

My hcitool / hcidump are exactly the same as before, nothing has changed since I had it working . Ran sudo setcap 'cap_net_raw,cap_net_admin+eip' which hcitool and setcap 'cap_net_raw,cap_net_admin+eip' which hcidump again and it also didn't help .

Feeling a bit lost here as there seems to be no change on my side that I can track except for the hassion version, which is now 0.102.3.

On a sidenote, I can see both my MJ_HT_V1 devices in my bluetooth list in the raspberry .

More features and options. LOCKED! Please open new issue or discussion.

• ability to specify BT interface; upcoming in v0.5
• ability to specify name for every unique id (mac);
• option to create separate entities for battery info 0.5.4-beta
• option to log unsupported Xiaomi sensors (INFO log level, reduced messages frequency, once per period?) 0.6.1
• the ability to receive data simultaneously from multiple interfaces 0.5.5-beta
• the ability to specify the number of decimal places for each type of measurement, for example:

decimals:
   temperature: 1
   humidity: 0

• consider representing sensors as devices in the HA device registry 0.9.0-beta
• "is it possible to include a timeout configuration i.e. when no data received after the timeout time, the entity is set as unavailable"
• whitelist 0.6.7
• support for storing mac:key pairs in secrets it works
• think of a hybrid solution for receiving data from sensors that do not appear in BLE ADV messages (#18, for example);
• BLE device tracker; 4.0.0

Xiaomi Honeywell Formaldehyde Monitor (JQJCY01YM) support

Hello, i am new to Home Assistant and Github.
Is it possible to integrate the "Xiaomi Honeywell Formaldehyde Monitor (JQJCY01YM)" into the sensor.mitemp_bt custom components ?

This sensor has a square shape and displays Formaldehyde (HCHO) level in mg/m^3 on the screen. It is powered by 2 AAA batteries and connects to Mi Home app with Bluetooth 4.2. I think it only works on the Mi Home Mainland China server and in the app it displays HCHO level, temperature and humidity.

Here are the specs :
https://www.priceboon.com/product/xiaomi-honeywell-jqjcy01ym/

Did: blt.3.129cmt93c5s00
Name: Xiaomi Honeywell Formaldehyde Monitor
Model: yuemee.airmonitor.mhfd1
Token: d8d033653b181975ac23d8e2
Mac: 48:57:43:00:9E:13

I checked the parings.txt file created by the "vevs Mi Home app" and it might use encryption like the LYWSD03MMC. The Bindkey is 24 characters long.

I followed the instructions on enabling logger and report_unknown option in Home Assistant and here is my home-assistant.log file attached to this message. I can confirm using the "nRF Connect" Android app that the device that appears in the log with MAC address : 485743009E13 is indeed the JQJCY01YM sensor.
home-assistant.log

How to use this as standalone?

First thing is first, so thank you for this project, it really improves the current status of the sensors in home assistant.
My question is more related on how to use as standalone or as a library to be integrated in something like this https://github.com/algirdasc/xiaomi-ble-mqtt
The use case is to be able to use a simple device such as rpi to gather the data and send it to home assistant via mqtt for those sensors that the home assistant bluetooth device cannot reach.
See algirdasc/xiaomi-ble-mqtt#17 for the 'reverse' issue.

Thanks!

Can't use component if more then one usb Bluetooth controllers present

What is use:

• Arch Linux x86_64
• home assistant 0.104 on hassio
• 2 usb bluetooth controllers

Component doesn't work at all. After logging into main docker container I can see that component starts hcidump, but hcitool isn't started. If manually start "hcitool -i hci0 lescan --duplicates --passive", than hcidump start populating values from scanned ble sensors (I've added parameter "-i hci1" to hcidump call in code).

PS: Tried to append "-i hci1" to parameters @sensor.py->start function with no success :(. Have no clue why it is starts OK from command line and not from python...

sensor ble not work

hi
after the update in the sensor not work .
this is the log:

PermissionError: [Errno 1] Operation not permitted
2020-02-24 15:01:58 ERROR (Thread-41) [asyncio] Fatal write error on socket tran                                                                                        sport
protocol: <aioblescan.aioblescan.BLEScanRequester object at 0x43288d50>
transport: <_SelectorSocketTransport fd=20 read=idle write=<idle, bufsize=0>>
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 857, in write
    n = self._sock.send(data)
PermissionError: [Errno 1] Operation not permitte

thanks

LYWSD02

Hi,

The LYWSD02 dont report battery status...

setcap instructions to different version does not work anymore

Hi @Magalex2x14

Since home asssistant 0.106, I got the permission error back. I tried the instructions as we have added in the faq, but for some strange reason, they don't work anymore.

As you can see, it is referring to python3.8, I changed it to python3.7 (which is also used by Home Assistant), but if I look at the path which is given by the getcap command, it is still using python3.8.

pi@raspberrypi:~ $ sudo getcap `readlink -f \`which python3\``
/home/pi/.local/bin/python3.8 = cap_net_admin,cap_net_raw+eip
pi@raspberrypi:~ $ sudo setcap 'cap_net_raw,cap_net_admin+eip' /usr/bin/python3.7
pi@raspberrypi:~ $ sudo getcap `readlink -f \`which python3\``
/home/pi/.local/bin/python3.8 = cap_net_admin,cap_net_raw+eip

Strange thing is that, after a restart (or two) it all works normal now, despite the fact that it is using the wrong python version. I'm a bit puzzled what is wrong here. Anyhow, it works normal, so no urgent question, but we might need to update the instructions. But for that, I need to understand what is going on.

It's not creating a Entity

Followed the guide and I'm running hassio, tried with and without the install bluez-hcidump and have restarted multiple times using the config provided on the integration page and still will not create a Entity. logs only show a warning about the integration "You are using a custom integration for mitemp_bt which has not been tested by Home Assistant...."
ps: can't use "name:" on configuration

No entities after reboot

OS: Hassio in a KVM on latest Proxmox version
Hassio version: 0.103.5
Component version: 0.4.1

First of all, a slightly off topic, quick message: Thank you very much for this awesome component! I have been running it on Hassio on my Pi 3+ with an OpenMQTTGateyway for about one month without any problems.

Three days ago, I have moved from a Pi to a more powerfull Proxmox-based setup. Now I run Hassio in a KVM which works great. I have installed mitemp_bt from HACS. The OpenMQTTGateway is up and running. I can pair all of my 9 pieces of Xiaomi LYWSDCGQ without any problems and they will appear in HA. They work flawlessly until a Home Assistant reboot. Afterwards, they have disappeared from HA, although MQTT activity can be seen by using the MQTT Explorer under the topic /home/OpenMQTTGateway_ESP32_BLE/BTtoMQTT. 5 sensors are listed there. They receive temperature and humidity information. However, this information is not passed to HA, i.e., no entities are created in HA. After dis- and reconnecting the ESP32 from power and repairing the devices, everything seems to work fine, until the next Home Assistant restart. Is there some kind of debug option or log entry with further information?

Update to 0.4.0 causes Home Assistant crashes

I am reporting the issue during upgrade from 0.4.0-beta5 to 0.4.0 final.
When I pressed "UPDATE" button in HACS, Home Assistant stop to working.

homeassistant    | 2019-12-22 23:03:52 INFO (MainThread) [hacs] Running set_state for custom-components/sensor.mitemp_bt
homeassistant    | 2019-12-22 23:03:52 INFO (MainThread) [hacs] Running update for custom-components/sensor.mitemp_bt
homeassistant    | 2019-12-22 23:03:56 INFO (MainThread) [hacs] Running set_state for custom-components/sensor.mitemp_bt
homeassistant    | 2019-12-22 23:03:56 INFO (MainThread) [hacs] Running install for custom-components/sensor.mitemp_bt
homeassistant    | 2019-12-22 23:03:59 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1915840048] Connection closed by client
homeassistant    | Exception in thread Thread-1:
homeassistant    | Traceback (most recent call last):
homeassistant    |   File "/usr/local/lib/python3.7/threading.py", line 926, in _bootstrap_inner
homeassistant    |     self.run()
homeassistant    |   File "/usr/local/lib/python3.7/threading.py", line 870, in run
homeassistant    |     self._target(*self._args, **self._kwargs)
homeassistant    |   File "/usr/src/homeassistant/homeassistant/util/logging.py", line 85, in _process
homeassistant    |     self._queue.get(), self.loop
homeassistant    |   File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 433, in result
homeassistant    |     raise CancelledError()
homeassistant    | concurrent.futures._base.CancelledError
homeassistant    |
homeassistant    | Config directory: /config
homeassistant    | Traceback (most recent call last):
homeassistant    |   File "/usr/src/homeassistant/homeassistant/__main__.py", line 396, in <module>
homeassistant    |     sys.exit(main())
homeassistant    |   File "/usr/src/homeassistant/homeassistant/__main__.py", line 388, in main
homeassistant    |     exit_code = asyncio_run(setup_and_run_hass(config_dir, args))
homeassistant    |   File "/usr/local/lib/python3.7/asyncio/runners.py", line 43, in run
homeassistant    |     return loop.run_until_complete(main)
homeassistant    |   File "/usr/local/lib/python3.7/asyncio/base_events.py", line 566, in run_until_complete
homeassistant    |     self.run_forever()
homeassistant    |   File "/usr/local/lib/python3.7/asyncio/base_events.py", line 534, in run_forever
homeassistant    |     self._run_once()
homeassistant    |   File "/usr/local/lib/python3.7/asyncio/base_events.py", line 1771, in _run_once
homeassistant    |     handle._run()
homeassistant    |   File "/usr/local/lib/python3.7/asyncio/events.py", line 88, in _run
homeassistant    |     self._context.run(self._callback, *self._args)
homeassistant    |   File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 18, in _handle_async_response
homeassistant    |     await func(hass, connection, msg)
homeassistant    |   File "/config/custom_components/hacs/ws_api_handlers.py", line 192, in hacs_repository
homeassistant    |     await repository.install()
homeassistant    |   File "/config/custom_components/hacs/repositories/repository.py", line 382, in install
homeassistant    |     self.ref,
homeassistant    |   File "/config/custom_components/hacs/repositories/repository.py", line 484, in download_content
homeassistant    |     directory_path, self.ref
homeassistant    |   File "/usr/local/lib/python3.7/site-packages/backoff/_async.py", line 131, in retry
homeassistant    |     ret = await target(*args, **kwargs)
homeassistant    |   File "/usr/local/lib/python3.7/site-packages/aiogithubapi/repository.py", line 92, in get_contents
homeassistant    |     raise AIOGitHubException(f"GitHub returned {response.status} for {url}")
homeassistant    | aiogithubapi.exceptions.AIOGitHubException: GitHub returned 404 for https://api.github.com/repos/custom-components/sensor.mitemp_bt/contents/custom_components/mitemp_bt

When I restart the HA, and click to HACS -> Installed -> Xiaomi BLE... so it goes to crash with similar message again. In logs the error is similar.
Note: The directory mitemp_bt is missing in custom_components directory now.

homeassistant    | 2019-12-22 23:21:56 INFO (MainThread) [hacs] Running set_state for custom-components/sensor.mitemp_bt
homeassistant    | 2019-12-22 23:21:56 INFO (MainThread) [hacs] Running update for custom-components/sensor.mitemp_bt
homeassistant    | 2019-12-22 23:21:59 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1874031024] Connection closed by client
homeassistant    | Traceback (most recent call last):
homeassistant    |   File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main
... 

sensors unavailable

Hello,

I have problem then install sonarr or radarr sensors. If i enable sonarr or radarr then xiaomi temperature with your repo show "unavailable". All installed from Home Assistant Community Store

Xiaomi BLE monitor sensor platform: 0.5.5
Sensor type: LYWSDCGQ
Home Assistant 0.105.5 (docker)
Sonarr: https://github.com/custom-components/sensor.sonarr_upcoming_media
Radarr: https://github.com/custom-components/sensor.radarr_upcoming_media
and this https://github.com/custom-cards/upcoming-media-card

Thank you

Where are miflora sensors data?

Hi,

I just discovered this custom-component and looks great so I want to try it because I want only one component to retrieve al my BLE sensors data. I have two miflora sensors, two LYWSD03MMC (I know they are not supported right now, no problem), and a LYWSD02.

With the LYWSD02 I had no problem. Found it easy and works great.
But with the miflora, I can not find them in States in Dev Tools. I do not see any new sensor for them or see anything in the logs. Maybe the component is not reading them?

With hcitool lescan command I can see them. I also could retrieve their data with other (python) scripts so I think they work fine.

Is there anywhere I can find some clue about what is happening?

Insert 2 component

it's a beautiful job.
I have 3 "lywsd02" and 1 LYWSDCGQ.
Is it possible to insert all the devices? I did various tests and I failed.
THANKS

LYWSD03MMC support (implemented since 0.6.0)

After a deeper study of the information available on the Internet, it seems that there is hope for the implementation of support for other sensors (as far as I understand, support for sensors with a method similar to ours is implemented in ESPHome). In addition to the already implemented work with LYWSDCGQ, I talk about:

• LYWSD02 (rectangular body, E-Ink) - dump received, work is done, supported since v0.4.0...

• HHCCJCY01 (MiFlora) - dump received, work is done, supported since v0.4.0...

• CGG1 (round body, E-Ink) - dump received, work is done, supported since v0.4.0...

• LYWSD03MMC ( square body, segment LCD) - dump received, need some help, start reading from this post.
  Collected tech.details summary.
  The decryption issue has been resolved, only the time for implementation is needed. Testing Released

ATTENTION! This topic discusses only questions regarding the operation of LYWSD03MMC sensors and methods for extracting encryption keys.

UPD. The dump didn’t help... Apparently, the advertisements are encrypted. But there is still hope!

Any plans to support LYWSD03MMC?

I've bought one Xiaomi Mijia LYWSD03MMC Smart Bluetooth 4.2 Electric Thermometer Second Generation, but as you documented, it's not supported and is not working.

Any plans to support this second generation sensor?

Thanks,
FL

HHCCJCY01 (Mi Flora) sensor has no battery level

Wow,plant sensors are now supported by your component. Thank you.
There is no battery level info for HHCCJCY01 like i see for LYWSDCGQ.

Is it a bug or battery info is not available?

Cheers.

Xiaomi Qingping Bluetooth Smart Alarm Clock support

Hello.
Is it possible to make Qingping support Bluetooth Smart Alarm Clock?
Two types of packets, encrypted and open, are transmitted alternately.

2020-03-14 17:17:04.719892 > 04 3E 1F 02 01 00 00 33 C1 50 34 2D 58 13 02 01 06 0F 16 95 FE 30 58 76 05 6B 33 C1 50 34 2D 58 08 B6
2020-03-14 17:17:05.729025 > 04 3E 21 02 01 00 00 33 C1 50 34 2D 58 15 02 01 06 11 16 CD FD 08 0C 33 C1 50 34 2D 58 01 04 D9 00 CE 00 BD
2020-03-14 17:17:06.731964 > 04 3E 1F 02 01 00 00 33 C1 50 34 2D 58 13 02 01 06 0F 16 95 FE 30 58 76 05 6B 33 C1 50 34 2D 58 08 B5
2020-03-14 17:17:07.737678 > 04 3E 21 02 01 00 00 33 C1 50 34 2D 58 15 02 01 06 11 16 CD FD 08 0C 33 C1 50 34 2D 58 01 04 D9 00 CE 00 BC
2020-03-14 17:17:08.741956 > 04 3E 1F 02 01 00 00 33 C1 50 34 2D 58 13 02 01 06 0F 16 95 FE 30 58 76 05 6B 33 C1 50 34 2D 58 08 B6
2020-03-14 17:17:09.749598 > 04 3E 21 02 01 00 00 33 C1 50 34 2D 58 15 02 01 06 11 16 CD FD 08 0C 33 C1 50 34 2D 58 01 04 D9 00 CD 00 BC
2020-03-14 17:17:10.751087 > 04 3E 1F 02 01 00 00 33 C1 50 34 2D 58 13 02 01 06 0F 16 95 FE 30 58 76 05 6B 33 C1 50 34 2D 58 08 B7
2020-03-14 17:17:11.758210 > 04 3E 21 02 01 00 00 33 C1 50 34 2D 58 15 02 01 06 11 16 CD FD 08 0C 33 C1 50 34 2D 58 01 04 D9 00 CD 00 BC

Mac: 58:2D:34:50:C1:33
D9 00 CD 00 21.7*C 20,5%

2020-03-14 17:17:36.884165 > 04 3E 2A 02 01 00 00 33 C1 50 34 2D 58 1E 02 01 06 1A 16 95 FE 58 58 76 05 6C 33 C1 50 34 2D 58 4D 4F 90 0B 2E 09 00 00 BB AC 83 32 B8
2020-03-14 17:17:37.889836 > 04 3E 21 02 01 00 00 33 C1 50 34 2D 58 15 02 01 06 11 16 CD FD 08 0C 33 C1 50 34 2D 58 01 04 D9 00 CE 00 BD
2020-03-14 17:17:38.891157 > 04 3E 2A 02 01 00 00 33 C1 50 34 2D 58 1E 02 01 06 1A 16 95 FE 58 58 76 05 6C 33 C1 50 34 2D 58 4D 4F 90 0B 2E 09 00 00 BB AC 83 32 B8
2020-03-14 17:17:39.902285 > 04 3E 21 02 01 00 00 33 C1 50 34 2D 58 15 02 01 06 11 16 CD FD 08 0C 33 C1 50 34 2D 58 01 04 D9 00 CD 00 BE
2020-03-14 17:17:40.903468 > 04 3E 2A 02 01 00 00 33 C1 50 34 2D 58 1E 02 01 06 1A 16 95 FE 58 58 76 05 6C 33 C1 50 34 2D 58 4D 4F 90 0B 2E 09 00 00 BB AC 83 32 B8
2020-03-14 17:17:41.912224 > 04 3E 21 02 01 00 00 33 C1 50 34 2D 58 15 02 01 06 11 16 CD FD 08 0C 33 C1 50 34 2D 58 01 04 D9 00 CD 00 BE

Bindkey: 3c9240f7154001f4954c740551a68706

Thank you for your efforts.

Xiaomi flowerpot support (Ropot, HHCCPOT002)

Would it be possible to read data from a smart flowerpot from Xiaomi (Ropot)? I have the HHCCPOT002 version. This product appeared on the market at the same time as Flower Sensor. It only measures the moisture and conductivity of the soil. Has a built-in rechargeable battery.

Originally posted by @kleju00 in #3 (comment)

Having trouble getting LYWSD03MMC working, would appreciate some help

First thing: thank you SO much for all your hard work on this!

I've managed to get my bind_key's using @vevsvevs 's customized Android app (see pairings.txt attached) pairings.txt

I've add the following to my sensors section of my configuration.yaml:

  - platform: mitemp_bt
    encryptors:
      'A4:C1:38:9A:70:D3': '47a343db0e1aede32f5aa350c91d3b88'
      'A4:C1:38:4B:DD:9A': '025ff01e304006e67e2f83dd59f536f0'
      'A4:C1:38:3E:A9:2A': '10217911862739af9accecc28539a349'
      'A4:C1:38:50:05:91': 'e6f906ebfa60a5f27140b0d9c4efefea'

Is the syntax and indentation correct? Your readme seems to show 11 spaces for each mac:bind_key pair but if I don't use 2 spaces the yaml parser complains about incorrect indentation.

The component seems to be working as I see in the HA log that it warns about using a custom mitemp and also when I turn on the debug logging it is outputting the right extra lines, however it doesnt seem to find any Xiaomi devices:

2020-03-22 16:40:12 DEBUG (SyncWorker_4) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1827 hci events, 0 xiaomi devices.
2020-03-22 16:41:13 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1872 hci events, 0 xiaomi devices.
2020-03-22 16:42:14 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1797 hci events, 0 xiaomi devices.
2020-03-22 16:43:15 DEBUG (SyncWorker_2) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1827 hci events, 0 xiaomi devices

I have a USB bluetooth dongle, hci0 is working fine, and when I run "sudo hcitool lescan" I can see data packets from LYWSD03MMC devices. (Cant run it since adding the component tho, as the hci0 interface is in use)

I ran a btmon for ~20 minutes and have zipped the log file and attached.
problem.zip

Anything look off in any of my syntax? Any pointers on where its going wrong?

Thanks, Sunny

You shouldn't use deprecated bluez utilities

Hi,
why are you using deprecated bluez utilities https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=b1eb2c4cd057624312e0412f6c4be000f7fc3617?

I suggest to use dbus api directly instead of hcitool and btmon/btsnoop instead of hcidump.

This is a problem if you use home-assistant on Arch Linux

Parsed: 484 hci events, 0 xiaomi devices

@Magalex2x14 entities checked = no result. Debug log actived:
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] update_ble called
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] Discovering Bluetooth LE devices
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] Time to analyze...
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] Getting data from HCIdump thread
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] HCIdump thread: joining
2020-03-07 00:19:44 DEBUG (Thread-20) [custom_components.mitemp_bt.sensor] HCIdump thread: main event_loop stopped, finishing
2020-03-07 00:19:44 DEBUG (Thread-20) [custom_components.mitemp_bt.sensor] HCIdump thread: Run finished
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] HCIdump thread: joined
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] Spawning HCIdump thread(s).
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] HCIdump thread: Init
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] HCIdump thread: Init finished
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] Starting HCIdump thread for hci0
2020-03-07 00:19:44 DEBUG (Thread-21) [custom_components.mitemp_bt.sensor] HCIdump thread: Run
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] HCIdump threads count = 1
2020-03-07 00:19:44 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] Finished. Parsed: 484 hci events, 0 xiaomi devices.
2020-03-07 00:19:44 DEBUG (Thread-21) [custom_components.mitemp_bt.sensor] HCIdump thread: Connection
2020-03-07 00:19:44 DEBUG (Thread-21) [custom_components.mitemp_bt.sensor] HCIdump thread: Connected
2020-03-07 00:19:44 DEBUG (Thread-21) [custom_components.mitemp_bt.sensor] HCIdump thread: start main event_loop

maybe the problem is 0 xiaomi devices? Why?

Bluetoothctl for lescan?

I am getting crazy to make bluetooth works on Nuc with Proxmox.
The internal bluetooth passing thru works on VM with the "bluetoothctl" command but not with "hcitool lescan".
With VM Debian and bluetoothctl scan on I get the "LYWSD02" device, hcitool lescan does not work :(

Unknown sensor type: 204802

Hi,

I'm running the lateset version of hassio : 0.103.4.
and i have a lot of errors about the component , every second without stopping. errors from logfile:
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 208D01
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 208D01
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 208D01
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 208D01
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 208D01
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 208D01
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 208D01
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 208D01
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 208D01
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802
2019-12-27 17:03:15 ERROR (SyncWorker_5) [custom_components.mitemp_bt.sensor] Unknown sensor type: 204802

I get data from sensors with any issue, expect the errors which increasing the log file constantly.

i've installed the commpents using HACS , i have installed the latets version : Installed: 0.4.0.

in the configuration.yaml i've only have the following configuration :
sensor:

• platform: mitemp_bt

Any idea?

All sensors not found after restart

I previously had one Xiaomi sensor and used this component to integrate, and it worked like a charm. Today I received two more sensors and home assistant were able to find them right after I pressed the pairing button on the sensor. But now when I restart hass.io, only two of the three sensors are created as entities. The third one is found when I manually press the pairing button on the sensor.

Is there any way to overcome this without having to manually press the pairing button on the sensor after a restart?

It is worth to add processing for the lack of necessary utilities

Here are the details of the error in the absence of hcidump:

[homeassistant.components.sensor] Error while setting up platform mitemp_bt
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 150, in _async_setup_platform
    await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
  File "/usr/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/homeassistant/.homeassistant/custom_components/mitemp_bt/sensor.py", line 145, in setup_platform
    scanner.start()
  File "/home/homeassistant/.homeassistant/custom_components/mitemp_bt/sensor.py", line 109, in start
    self.hcidump = subprocess.Popen(['hcidump', '--raw', 'hci'], stdout=self.tempf, stderr=None)
  File "/usr/lib/python3.7/subprocess.py", line 775, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.7/subprocess.py", line 1522, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'hcidump': 'hcidump'

Decimals

In const.py can this be the default on future releases:

DEFAULT_DECIMALS = 1

I don't know why anyone would want 2 decimals but I keep having to change it back each update.

Thank you in advance :)

Sensors not fowarding to Homekit

Hi! I’m using this component in Docker HA. I also added native HomeKit integration from HA documentation. I’m using rounded Xiaomi sensor (first one from photo). I cannot add sensors to Home (Apple) app. All sensors are not readable in app. Why it is not working?

New support Xiaomi Qinping Alarm Clock

Hi,
Given that it's a xiaomi bt device, that there are humidity and temperature sensor, I'd like to have it work with home assistant.
Following the how to, here is what I get in log:

2020-03-10 08:13:12 INFO (SyncWorker_19) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053a625950342d5808e2
[...]
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053a625950342d5808dd
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053a625950342d5808e2
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -31, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e1
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808dd
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e2
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -31, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e1
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e2
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e2
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -32, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e0
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e2
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808dd
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808dd
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e2
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -32, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e0
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808dd
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e2
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808dd
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808dd
2020-03-10 08:14:13 INFO (SyncWorker_12) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053c625950342d5808e2
[...]
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe305876053e625950342d5808dd
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e2902010000625950342d581d020106191695fe585876053f625950342d58658b10407e0000f19c270be2
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e2902010000625950342d581d020106191695fe585876053f625950342d58658b10407e0000f19c270bdd
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808e2
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808e2
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -32, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808e0
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808e2
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808dd
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808e2
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -33, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808df
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808e2
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808dd
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808dd
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808dd
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808e2
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -37, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808db
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -30, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808e2
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -35, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808dd
2020-03-10 08:16:15 INFO (SyncWorker_1) [custom_components.mitemp_bt.sensor] BLE ADV from UNKNOWN: RSSI: -31, MAC: 582D34505962, ADV: 043e1f02010000625950342d58130201060f1695fe3058760540625950342d5808e1

0.5.0 testing

To discuss and test a new data collection method.
0.5.0 trying to close #9 #14 #23 #25

Stops getting new information after couple of hours

Hello, thanks for this great plugin.
Yet, there seems to be an issue, with all of my sensors. I have the LYWSD02, mi flora and mijia round sensors.
The problem is that after a couple of hours it stops getting new information, a reboot temporarily fixes this. I have tried your latest release and even your 0.5.3 beta, but both have the same issue.

Here is my config:
sensor:

• platform: mitemp_bt
  rounding: True
  decimals: 1
  period: 60
  log_spikes: False
  use_median: False
  active_scan: False
  hci_interface: 0

RSSI sensor

Dear developers,
I congrats you for the plugin, I find it well made.
From the version "0.5.3" you added the possibility to see the battery level as an entity, and it's working great.

For the next releases, I suggest to include the same thing for RSSI. It will be nice to have also this information easily available.

thank you.

Device tracker “bluetooth_tracker“ stop working

Device tracker “bluetooth_tracker“ stop working on raspberry pi 3+ when add platform mitemp_bt with error:

Error looking up Bluetooth device
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/bluetooth/bluez.py", line 31, in discover_devices
lookup_class=lookup_class, device_id=device_id)
_bluetooth.error: (4, 'Interrupted system call')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/bluetooth_tracker/device_tracker.py", line 140, in perform_bluetooth_update
devices = await hass.async_add_executor_job(discover_devices, device_id)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/bluetooth_tracker/device_tracker.py", line 62, in discover_devices
device_id=device_id,
File "/usr/local/lib/python3.7/site-packages/bluetooth/bluez.py", line 34, in discover_devices
raise BluetoothError ("error communicating with local "
bluetooth.btcommon.BluetoothError: error communicating with local bluetooth adapter

System | HassOS 3.7
arch | armv7l
dev | false
docker | true
hassio | true
os_name | Linux
python_version | 3.7.5
timezone | Europe/Kiev
version | 0.103.5
virtualenv | false

Configuration.yaml

sensor:
  - platform: mitemp_bt
device_tracker:
  - platform: bluetooth_tracker
    interval_seconds: 10
    consider_home: 180
    new_device_defaults:
      track_new_devices: true

Move communication to BLE devices to pypi package

This custom component will (hopefully) result in an official integration in Home Assistant. First, a couple of bugs need to be fixed, which will take some time.

When that is finished, the next step would be to create a pypi package that handles the communication part of the code. The official home assistant developers documentation states the following:

All communication to external devices or services must be wrapped in an external Python library hosted on pypi.

This issue is created to collect the information we need, and to discuss the development for this.

Note however that @Magalex2x14 is first focusing on bug fixing the current code.

• Instructions to create pypi packages
  https://packaging.python.org/tutorials/packaging-projects/

Progress

• Created and uploaded an example package at the test environment of pypi.

VegTrug Grow Care Garden (GCLS002) support

I was able to get the VegTrug Grow Care Garden sensor (GCLS002) data.

It sends the same data as HHCCJCY01 but just use b'\x20\xBC\x03' instead of b'\x20\x98\x00'.

Cleargrass CGD1 Mijia bluetooth 5.0 support

dump.txt
According to information from the owner: "temp was aprox. around 19,5°C and the humidity about 50%".
at first glance, the messages are very similar to LYWSD03MMC - encrypted?

Rounded value does not return decimal place

The returned value does not always get returned in the same format.

With decimal places as "1", a value that rounds to 20.0 will just be returned as 20.

Installation on Hass.io?

Hi,
very nice idea but is it possible to setup this and run on Hass.io instance?

Regards,
Jacek

No battery information

Hello, I succesfully installed the custom component and it's working great except I don't have the battery sensor. I don't find it in the entity list. Is it a bug or something I miss ?

batt_entities invalid configuration

I have the latest update installed

But can't use batt_entities feature

My configuration:

  - platform: mitemp_bt
    rounding: True
    decimals: 1
    period: 60
    log_spikes: False
    use_median: False
    active_scan: False
    hci_interface: 0
    batt_entities: True

How can I fix that?

Not possible to use RAM for temp file on Hassio

Situation: I want the tempfile to be written to RAM instead of the SD card. A solution is written in the README, but as far as I understand that doesn't work if using RPi with HASSIO.

Question: Is it possible to use the https://pypi.org/project/memory-tempfile/ library and default write to memory instead of the SD card?

Unknown Sensor Typ

For about a week now, the contact with the Xiaomi BT Temp sensors has stopped working after a few hours.

Restarting the RPI will solve the problem again for the next few hours. The same behavior was always with the old integrate mitemp plugin from HomeAssistant.

I don't know if that came without an update or through an update from Home Assistant, or Hassio FW itself or through the larger HACS update.

Since I installed HACS in December and used the mitemp sensor plugin from there everything has worked wonderfully.

The logs say:
Unknown sensor type: 20AAEE (the name / SN of the sensor)
"Date" custom_components / mitemp_bt / sensor.py (ERROR)

Hassio / Home Assistant runs on a Raspberry Pi 3 B

Sensor entity attributes contain spaces in name

I think it is not valid that entities created by component have attributes name containing spaces: "sensor type", "last packet id", "last mean of".
It's not consistent with others, and also makes impossible to use those attributes in yaml.

No module named 'aioblescan'

I tried to configure my new LYWSD03MMC thermomenters, so I upgraded mitemp_bt to last version, but my already working thermometer LYWSDCGQ stop working also (no devices listed in sensors).
If I put back my previous version of mitemp_bt, it is working again.

So I tried to upgrade hassio. I upgraded to:

arch	armv7l
dev	false
docker	true
hassio	true
os_name	Linux
os_version	4.19.106-v7
python_version	3.7.7
timezone	Europe/Prague
version	0.107.7
virtualenv	false

But now, when I try to check configuration, I'm getting error:
Platform error sensor.mitemp_bt - No module named 'aioblescan'

Thanks for help.

Lukas

No hci interface? Hass.io..

I take it this component doesn't work with Hass.io? I can't run any hci commands..

Not pulling data from Veg Trung Sensor.

This component works great for my veg trung sensors with Mac addresses starting with 80:EA:CA:88... however one of my sensors has a MAC address starting with C4:7C:8D:67... and for some reason this integration doesn’t make a sensor for it. Also this integration doesn’t seem to be able to pull battery %, like the MiFlora component can. Tried both configuration options.

Poor performance after moving hassio to ssd

I know it may sound strange, and I don't see a direct relationship, but after moving my hassio installation from sd to an ssd, I have noticed a great loss of performance. I receive much less data from my sensors. Is this something known?

Before change, I had around 30 readings each 2 minutes, but now, some of sensors don't update and others get 1 packet each hour.

Attribute hass is None error

Hi @Magalex2x14

I now have an issue myself. After updating to 106.0/1/2 i get the following error after the restart.

Error during Bluetooth LE scan: Attribute hass is None for <Entity mi t_4C65A8DDB89B: 16.3>

I'm not sure what is going on exactly. The sensor works fine.