Is there any way to “age out” the readings or perhaps have a timestamp on the last one.
As it stands if you have an issue with a sensor the last reading is still “current” and of course might not reflect reality and this exhibit undesirable results in a flow.
Or is there anyway the application could flag an error if no reading is received after a configurable timeout period?
I get the same issue. That it connects as an unknown Zigbee device after flashing FW.
Did you manage resolve the issue? Any solutions available?
I also have Xiaomi LYWSD0MMC-z with FW version: 3001-0120.
Awesome! I will flash 10 of these for my cabin. Since I don’t have a computer at my cabin, is it fine to flash them all at home or are there any disadvantages by doing so? To identify them from each other I could just remove the batteries and add them one by one in Homey.
It’s so nice that this app exists. I have a humble feature request:
It would be nice to be able to choose how many decimals to be shown from the device, just like you can with the Tuya Zigbee app. It’s not the end of the world that this isn’t available, but it would tidy things up a bit having consistency throughout my devices.
Hi Michiel, not really. Mine were completely stuck at some point, so I had to flash them over via USB-UART and I moved into ESPHome (with few ESP boards to have a full house coverage) with the bluetooth version of these, instead of trying and converting them to Zigbee again.
✓ Pre-processing app...
Added Driver `xiaomi-thermometer-ble`
Added Driver `xiaomi-thermometer-zigbee`
× Command failed: npm ls --parseable --all --only=prod
npm WARN config only Use `--omit=dev` to omit dev dependencies from the install.
npm ERR! code ELSPROBLEMS
npm ERR! missing: homey-zigbeedriver@^2.1.2, required by hu.corenet.mitemp@1.0.0
npm ERR! missing: zigbee-clusters@^2.3.0, required by hu.corenet.mitemp@1.0.0
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\XXXXXX\AppData\Local\npm-cache\_logs\2024-04-22T15_08_40_980Z-debug-0.log
× Error: This error may be fixed by running `npm install` in your app.
at C:\Users\XXXXXX\AppData\Roaming\npm\node_modules\homey\lib\App.js:874:15
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async App._copyAppProductionDependencies (C:\Users\XXXXXX\AppData\Roaming\npm\node_modules\homey\lib\App.js:871:26)
at async Promise.all (index 1)
at async App.preprocess (C:\Users\XXXXXX\AppData\Roaming\npm\node_modules\homey\lib\App.js:826:5)
at async App.install (C:\Users\XXXXXX\AppData\Roaming\npm\node_modules\homey\lib\App.js:767:7)
at async Object.exports.handler (C:\Users\XXXXXX\AppData\Roaming\npm\node_modules\homey\bin\cmds\app\install.js:25:5)
@ZsR@robertklep Hello, when I installed “devbis” firmware as zigbee software, I observed that the xiaomi sensor works better. But when I install this firmware, it appears as an unknown device in homey pro 2023. Can you introduce this to homey.