Determine hardware version of LYWSD03MMC B1.6 released since 2025.03

[wta12]

Since new version of LYWSD03MMC B1.6 since 03.2025 has very high energy usage, I wonder how to determine is the new version with high consumption or not.
I heard web flash portal has cached and doesn't recognize hardware version well after flashing but can we get hardwire info from python interface ?

[pvvx]

The firmware versions offered feature HW auto-detection.
The HW version number in BLE has a standard UUID that can be read on any Bluetooth adapter.
The firmware versions offered and the original Xiaomi firmware versions have this information.
The HW version number can also be viewed in Windows Chrome by enabling the BLE monitor and entering the following line: "chrome://bluetooth-internals."

[wta12]

found service ID and values from chrome:// as below. Which service ID to read for HW version number ? Reference only is fine. I will try to add hardware version to python interface if it's not available.

[pvvx]

Google: AI Review:
UUID 0x2a27 refers to the Bluetooth SIG Hardware Revision String characteristic UUID, a 128-bit identifier used in the Device Information Service (180A) to provide a UTF-8 string representing the hardware revision of a device. This standard characteristic allows devices to report their hardware version as a human-readable string.

[pvvx]

Since new version of LYWSD03MMC B1.6 since 03.2025 has very high energy usage, I wonder how to determine is the new version with high consumption or not.

Determined by any PowerProfiler when measuring consumption.

I heard web flash portal has cached and doesn't recognize hardware version well after flashing but can we get hardwire info from python interface ?

After updating the firmware to a different version, the MAC address of the BLE device does not change. Cache binding is carried out via the MAC of the BLE device.
According to the BLE standard, the system or adapter must cache a table of UUIDs of connected BLE devices. It does not matter which API you use to read data from the BLE device.
If errors occur, upon reconnecting, the system must clear the cache data for the current BLE device. On Linux, you must delete the BLE device cache data directory.
On other systems, a reboot of the system or BLE adapter is recommended, as the adapter itself may also cache data.
In Windows, the BLE device UUID table and files are cached by Chrome Explorer, and a restart is often sufficient.

The main problems only occur on Linux with Bluez. You have to access the file system and delete Bluez cache files, which are overwritten and appended to each time you actively scan for BLE devices, causing premature wear on the SSD...

Look Google: "bluez clear cache"

[wta12]

Determined by any PowerProfiler when measuring consumption.

• if the Flasher.html shows B1.5 after flashing from original, I don't need to worry about 1.6 new (SPI LCD) , correct ?
• Maybe earlier version of firmware (5.2 etc) returns blank screen is enough to differentiate between new and old B1.6 HW ?
  Not sure if every LYWSD03MMC B1.6 since 03.2025 using SPI LCD or kind of counterfeit products from Aliexpress ?? I have recently purchased a batch of six LYWSD03MMC from Taobao (Chinese dometic estore) before your updates about new HW - will report back if they are new one.

[pvvx]

B1.6(new)	SPI	0x44 (SHT4x)	Custom HW: B1.1

Added to README:
To eliminate the confusion created by Xiaomi with identical HW numbers, the internal number B1.1 is used for new B1.6 versions in the alternative firmware.