LYWSD03MMC support (implemented since 0.6.0)

[Magalex2x14]

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!

[JJussi]

Have you checked: https://habr.com/ru/post/452558/ (if needed google translate do good work)

I have LYWSD02 and here is what it sending:

hcidump --raw | grep -v "3F 58 70"
HCI sniffer - Bluetooth packet analyzer ver 5.50
device: hci0 snap_len: 1500 filter: 0xffffffff

04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 DF
04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 D8
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 C5
04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 DF
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 CD
04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 D9
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 CE
04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 CF
04 3E 28 02 01 00 00 78 B8 72 7D 5B 3F 1C 02 01 06 03 02 1A
18 14 16 95 FE 70 20 5B 04 4F 78 B8 72 7D 5B 3F 09 06 10 02
4A 01 E1
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 C4
04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 CC
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 C4
04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 CF
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 C4
04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 C9
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 CE
04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 DF
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 BF
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 C3
04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 CF
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 C5
04 3E 2B 02 01 03 01 20 AF 16 2D C1 2E 1F 1E FF 06 00 01 09
20 02 BE C7 A9 2E B4 17 E3 07 73 B4 62 81 C9 1F 5B 17 73 F8
3A F3 03 F7 75 C9
04 3E 2B 02 01 00 00 0B 32 AD 1A B1 CC 1F 02 01 1A 1B FF 75
00 42 04 01 01 6F CC B1 1A AD 32 0B CE B1 1A AD 32 0A 01 98
00 00 00 00 00 D4

[JJussi]

Sorry, this capture have this "all ready" supported (round one) sensor on the range... But you can easily filter it away...

https://www.dropbox.com/s/kbk98bzyue84fu5/dump.txt?dl=0

Values where 33% and 26,7C thru whole capture time.

[Magalex2x14]

Russian is my native language ) Yes, I saw this article. The fact is that its author uses a connection to the sensor. This is not our method ) We parse broadcast data, which greatly saves battery power and gives other pluses as a result from processing a continuous data stream (look at the description of the use_median option in readme.md, for example).

[JJussi]

Yes, I know that you use a different method, but of course, received data should be at same format. So if you can "inject" those hcidump results to your code, you should see if your code works. Hopefully, my dumps help...

[langerhans]

I just found another model that seems to be fairly new: LYWSD03MMC
Some shops have it for 18$ for three of them which is pretty cheap. Sadly seem to be sold out right now. Unsure yet if it broadcasts similarly to the other devices. I plan to buy some and will let you know when I get a chance to play with them.
Also trying to find the MiFlora for cheap somewhere, but no luck apart from Amazon around here.

[Magalex2x14]

I pushed pre-release with other sensors support. Installation in HACS is also available if you enable "Show betas" on the integration page.
A MiFlora dump is still needed to implement support for other MiFlora sensor features besides temperature.
Thanks @JJussi and Sergey Sazonov for LYWSD02 and CGG1 dumps!

[Ernst79]

I can only confirm that the original sensor still works fine with the new code. I new attributes (rssi and sensor type are also available). I don't have any of the other sensors, so cannot test that.

If you are finished, I can do a final review if you want. But you have to make a PR than.

[Magalex2x14]

There is still work to do after we have MiFlora dump - at least new classes for its sensors will be needed. While I would not like to do PR in the master. Plus there are a few more details that I would like to correct before being released to the master. After that, of course, we will do everything right.

[JJussi]

Thank you! I can confirm that LYWSD02 works perfectly!

[Quppa]

I just found another model that seems to be fairly new: LYWSD03MMC
Some shops have it for 18$ for three of them which is pretty cheap. Sadly seem to be sold out right now. Unsure yet if it broadcasts similarly to the other devices. I plan to buy some and will let you know when I get a chance to play with them.
Also trying to find the MiFlora for cheap somewhere, but no luck apart from Amazon around here.

I wonder if it's this model? If so, I have one on the way - happy to share a dump of its data once it arrives (unless someone else beats me to it).

[JJussi]

Looks like.. As it says there:

Brand | XIAOMI Mijia
Model | LYWSD03MMC

[Magalex2x14]

