wholly crap it worked I not sure why but I finally got the Stream VPN installed and was able to get the bind_key OK how do I get a more meaningful name assigned to each of the encryptors rather than mi_t_a4c1380dfb2b
Congratulations )
Home Assistant -> Configuration -> Entities, search by name and click on entity which you want to change.
Have you ever seen this on my rpi console this message just keeps scrolling across the screen bluetooth hci0 Frame reassembly failed (-84) also seeing SCO packet for unknown connection handle and advertising data len corrected the later two are much fewer
One more question is it possible to get the battery level from the LYWSD03MMC
again thanks for all your help
Hi
I have 1x LYWSDCGQ and 2x HHCCJCY01.
The round LYWSDCGQ works fine, no issues.
But my 2 HHCCJCY01 (mi flora) dosnt, and im not sure what im missing.
If i do a scan on the host, i can find it:
[NEW] Device C4:7C:8D:61:FF:B9 Flower mate
But mitemp only finds 1 device (temp sensor):
2020-04-08 10:42:20 DEBUG (SyncWorker_1) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1415 hci events, 1 xiaomi devices.
Configuration:
sensor:
- platform: mitemp_bt
decimals: 1
They worked fine with the old bluethooth intergration in HA with the following:
sensor:
- platform: miflora
mac: 'C4:7C:8D:61:FF:B9'
median: 2
adapter: hci0
(which is removed from the running conf)
Assistance Requested
This is a common problem with the bluetooth subsystem on raspberry.
is it possible to get the battery level from the LYWSD03MMC
Of course, there is a special option for this - batt_entities. Everything is described in the documentation.
Please look at this post. Often all problems with these sensors are solved by their activation in the official application and firmware update.
Thanks I see where I went wrong when adding to lovelace I used the same nameing convention I was just using ‘b’ instead of ‘batt’. whats your knowledge on other bluetooth stuff I have some xiaomi window/door sensors and I used a usb bluetooth dongle ‘Nortek’ but a couple seem to be just out of range any way to increase bluetooth signal strength?
As far as I know, door and window sensors in the Xiaomi ecosystem are ZigBee-devices, you cannot receive data from them using a bluetooth dongle.
All my knowledge of the Xiaomi ecosystem (regarding bluetooth) is limited to the list of devices supported by my component.
Some methods for expanding bluetooth coverage are described in our FAQ.
Hi thanks for this tip, it worked after updating the miflora hardware.
For any having the same issue as me, im running a chinese “locked” version of the miflora, so i wasnt able to update though the normal “flower care” app, eventhough setting it to china.
So i installed the “mi home” app, in settings set it to “china” and then i was able to pair it within mi-home, and update it
Thanks again!
my mistake it is a ZigBee USB controler but while checking logs I found Log Details (ERROR)
Logger: custom_components.mitemp_bt.sensor
Source: custom_components/mitemp_bt/sensor.py:654
First occurred: April 7, 2020, 8:21:13 PM (912 occurrences)
Last logged: 10:22:36 AM
- token: 3e2a0201
- nonce: 2bfb0d38c1a45b05eb65a604
- encrypted_payload: 930e003c6765a6043e2a0201
- cipherpayload: 930e003c67
- Decryption failed for A4C1380DFB2B, decrypted payload is None
Should I worry about this
This is a decryption error message.
As a rule, it says that the key specified in the encryptors option is not suitable for decryption.
That is, you have the wrong key for the sensor with the address A4C1380DFB2B.
Before you take action, make sure that this error continues to be repeated at the moment. Maybe it was relevant only during your experiments?
0.6.5 version released.
Changes:
- support for JQJCY01YM Xiaomi Honeywell Formaldehyde Sensor
(about 50 messages per minute total: temperature + humidity + formaldehyde + battery level) -
decimals: 1
by default (instead ofdecimals: 2
) - some multithreading optimizations
All my sensors are working fine but I don’t know if it is related but all my Amazon echo devices became unavailable so I deleted the integration for Alexa_media and redid it but none of my echo devices were discovered
As far as I can see, this integration does not use bluetooth, it is a cloud-based integration. Therefore, I think the problem is not related to the component discussed here.
BUT!
If the problem appeared after updating the component to 0.6.4, then update it again to 0.6.5.
Almost immediately after 0.6.4, I released 0.6.5, which fixes problems with HA loading on some systems. The problem is very strange, was absent on my systems, but several users wrote about the problem at once, so make sure you have 0.6.5.
Thanks a lot, you helped me on solving the issue !! Very appreciated ! Thanks
Just to make sure, there is nothing device specific that needs to be added to the configuration for HHCCJCY01 (MiFlora)? I have tried settings this up multiple times but no sensors are detected. I followed steps 2-6 carefully (as step 1 is not needed and not possible? on Hass.io)
So far, I was only successful with the MiFlora integration.
You don’t need to add anything special to the configuration for MiFlora sensor.
Most often, MiFlora does not work out of the box for two reasons:
- it is not added to the official app;
- old firmware;
Pay attention to this post and further on the link in it.