[New device support]: LYWSD03MMC-z #21467

TheGroundZero · 2024-02-19T11:28:15Z

Link

https://www.zigbee2mqtt.io/devices/LYWSD03MMC.html

Database entry

{
  "id": 25,
  "type": "EndDevice",
  "ieeeAddr": "0xa4c138b32f2fcff4",
  "nwkAddr": 47596,
  "manufId": 4417,
  "manufName": "Xiaomi",
  "powerSource": "Battery",
  "modelId": "LYWSD03MMC-z",
  "epList": [
    1
  ],
  "endpoints": {
    "1": {
      "profId": 260,
      "epId": 1,
      "devId": 770,
      "inClusterList": [
        0,
        1,
        3,
        32,
        1026,
        1029
      ],
      "outClusterList": [
        25,
        516
      ],
      "clusters": {
        "genBasic": {
          "attributes": {
            "modelId": "LYWSD03MMC-z",
            "manufacturerName": "Xiaomi",
            "powerSource": 3,
            "zclVersion": 3,
            "appVersion": 0,
            "stackVersion": 2,
            "hwVersion": 20,
            "dateCode": "20240211",
            "swBuildId": "3001-0120"
          }
        },
        "genPollCtrl": {
          "attributes": {
            "checkinInterval": 14400
          }
        },
        "genPowerCfg": {
          "attributes": {
            "batteryPercentageRemaining": 200,
            "batteryVoltage": 31
          }
        },
        "msTemperatureMeasurement": {
          "attributes": {
            "measuredValue": 2361
          }
        },
        "msRelativeHumidity": {
          "attributes": {
            "measuredValue": 5412
          }
        }
      },
      "binds": [
        {
          "cluster": 32,
          "type": "endpoint",
          "deviceIeeeAddress": "0x00124b0024c2cfef",
          "endpointID": 1
        },
        {
          "cluster": 1,
          "type": "endpoint",
          "deviceIeeeAddress": "0x00124b0024c2cfef",
          "endpointID": 1
        },
        {
          "cluster": 1026,
          "type": "endpoint",
          "deviceIeeeAddress": "0x00124b0024c2cfef",
          "endpointID": 1
        },
        {
          "cluster": 1029,
          "type": "endpoint",
          "deviceIeeeAddress": "0x00124b0024c2cfef",
          "endpointID": 1
        }
      ],
      "configuredReportings": [
        {
          "cluster": 1,
          "attrId": 33,
          "minRepIntval": 3600,
          "maxRepIntval": 65000,
          "repChange": 10,
          "manufacturerCode": null
        },
        {
          "cluster": 1026,
          "attrId": 0,
          "minRepIntval": 10,
          "maxRepIntval": 3600,
          "repChange": 100,
          "manufacturerCode": null
        },
        {
          "cluster": 1029,
          "attrId": 0,
          "minRepIntval": 10,
          "maxRepIntval": 3600,
          "repChange": 100,
          "manufacturerCode": null
        }
      ],
      "meta": {}
    }
  }

Comments

I have flashed two LYWSD03MMC in the past without issue. But those have show a ZigbeeModel of "LYWSD03MMC" while this one shows "LYWSD03MMC-z"

Flashed with @pvvx's flasher (https://pvvx.github.io/ATC_MiThermometer/TelinkMiFlasher.html)
IIRC the firmware version was Z03MMC_0120.bin.

Previous flashes were with 0119 but have since been upgrade via Z2M.
This was also the first flash from a device out-of-the-box with the Mi firmware, while the previous devices were flashed with PVVX's BLE firmware prior to flashing to the Zigbee firmware.

Logs show:

Exception while calling fromZigbee converter: Definition 'LYWSD03MMC-z' has not endpoint defined}

External definition

# Generated by DevTools, unaltered
const {batteryPercentage, temperature, humidity} = require('zigbee-herdsman-converters/lib/modernExtend');

const definition = {
    zigbeeModel: ['LYWSD03MMC-z'],
    model: 'LYWSD03MMC-z',
    vendor: 'Xiaomi',
    description: 'Automatically generated definition',
    extend: [batteryPercentage(), temperature({"endpoints":["1"]}), humidity({"endpoints":["1"]})],
    meta: {},
};

module.exports = definition;

The text was updated successfully, but these errors were encountered:

pvvx · 2024-02-19T11:45:04Z

pvvx/ZigbeeTLc#58 (comment)
https://github.com/pvvx/ZigbeeTLc/blob/master/z2m/lywsd03mmc-z.js

TheGroundZero · 2024-02-19T21:33:25Z

So I downloaded lywsd03mmc-z.js to My Z2M config folder, then added it as an External Converter, and removed and re-joined my device.
That seems to have done it for that sensor.

It does appear my 2 other, previously functional, sensors are not throwing errors.
I'll remove those and re-join them as well and see if that fixes things.

(I added the ZigbeeTlc reference in the Description so I don't forget where I got the custom fw from 😅)

BartCardan · 2024-02-21T22:33:39Z

Just because I am curious: what is changed in the latest release that we need to add a external converter?

TheGroundZero · 2024-02-22T09:22:24Z

Just because I am curious: what is changed in the latest release that we need to add a external converter?

From what I understood, Z2M picks the device config based on the Zigbee Model.
The config for the "LYWSD03MMC" Zigbee Model maps to the config for the devbis firmware. The config for the ZigbeeTLc firmware is a bit different, so you'd run into issues with missing or nonfunctional sensors etc.
So to differentiate devices flashed with ZigbeeTLc, they now identify as "LYWSD03MMC-z", but no config has been mapped to this Device Model in Z2M yet.
I suppose the External Converter is a temporary fix until the device is officially supported by Z2M.

Milinator · 2024-02-23T21:52:01Z

I added the device with lywsd03mmc-z.js and it is basically working, but it's reporting only (exactly) every hour. That's why I want to revert back to BLE and then reflash the zigbee firmware with a given interval. Problem is: I can't go back to BLE, I'm following this blog post: https://smarthomescene.com/guides/how-to-setup-zigbee2mqtt-local-ota-index/

Have done everything as described, but there is no update available in Z2M. Maybe that's also caused by the "z" at the end? Any help'd be appreciated, I don't really want to buy a UART dongle...

Milinator · 2024-02-24T16:27:06Z

I added the device with lywsd03mmc-z.js and it is basically working, but it's reporting only (exactly) every hour. That's why I want to revert back to BLE and then reflash the zigbee firmware with a given interval. Problem is: I can't go back to BLE, I'm following this blog post: https://smarthomescene.com/guides/how-to-setup-zigbee2mqtt-local-ota-index/

Have done everything as described, but there is no update available in Z2M. Maybe that's also caused by the "z" at the end? Any help'd be appreciated, I don't really want to buy a UART dongle...

Fixed with this update file
devbis/z03mmc#118 (comment)

dasEtwasmitPunkten · 2024-03-02T14:34:00Z

@Koenkk I saw this device wasn't included in the last release. Is there a plan to integrate it in one of the next versions?
thanks in advance

Koenkk · 2024-03-02T19:03:48Z

@smarts4home since you created Koenkk/zigbee-herdsman-converters#7070 before, do you still want to add this device?

mrmaximas · 2024-03-03T21:02:16Z

@pvvx not possible to set some parameters via z2m web ui, like Comfort temperature min/max etc.
how to force it? below are error log and two screenshots, is there any bugs in the converter?

Firmware build date
20240211
Firmware version
3001-0120

Publish 'set' 'comfort_humidity_min' to 'Test Sensor' failed: 'Error: Write 0xa4c1383bc0835aec/1 hvacUserInterfaceCfg({"260":{"value":4000,"type":33}}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'INVALID_DATA_TYPE')'
Publish 'set' 'comfort_temperature_max' to 'Test Sensor' failed: 'Error: Write 0xa4c1383bc0835aec/1 hvacUserInterfaceCfg({"259":{"value":2300,"type":41}}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'INVALID_DATA_TYPE')'

kafisc1 · 2024-03-10T19:00:35Z

This external converter (and also without any external convert) stopped working for my LYWSD03MMC-z since upgrading z2m with the following error:
Exception while calling fromZigbee converter: Definition 'LYWSD03MMC-z' has not endpoint defined}

Is anyone facing the same issue?

txitxo0 · 2024-03-11T07:28:11Z

This external converter (and also without any external convert) stopped working for my LYWSD03MMC-z since upgrading z2m with the following error: Exception while calling fromZigbee converter: Definition 'LYWSD03MMC-z' has not endpoint defined}

Is anyone facing the same issue?

Yep, here experimenting the same behaviour

kafisc1 · 2024-03-11T07:39:29Z

This external converter (and also without any external convert) stopped working for my LYWSD03MMC-z since upgrading z2m with the following error: Exception while calling fromZigbee converter: Definition 'LYWSD03MMC-z' has not endpoint defined}
Is anyone facing the same issue?

Yep, here experimenting the same behaviour

Switched from dev to stable branch for now.
The error does not occur here.

txitxo0 · 2024-03-12T11:36:32Z

This external converter (and also without any external convert) stopped working for my LYWSD03MMC-z since upgrading z2m with the following error: Exception while calling fromZigbee converter: Definition 'LYWSD03MMC-z' has not endpoint defined}
Is anyone facing the same issue?

Yep, here experimenting the same behaviour

Switched from dev to stable branch for now. The error does not occur here.

I am using the zigbee2mqtt home asistant addon and, as far as I know it is using the stable branch as well. How did you do it?

kafisc1 · 2024-03-13T09:37:28Z

I added the external converter from the buttom
I removed the HASS-Addon (make copy of addon config from the section socat ) "Zigbee2MQTT-dev" and installed Zigbee2MQTT (enter prior saved config into socat in the addon settings)
I rebooted the whole machine and it was working again

External converter:

`// Autor: Markus Bodengriller https://github.com/Bodengriller
// requires zigbee2mqtt v1.34+
// external converter for Xiaomi LYWSD03MMC https://github.com/pvvx/ZigbeeTLc
// based on external converter for devbis-Firmware
// https://raw.githubusercontent.com/devbis/z03mmc/master/converters/lywsd03mmc.js

const {
batteryPercentage,
temperature,
humidity,
enumLookup,
binary,
numeric,
quirkAddEndpointCluster,
} = require('zigbee-herdsman-converters/lib/modernExtend');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const ota = require('zigbee-herdsman-converters/lib/ota');

const dataType = {
boolean: 0x10,
uint8: 0x20,
uint16: 0x21,
int8: 0x28,
int16: 0x29,
enum8: 0x30,
};

module.exports = definition;`

sabamimi · 2024-03-14T11:02:13Z

Thanks for this LYWSD03MMC-z support !
I hope it will make it to the official version.

One small issue on my side : the batterie reports 100% all the time, any clue ? should I reapply firmware?

kafisc1 · 2024-03-14T11:12:34Z

Thanks for this LYWSD03MMC-z support ! I hope it will make it to the official version.

One small issue on my side : the batterie reports 100% all the time, any clue ? should I reapply firmware?

The battery report is working for me. Seems like the devices are staying a long time on 100% and are only reporting on greater changes.

sabamimi · 2024-03-14T11:54:52Z

Thanks @kafisc1 for your feedback

txitxo0 · 2024-03-14T16:23:49Z

I have just added this external converter from the settings menu and reboot all the host, but I am still experimenting issues. The device is not supported and the temp and humidity are not being exposed.

I am using the ZigBee regular addon in HA, not the edge version

TheGroundZero · 2024-03-14T19:29:55Z

I have just added this external converter from the settings menu and reboot all the host, but I am still experimenting issues. The device is not supported and the temp and humidity are not being exposed.

I am using the ZigBee regular addon in HA, not the edge version

You need to remove the device from Z2M and re-pair it.
https://sequr.be/blog/2024/02/flash-xiaomi-lywsd03mmc-ble-sensor-with-zigbee-firmware/#lywsd03mmc-z

pvvx · 2024-03-14T23:32:49Z

The battery report is working for me. Seems like the devices are staying a long time on 100% and are only reporting on greater changes.

The initial, ultra-short period of operation of the new battery is cut off. These are voltages greater than 3.0V.
Otherwise, in a few days you will have 80% and so 80% of the working time.

If you set 3.3V to 100%, then most people complain that the battery is discharged by 20% in a few days. :P

80% of the time the CR2032 under load in the thermometer delivers 2.8..2.95V (+25C), not 3.3V.

fhempy · 2024-04-01T19:31:12Z

@Koenkk

@smarts4home since you created Koenkk/zigbee-herdsman-converters#7070 before, do you still want to add this device?

Hi,
I thought that the code from this external converter (https://github.com/pvvx/ZigbeeTLc/blob/master/z2m/lywsd03mmc-z.js) is going to be added to the April release. Any further plans for the next release, or is there something missing?

pvvx · 2024-04-01T20:44:05Z

Standard Zigbee 3.0 does not require special support.
Converters are required solely to support non-standard functions.
As a result, if zigbee2mqtt supports Zigbee 3.0, then the thermometers should work without any converters.
For example, ZHA partially supports Zigbee 3.0 and does not require any converters or “quirks” to operate the described thermometers. And when connecting new devices, users do not have to wait for support from software creators.

LeeWiu · 2024-04-03T08:14:40Z

https://github.com/pvvx/ZigbeeTLc/blob/master/z2m/lywsd03mmc-z.js is not working anymore after updating to Z2M to 1.36.1-1, I get Unsupported device. I tried to delete and add again, same thing. I even added a new device, still unsupported.
Downgraded to 1.36.0-1 and all good.

FW 3001-0120 20240226

dasEtwasmitPunkten · 2024-04-03T08:34:54Z

https://github.com/pvvx/ZigbeeTLc/blob/master/z2m/lywsd03mmc-z.js is not working anymore after updating to Z2M to 1.36.1-1, I get Unsupported device. I tried to delete and add again, same thing. I even added a new device, still unsupported. Downgraded to 1.36.0-1 and all good.

FW 3001-0120 20240226

I am experiencing the same behavior. Fortunately the temperature and humidity sensors are still working. The custom functions like the comfort temperature and humidity limits are gone.
Can somebody explain the behavior?

LeeWiu · 2024-04-03T08:40:53Z

I updated the file and it's working now, was a small change about 20 hours ago, I'm not sure if this was the culprit pvvx/ZigbeeTLc@6d8e14b

korbinio · 2024-04-05T09:17:21Z

@Koenkk

@smarts4home since you created Koenkk/zigbee-herdsman-converters#7070 before, do you still want to add this device?

Hi, I thought that the code from this external converter (https://github.com/pvvx/ZigbeeTLc/blob/master/z2m/lywsd03mmc-z.js) is going to be added to the April release. Any further plans for the next release, or is there something missing?

@Koenkk: +1 from me for adding this to the next release :)

Koenkk · 2024-04-06T07:00:08Z

Can someone make a pull request for this?

xylorin · 2024-04-13T20:24:12Z

Any chance to receive a standard support for this device in future?

baloo2 · 2024-04-17T18:16:00Z

+1 to add support for this - thanks a lot

pvvx · 2024-04-18T05:43:48Z

Version 0.1.2.1 includes the ability to change the name of the device. :)
Made to create a mess in Z2M, with the goals of correcting the identification of devices according to the codes of the firmware version and other digital identifiers to Zigbee 3.0. Otherwise, Z2M does not update the expansion of functionality after OTA and incorrectly identifies the devices. In addition, Z2M requires users to write scripts for standard Zigbee 3.0 devices.

baloo2 · 2024-04-18T08:39:57Z

Thanks! Shoud the update be available online in Z2M or I have to update it manually (my_index.json)?

BWFCGUIXT · 2024-04-18T11:19:58Z

Zigbee2MQTT version [1.36.1]
commit: [ffc2ff1]
Coordinator type: EZSP v8
Coordinator revision: 6.10.3.0 build 297

Now getting the following error when trying to update:


Error 2024-04-18 13:13:54Failed to check if update available for 'Temperature/Humidity Sensor Living room' (The value of "offset" is out of range. It must be >= 0 and <= 98266. Received 98268)


Debug 2024-04-18 13:13:54RangeError: The value of "offset" is out of range. It must be >= 0 and <= 98266. Received 98268 at new NodeError (node:internal/errors:405:5) at boundsError (node:internal/buffer:88:9) at Buffer.readUInt16LE (node:internal/buffer:245:5) at parseSubElement (/app/node_modules/zigbee-herdsman-converters/src/lib/ota/common.ts:149:26) at Object.parseImage (/app/node_modules/zigbee-herdsman-converters/src/lib/ota/common.ts:192:29) at fillImageInfo (/app/node_modules/zigbee-herdsman-converters/src/lib/ota/zigbeeOTA.ts:29:26) at /app/node_modules/zigbee-herdsman-converters/src/lib/ota/zigbeeOTA.ts:51:109 at Array.map (<anonymous>) at getIndex (/app/node_modules/zigbee-herdsman-converters/src/lib/ota/zigbeeOTA.ts:51:45) at processTicksAndRejections (node:internal/process/task_queues:95:5)

Probably completely unrelated but maybe someone has the solution for the following error:

error 2024-04-18 13:18:43: Entity 'homeassistant/sensor' is unknown

Seems I was actually doing this wrong and trying to use: [Z03MMC_v0121.bin] https://github.com/pvvx/ZigbeeTLc/blob/master/bin/Z03MMC_v0121.bin)

Instead of using the .zigbee file.

pvvx · 2024-04-18T13:31:15Z

LYWSD03MMC-z FW ver 0.1.2.1

ZHA: LYWSD03MMC-z by Xiaomi , Firmware: 0x01213001

zha_toolkit_version: v1.1.10
zigpy_version: 0.63.4
zigpy_rf_version: 0.38.1
ieee_org: update.xiaomi_lywsd03mmc_z_firmware
ieee: a4:c1:38:0b:5e:ed:85:b7
command: attr_read
command_data: null
start_time: "2024-04-18T13:27:14.572671+00:00"
errors: []
params:
  endpoint_id: 1
  cluster_id: 516
  attr_id: 256
  dir: 0
  tries: 1
  expect_reply: true
  args: []
  read_before_write: true
  read_after_write: true
attr_type: "0x29"
write_is_equal: false
result_read:
  - "256": 0
  - {}
success: true

attr_type: "0x29" - Signed 16bit int

In future firmware versions, to eliminate dependencies from Z2M glitches, it is planned to install device settings via BLE from the Google Chrome web browser.
The firmware will support both BLE and Zigbee. Switching to BLE will be temporary, for LYWSD03MMC for ~80 seconds to connect after turning the battery off and on.

LeeWiu · 2024-04-18T15:33:45Z

LYWSD03MMC-z FW ver 0.1.2.1

ZHA: LYWSD03MMC-z by Xiaomi , Firmware: 0x01213001
zha_toolkit_version: v1.1.10
zigpy_version: 0.63.4
zigpy_rf_version: 0.38.1
ieee_org: update.xiaomi_lywsd03mmc_z_firmware
ieee: a4:c1:38:0b:5e:ed:85:b7
command: attr_read
command_data: null
start_time: "2024-04-18T13:27:14.572671+00:00"
errors: []
params:
  endpoint_id: 1
  cluster_id: 516
  attr_id: 256
  dir: 0
  tries: 1
  expect_reply: true
  args: []
  read_before_write: true
  read_after_write: true
attr_type: "0x29"
write_is_equal: false
result_read:
  - "256": 0
  - {}
success: true
attr_type: "0x29" - Signed 16bit int

In future firmware versions, to eliminate dependencies from Z2M glitches, it is planned to install device settings via BLE from the Google Chrome web browser. The firmware will support both BLE and Zigbee. Switching to BLE will be temporary, for LYWSD03MMC for ~80 seconds to connect after turning the battery off and on.

This is the right OTA file?
https://github.com/pvvx/ZigbeeTLc/blob/master/bin/devbis/1141-0203-79993001-Z03MMC_v0121.zigbee

robvanoostenrijk · 2024-04-29T08:51:40Z

The support for LYWSD03MMC-z (and other pvvx ZigbeeTLc devices) is covered in Koenkk/zigbee-herdsman-converters#7457

OTA is supported as well. Once the device support is merged, I'll reach out to @pvvx to see if we can update the Zigbee2MQTT firmware index to point to the firmware provided on the ZigbeeTLc repo.

xylorin · 2024-05-06T10:27:04Z

just wanted to thank you all, today i checked my HA and the device is now correctly working!

https://www.zigbee2mqtt.io/devices/LYWSD03MMC-z.html#xiaomi-lywsd03mmc-z

z-master42 · 2024-05-15T15:27:48Z

I have six of these with firmware 0120. I was offered an OTA update to 0121 for three of them. Still not for the other three. Any ideas?

TheGroundZero added the new device support New device support request label Feb 19, 2024

[New device support]: LYWSD03MMC-z #21467

[New device support]: LYWSD03MMC-z #21467

Comments

TheGroundZero commented Feb 19, 2024 • edited Loading

Link

Database entry

Comments

External definition

pvvx commented Feb 19, 2024

TheGroundZero commented Feb 19, 2024 • edited Loading

BartCardan commented Feb 21, 2024

TheGroundZero commented Feb 22, 2024

Milinator commented Feb 23, 2024

Milinator commented Feb 24, 2024

dasEtwasmitPunkten commented Mar 2, 2024

Koenkk commented Mar 2, 2024

mrmaximas commented Mar 3, 2024 • edited Loading

kafisc1 commented Mar 10, 2024

txitxo0 commented Mar 11, 2024

kafisc1 commented Mar 11, 2024

txitxo0 commented Mar 12, 2024

kafisc1 commented Mar 13, 2024

sabamimi commented Mar 14, 2024

kafisc1 commented Mar 14, 2024

sabamimi commented Mar 14, 2024

txitxo0 commented Mar 14, 2024

TheGroundZero commented Mar 14, 2024

pvvx commented Mar 14, 2024 • edited Loading

fhempy commented Apr 1, 2024 • edited Loading

pvvx commented Apr 1, 2024 • edited Loading

LeeWiu commented Apr 3, 2024 • edited Loading

dasEtwasmitPunkten commented Apr 3, 2024 • edited Loading

LeeWiu commented Apr 3, 2024

korbinio commented Apr 5, 2024

Koenkk commented Apr 6, 2024

xylorin commented Apr 13, 2024

baloo2 commented Apr 17, 2024 • edited Loading

pvvx commented Apr 18, 2024 • edited Loading

baloo2 commented Apr 18, 2024

BWFCGUIXT commented Apr 18, 2024 • edited Loading

pvvx commented Apr 18, 2024 • edited Loading

LeeWiu commented Apr 18, 2024

robvanoostenrijk commented Apr 29, 2024 • edited Loading

xylorin commented May 6, 2024 • edited Loading

z-master42 commented May 15, 2024

TheGroundZero commented Feb 19, 2024 •

edited

Loading

TheGroundZero commented Feb 19, 2024 •

edited

Loading

mrmaximas commented Mar 3, 2024 •

edited

Loading

pvvx commented Mar 14, 2024 •

edited

Loading

fhempy commented Apr 1, 2024 •

edited

Loading

pvvx commented Apr 1, 2024 •

edited

Loading

LeeWiu commented Apr 3, 2024 •

edited

Loading

dasEtwasmitPunkten commented Apr 3, 2024 •

edited

Loading

baloo2 commented Apr 17, 2024 •

edited

Loading

pvvx commented Apr 18, 2024 •

edited

Loading

BWFCGUIXT commented Apr 18, 2024 •

edited

Loading

pvvx commented Apr 18, 2024 •

edited

Loading

robvanoostenrijk commented Apr 29, 2024 •

edited

Loading

xylorin commented May 6, 2024 •

edited

Loading