I noticed that the LYWSD02 and 03 sensors do not show the battery status on the display... And the fact is that 02 does not broadcast it. Curious, will 03 do it?

P.S. Tomorrow I expect to get a MiFlora sensor, and on the weekend I plan to finish with its full support.

[Magalex2x14]

I just pushed v0.4.0-beta.2 pre-release with MiFlora full support.
I found that MiFlora does not broadcasts battery status (googled it - people write that it was disabled in the latest firmware versions). Another strange thing is that MiFlora repeats the measurement data several times (the packets are different, rssi is different, but the packet_id is identical) - I had to check this before processing. Other sensors have never sent me packets with the same id. As a result, it turned out that MiFlora updates the data once a minute approximately...

[ma-zal]

Can you mention in documentation (in README), how often devices are broadcasting the sensors value? Based on your investigation you probably know it. :-) It will be also great to mention, that the broadcasting interval is fixed (cannot be changed).

I am asking for this info, because my LYWSDCGQ is reporting every minute - and I am confused if it is correct default behavior, or it will drain the baterry fast.

[Ernst79]

Do you mean the interval the data is updated in Home Assistant? This is mentioned in the README and is a setting (period)

Period
(positive integer)(Optional) The period in seconds during which the sensor readings are collected and transmitted to Home Assistant after averaging. Default value: 60

So, yes, 1 minute is default, but you can change it if you want.

Or do you mean the interval the actual sensor sends out it's data? I don't think you can change the interval LYWSDCGQ is actually sending data, am I right @Magalex2x14 ?

[ma-zal]

This is mentioned in the README and is a setting (period)

But as I understand, this period parameter is just filtering the incomming data to avoid too often updating (and storing) in Home-Assistant database. But this period parameter is not affecting, how often the Xiaomi device is broadcasting data via BLE. So Xiaomi device has no idea, that some period value is defined in integration script, and Xiaomi still reporting with same speed. Is it correct?

... I am asking for documentation of BLE data broadcasting intervals.

[Magalex2x14]

It may still be worthwhile to clarify the sensor broadcast interval and the component measurement period (period option)... For example, my three LYWSDCGQs send 20-25 unique messages at RSSI -75 ..- 70 dBm. With the option period = 60, the component accumulates 20-25 messages received per minute, and after the period expires, averages them and updates the sensor status in HA. The period does not affect the consumption of the sensor. It only affects the HA sensor update rate and the number of averaged values.

P.S. Ernst is wright, we can't change sensor broadcasting interval.
P.P.S. Yes, ma-zal, correct.

[Magalex2x14]

I am asking for documentation of BLE data broadcasting intervals.

Why not... I'm sure of the broadcast interval LYWSDCGQ and MiFlora that I have. For the rest, statistics from users are needed (especially since the sensor attributes have the number of received packets for the measurement period - "last mean of" or "last median of").

[Ernst79]

@Magalex2x14 In the README (first section), you mentioned the following:

this custom component is parsing the Bluetooth Low Energy packets payload that is emitted each second by the sensor

Not sure if this is correct

[Magalex2x14]

Yes, that’s true, but not quite. In fact, it sends about every second, but not all packets contain measurements, and, as it turned out in the case of MiFlora, not all of them are unique... We need to change the wording, yes...

[Ernst79]

I tried to check the "last mean of" value, but I now see I have the same issue as in #12. The sensor had stopped yesterday. Apparently not a dead battery, as I thought yesterday.

[Ernst79]

Ok, did a check.

• LYWSDCGQ Sensor at 20 cm from raspberry pi,
• rssi = -58 dBm,
• I get between 19 till 24 readings (varies a bit) per 60 seconds (last mean of).

[valsergi]

Someone help me, with this error, I have achieved everything necessary, thanks to the help of this forum, but I cannot get it to link with HA

Thank´s

As seen in the image, apparently the permissions to write are ok, but I have problems with the connection, here I leave the HA log

[stu531]

Yep, got this working too - on a set of 3 LYWSD03MMCs, with a Rasp Pi 3. Thanks @Magalex2x14 !

[Griizly]

Hello, I use a RPI4 with hassio, already found the bindkey using the vevs mi home app, inserted data in my configuration.yaml, waited more than 1 hour but still no sign of the sensor in HA
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
    batt_entities: False
    encryptors:
      'A4:C1:38:81:39:9A': 'fc2b392e7e785de2aa959710ce3b274b'
    report_unknown: False
    whitelist: False

I'm not able to run the sudo setcap command but i'm running hassio so I think it's normal.
Using bluetoothhctl scan on command in ssh i managed to see this line so the bluetooth saw the device

[bluetooth]# scan on                                                                                                                                                                                                                 
Discovery started
[CHG] Controller DC:A6:32:56:9B:3F Discovering: yes
[CHG] Device 3C:BD:3E:C2:FB:8F RSSI: -48
[CHG] Device A4:50:46:3C:B0:DE RSSI: -70
[CHG] Device 3C:BD:3E:C2:FB:8F RSSI: -56
[CHG] Device 3C:BD:3E:C2:FB:8F RSSI: -47
[CHG] Device 3C:BD:3E:C2:FB:8F RSSI: -57
[DEL] Device 3C:BD:3E:C2:FB:8F Mi Box
[DEL] Device A4:50:46:3C:B0:DE POCOPHONE
[NEW] Device 3C:BD:3E:C2:FB:8F Mi Box
[NEW] Device A4:50:46:3C:B0:DE POCOPHONE
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Device A4:50:46:3C:B0:DE UUIDs: 00000000-0000-0000-0000-000000000000
[NEW] Device A4:C1:38:81:39:9A LYWSD03MMC

any idea of what I miss ? Thanks !

[liquid-motion]

do root needed to install your mod?

No. But you have to remove the original app first.

using the MiHome Mod (not sure if is the same told by @vevsvevs) from this telegram repo: https://t.me/xCrepository xCapRepo

No, this is an Italian mod, which is consists of parts furtively "borrowed" from my work...
My mod lives here (please use Google Translate), new version with bind_key logging already published :) Just install the mod, create folder /your_interlal_storage/vevs/logs/ and pair your BLE device - file pairings.txt with a corresponding data will be created.

I hate bumping this closed topic but I had a problem while trying to use the mod apk and spent maybe 3 hours trying to figure out.

@vevsvevs you should make a note that you need to manually give your mod apk permission to write to storage. It didn't prompt asking this and wasn't making the pairing.txt file. I spent 3 hours smashing my head against a wall then it just dawned on me to try this. I got the file and and it has the keys now.

@vevsvevs And please add to this note that you have to create these folders (vevs/logs) yourself, before pairing. I spent 2 hours smashing my head against a wall, but now I have my keys!

[nalt]

Hi,
is there no way to get the key simply from the Android app data folder, /data/user/…/com.xiaomi.smarthome/?

[Krojack]

Hi,
is there no way to get the key simply from the Android app data folder, /data/user/…/com.xiaomi.smarthome/?

There is not. It's an encryption key so the whole point is to keep it private.

Just use the modified app and follow the instructions to create the folders. Once you're done then you can uninstall the app.

[stevoh6]

do root needed to install your mod?

No. But you have to remove the original app first.

using the MiHome Mod (not sure if is the same told by @vevsvevs) from this telegram repo: https://t.me/xCrepository xCapRepo

No, this is an Italian mod, which is consists of parts furtively "borrowed" from my work...
My mod lives here (please use Google Translate), new version with bind_key logging already published :) Just install the mod, create folder /your_interlal_storage/vevs/logs/ and pair your BLE device - file pairings.txt with a corresponding data will be created.

I hate bumping this closed topic but I had a problem while trying to use the mod apk and spent maybe 3 hours trying to figure out.
@vevsvevs you should make a note that you need to manually give your mod apk permission to write to storage. It didn't prompt asking this and wasn't making the pairing.txt file. I spent 3 hours smashing my head against a wall then it just dawned on me to try this. I got the file and and it has the keys now.

@vevsvevs And please add to this note that you have to create these folders (vevs/logs) yourself, before pairing. I spent 2 hours smashing my head against a wall, but now I have my keys!

You are awesome, thank you for saving my time :-) I spend only hour until i find yours comment.

[valpackett]

Also you need to fully restart (force stop) the modded app if you've created vevs/logs after installing it.

[JsBergbau]

There is now a very easy way to get the bind key, see mKeRix/room-assistant#277

[redyuan43]

Hi guys, can you please help me configure my LYWSD03MMC. I have installed app from @vevsvevs and I see token for the device but it's 24 characters. How to find the 32 one?

I have the same issue too. Firmware:1.0.0_0109. Hardware is: LYWSD03MMC

[batja84]

Hi guys, can you please help me configure my LYWSD03MMC. I have installed app from @vevsvevs and I see token for the device but it's 24 characters. How to find the 32 one?

I have the same issue too. Firmware:1.0.0_0109. Hardware is: LYWSD03MMC

Just use TelinkFlasher web interface from here https://github.com/atc1441/ATC_MiThermometer

[simfun]

Hi guys, can you please help me configure my LYWSD03MMC. I have installed app from @vevsvevs and I see token for the device but it's 24 characters. How to find the 32 one?

I have the same issue too. Firmware:1.0.0_0109. Hardware is: LYWSD03MMC

You need to find the bind_key not the token.

[Petro31]

do root needed to install your mod?

No. But you have to remove the original app first.

using the MiHome Mod (not sure if is the same told by @vevsvevs) from this telegram repo: https://t.me/xCrepository xCapRepo

No, this is an Italian mod, which is consists of parts furtively "borrowed" from my work...
My mod lives here (please use Google Translate), new version with bind_key logging already published :) Just install the mod, create folder /your_interlal_storage/vevs/logs/ and pair your BLE device - file pairings.txt with a corresponding data will be created.

I hate bumping this closed topic but I had a problem while trying to use the mod apk and spent maybe 3 hours trying to figure out.
@vevsvevs you should make a note that you need to manually give your mod apk permission to write to storage. It didn't prompt asking this and wasn't making the pairing.txt file. I spent 3 hours smashing my head against a wall then it just dawned on me to try this. I got the file and and it has the keys now.

@vevsvevs And please add to this note that you have to create these folders (vevs/logs) yourself, before pairing. I spent 2 hours smashing my head against a wall, but now I have my keys!

@vevsvevs And please add to this note that in the MiHome mod you have to navigate to Profile -> Experimental features, then turn on Write to custom log files, before pairing. I spent 1 hour smashing my head against a wall, but now I have my keys!

[Ernst79]

Added your notes to the faq, thanks.

[uncle-wong]

do root needed to install your mod?

No. But you have to remove the original app first.

using the MiHome Mod (not sure if is the same told by @vevsvevs) from this telegram repo: https://t.me/xCrepository xCapRepo

No, this is an Italian mod, which is consists of parts furtively "borrowed" from my work...
My mod lives here (please use Google Translate), new version with bind_key logging already published :) Just install the mod, create folder /your_interlal_storage/vevs/logs/ and pair your BLE device - file pairings.txt with a corresponding data will be created.

I hate bumping this closed topic but I had a problem while trying to use the mod apk and spent maybe 3 hours trying to figure out.
@vevsvevs you should make a note that you need to manually give your mod apk permission to write to storage. It didn't prompt asking this and wasn't making the pairing.txt file. I spent 3 hours smashing my head against a wall then it just dawned on me to try this. I got the file and and it has the keys now.

@vevsvevs And please add to this note that you have to create these folders (vevs/logs) yourself, before pairing. I spent 2 hours smashing my head against a wall, but now I have my keys!

What is the full path of vevs/logs?

[antoweb]

do root needed to install your mod?

No. But you have to remove the original app first.

using the MiHome Mod (not sure if is the same told by @vevsvevs) from this telegram repo: https://t.me/xCrepository xCapRepo

No, this is an Italian mod, which is consists of parts furtively "borrowed" from my work...

My mod lives here (please use Google Translate), new version with bind_key logging already published :) Just install the mod, create folder /your_interlal_storage/vevs/logs/ and pair your BLE device - file pairings.txt with a corresponding data will be created.

@vevsvevs Hello i have downloaded the new version of modded xiaomi home but now the vaccum log are not in /vevs/logs/mio but in /vevs/logs/rcptalk and i cant see anymore the action "aiid":3 for retrieve my room ids. ANy suggetions?