Addr of lcd and sensor lost
Opened this issue · 4 comments
After flashing the firmware with ZigBee with the display turned off, after a while the sensor stopped working, although the device itself responded to requests, it also became impossible to turn on the display, the command was accepted but the display did not turn on. After flashing it to ble, it became clear that the device had lost the addresses of the display and sensor. Can this be fixed somehow?
Most likely this is a hardware problem. Look at the printed circuit board and the soldering of the elements.
Everything is fine with the contacts, the sensor worked for several years before. I also noticed that the hw version in the firmware information and on the board is different. 1.4 on the board and 1.6 in the information.
The HW version is determined by the I2C addresses of the sensor and display controller.
Write the device’s response to https://pvvx.github.io/ATC_MiThermometer/TelinkMiFlasher.html to command “02”:
15:25:57: Hardware Revision String: B1.4
15:25:57: Software Revision String: V4.7
15:25:57: Firmware Revision String: github.com/pvvx
15:25:57: Detected custom Firmware
15:25:57: Hardware Version: LYWSD03MMC B1.4, Software Version: 4.7, Sensor: SHTC3 (SHTV3)
15:25:57: Custom config HEX string: 55051000004004a9313180e1
15:26:08: Settings 03 was sent successfully
15:26:15: Settings 02 was sent successfully
15:26:16: Sensor: I2C addres 0x70, LCD driver: I2C addres 0x3C
And in the "console" (Chrome F12) using the command "03".
Specially checked on HW B1.4:
- BLE connecting and turned off the display.
- Turned off/on the power.
- BLE connecting and turning on the display.
- Disable BLE connection.
Everything is fine.
Consumption in sleep mode with display off:
Consumption in sleep mode with display on:
