LYWSD03MMC-z

[Vortecsz]

After flashing the LYWSD03MMC with z03mmc 1.1.0 the device connect's to zigbee2mqtt.
Flashed first from OTA and after from UART but the problem persist.
The only available value is the battery, it is strange because the device is called: LYWSD03MMC-z
Other's users have also this problem: https://www.reddit.com/r/homeassistant/comments/1aok4l4/help_im_stuck_with_an_unknown_zigbee_device/

[devbis]

Hi! You haven't flashed firmware from this repo but from a fork https://github.com/pvvx/ZigbeeTLc/

You can follow up with that fw, or use local ota to convert to my firmware using local OTA (z2m or ZHA) and 1141-020a-11003001-z03mmc.zigbee.zip as new firmware.

[toelke]

I had the same issue. This is what I did:

1. I copied the file custom_devices_diy.js from the running docker container: docker cp zigbee2mqtt:/app/node_modules/zigbee-herdsman-converters/devices/custom_devices_diy.js .
2. I modified that file by replacing LYWSD03MMC with LYWSD03MMC-z for zigbeeModel.
3. I mounted that modified file into the same place in the docker-container docker run ... -v ./custom_devices_diy.js:/app/node_modules/zigbee-herdsman-converters/devices/custom_devices_diy.js ...
4. Now zigbee2mqtt would correctly detect the device, but obviously that is a bit brittle.

When I do an OTA now, the device is updated to a newer version of the fork :-(

I tried adding the zip-file you linked to a local index, but z2m does not pick up that file but still the fork. Do you know how I can force z2m to OTA your file?

configuration.yaml:

ota:
    zigbee_ota_override_index_location: my_index.json

my_index.json

[{
        "url": "1141-020a-11003001-z03mmc.zigbee",
        "force": "true"
}]

[devbis]

Your ota configuration looks good. It depends on errors that you have trying to update.
z2m asks device for possible manufacturer and image type and then checks its index.
Did you unzip the file? Is it located in the same folder as configuration.yaml and my_index.json?

[toelke]

It is, yes.

I see the message

2024-02-16 10:55:35 OTA: Images currently unavailable for device 'LYWSD03MMC-z', hardwareVersion '15', manufacturerName Xiaomi, {"fieldControl":0,"manufacturerCode":56085,"imageType":515,"fileVersion":285224961}'

[drag0n141]

Hey,
i have the same problem, after flashing the 1141-020a-11003001-z03mmc.zigbee.zip file it has now the same version as my others. But is shows still the "LYWSD03MMC-z" name and not all functions. Is it possible to reflash it without the -z?

[devbis]

z2m caches device properties if mac address wasn't changed. You can reread it via dev console, or remove device, restart z2m and join the device again.

[toelke]

Indeed. Dev console -> cluster genBasic -> attribute modelId -> read.

Thanks!

[Milinator]

Hi! You haven't flashed firmware from this repo but from a fork https://github.com/pvvx/ZigbeeTLc/

You can follow up with that fw, or use local ota to convert to my firmware using local OTA (z2m or ZHA) and 1141-020a-11003001-z03mmc.zigbee.zip as new firmware.

I was having the exact same issue and I was trying to flash different OTA updates (but they never showed up, because they were probably/obviously not the right ones). Your update file showed up immediately. Just out of curiosity: How did you know the right update firmware file?

[MathijsG]

I have a hard time downgrading to BLE again. I tried all available files, according to this website:

But I always get this:

Tried the Dev console thing mentioned here as well. How can I downgrade/switch to BLE when I already have the latest zigbee version now?

These are it's values:

I mainly want to go back to BLE, because the zigbee firmware doesn't seem to properly update the temperature back. Only when I manually press the refresh arrows in Zigbee2mqtt for temperature, it get's updated properly. Already set the reporting times and values very low, but no luck.

[MathijsG]

In the end I went back to Bluetooth via: https://github.com/devbis/z03mmc?tab=readme-ov-file#return-to-bluetooth-firmware

Using the file: https://github.com/devbis/z03mmc/blob/master/assets/db15-0203-99993001-ATC_v46.zigbee

Why did I went back? Well, the temperature almost never seemed to update. It kept the current temperature until I clicked on the refresh icons of the temperature in Zigbee2mqtt.