Meawow MHO-C122 (2AWMOMHOC122) support #339

FaBjE · 2023-05-13T12:14:38Z

Introduction

Recently I acquired a few of the Meawow MHO-C122 (2AWMOMHOC122) sensors for a bargain price.
Hoping I was able to scrape the sensor data from the advertisement or basic readout of some characteristics.
Long story short, with the default firmware: Data is not advertised, Readout is only on a proprietary protocol, you can only connect over Bluetooth when you just inserted the battery.

I tried if the OTA update page of this project had any luck but unfortunately not. The published characteristics are nowhere near what the default Xiaomi units publish.

4:11:00 PM: Searching for devices
4:11:02 PM: Connecting to: C121
4:11:13 PM: Not found Telink OTA service!
4:11:13 PM: Disconnected.

Opening up the unit I saw the PCB with almost identical setup/components as the Xiaomi units.
No wonder as these are produced by the same company (I believe)
Giving me the Idea if with maybe some minor tweaks the software of this project can be run on those units as well.
This issue will be my little blog/progress report. Feel free to help out if you have anything to add.

Meawow MHO-C122 (2AWMOMHOC122)

https://meawow.com/product/thermo-hygrometer/mho-c122/

Exteriour

The unit LCD/casing is identical to the MHO-C101

Interiour

I took the following pictures of the PCB
Front:

Back:

On that we can see the (familiar)
MCU: TLSR8251F512ET24
LCD: IST3055NA0
Sensor: (Probably) SHTV3

Software

The default software gives the following log when connecting with the nRF Connect app.
meawow connection log.txt

ToDo List

Establish UART connection
Retrieve original firmware
Program with custom firmware + test
Fix LCD layout

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

AvA1970 · 2023-05-13T13:23:47Z

I have purged also 5 of these. Would be nice to flash firmware or to advertise ble so HA could pick these up.

I will follow this topic with interest.

killabeenl · 2023-05-17T07:14:04Z

I have also a couple of these and it would be nice if we can flash them to use with HA

NH-Networks · 2023-05-19T22:51:15Z

same here! hope someone can figure this out..

ZekiZico · 2023-05-20T11:27:12Z

I'm interested in this too, can't get them connected to HA

FaBjE · 2023-05-20T13:03:59Z

I've made some progress. I have made a little programmer jig with a CH340 I'm able to readout the flash contents of the MCU.
I should be able to program the unit with new firmware, But I haven't tried (yet).
You only need the three connection pads on the right of the PCB.

Original_Firmware_MHO_C122.zip

Using this schematic/instruction:
https://github.com/pvvx/TlsrComSwireWriter#telink-swire-simulation-on-a-com-port

VCC is connected to the RTS to be able reset the MCU
The PCB is clamped between a dual-row header (and some cardboard stuff) This provides exact spacing and does not require soldering to the PCB.

Things I have learned

The silkscreen labels on the PCB can be deceiving. Reset is not the MCU reset, but just an IO pin.
You cant use the programmer scripts from a Virtual machine, WSL or a docker container. The timing becomes too unstable.
A full readout on the flash takes about 15 minutes. (for 512KB) But hey, I'm glad it works without buying an expensive programmer.
This command worked best for me: \python.exe TLSR825xComFlasher.py -p COM23 -t 70 rf 0 0x80000 firmware_download.bin

ZekiZico · 2023-05-20T13:44:48Z

Good job!

NH-Networks · 2023-05-20T14:32:30Z

I will use your findings and will try out to replicate it, have all tools needed. Do you think we can flash the same firmware without any modifications? Op za 20 mei 2023 15:04 schreef 'Fabje' via Info Fwd ***@***.***>:

…

I've made some progress. I have made a little programmer jig with a CHD340 I'm able to readout the flash contents of the MCU. I should be able to program the unit with new firmware, But I haven't tried (yet). You only need the three connection pads on the right of the PCB. Original_Firmware_MHO_C122.zip <https://github.com/pvvx/ATC_MiThermometer/files/11522404/Original_Firmware_MHO_C122.zip> Using this schematic/instruction: https://github.com/pvvx/TlsrComSwireWriter#telink-swire-simulation-on-a-com-port - VCC is connected to the RTS to be able reset the MCU - The PCB is clamped between a dual-row header (and some cardboard stuff) This provides exact spacing and does not require soldering to the PCB. [image: programmer setup] <https://user-images.githubusercontent.com/5355001/239688451-11ec291e-c1a9-4074-9a03-e5854d525268.jpg> Things I have learned - The silkscreen labels on the PCB can be deceiving. Reset is not the MCU reset, but just an IO pin. - You cant use the programmer scripts from a Virtual machine, WSL or a docker container. The timing becomes too unstable. - A full readout on the flash takes about 15 minutes. (for 512KB) But hey, I'm glad it works without buying an expensive programmer. - This command worked best for me: \python.exe TLSR825xComFlasher.py -p COM23 -t 70 rf 0 0x80000 firmware_download.bin — Reply to this email directly, view it on GitHub <#339 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGCTINEOKOWBNB7TTWOZHUDXHC6MTANCNFSM6AAAAAAYAOVNRI> . You are receiving this because you commented.Message ID: ***@***.***>

FaBjE · 2023-05-21T11:38:59Z

Some progress was made. I managed to flash the ATC_v42.bin. and the good news is that bluetooth works.
The sensor and battery readout seems to work fine.
But the LCD is messed up. It seems to work, but the segment layout is different, so you get really weird data displayed.

I tried some other firmwares and these are the results:

ATC_v42.bin: LCD Seems to work messed up segments, BT Temp/Humidity OK
MHO_C401_v42: No LCD, BT Temp/Humidity OK
MHO_C401N_v42.bin: No LCD, BT Temp/Humidity OK

Things I Learned

My programming jig is really temperamental. So don't recommend copying it. I suspect the power from the RTS pin is not sufficient.

@pvvx Is there a way to easily identify the LCD segment layout? Like flash each segment one by one?

pvvx · 2023-05-21T23:16:00Z

Control function ID when connected

ID	Command
0x60	Get/Set LCD buffer

TelinkMiFlasher.html.

6001020304...
60 - command
01020304... - lcd buffer

Creates a bit-map similar to the one shown here - epd_mho_c401n.c

pvvx · 2023-05-22T00:15:44Z

Original_Firmware_MHO_C122.zip

Cut OTA file (CRC ok) -> https://github.com/pvvx/ATC_MiThermometer/blob/master/Original_OTA_MHO_C122_tuya.bin

This OTA file has a size of more than 128 kilobytes.
Typical Telink BLE firmware does not support OTA sizes larger than 128 kilobytes.
For this firmware, you will have to change the source code, approximately as done for MJWSD05MMC.

pvvx · 2023-05-23T22:37:10Z

The latest versions of Tuya BLE transmission of advertising packages with sensor data.
Also in Tuya BLE there is a download OTA with a key signature. Some of the codes can be found on the Tuya Cloud.

"LocalTuya integration" in the "HA" misleads users by not indicating that BLE is not supported.

FaBjE · 2023-05-26T08:53:00Z

I've made an LCD segment map. I'll try to cook up a lcd driver for it.

Apologies for the mix between 0 indexed (bytes) and 1 indexed (bits), I guess I wasn't fully awake yet....

pvvx · 2023-05-27T23:11:30Z

ATC_v42.bin: LCD Seems to work messed up segments, BT Temp/Humidity OK

What is the address of the LCD controller?

And how are things with Tuya OTA?

pvvx · 2023-05-28T02:51:43Z

I recorded the firmware MHO-C122 in Xiaomi LYWSD03MMC (HW: B1.4).

Registered in "Smart Life":

Average Power:

nRFConnect (advertising):

Data is transmitted from the sensor.

https://iot.tuya.com/ (Registration in the cloud is free for all your devices registered in "Smart Life". All encryption keys are available.)
Device Management -> Get device details:

{
  "result": {
    "active_time": 1685239585,
    "biz_type": 18,
    "category": "wsdcg",
    "create_time": 1685239585,
    "icon": "smart/icon/bay1607936793441YbTx/03baef663c3c1a2149c7fbf98110e134.png",
    "id": "bf7xxxxxxxxhrn",
    "ip": "",
    "lat": "xx.9400",
    "local_key": "d+xxxxxxxxxxxxxx9-^",
    "lon": "xx.1000",
    "model": "MHO-C121",
    "name": "Temperature Humidity Sensor",
    "online": false,
    "owner_id": "47xxxx61",
    "product_id": "3nxxxxw6",
    "product_name": "Temperature Humidity Sensor",
    "status": [
      {
        "code": "va_temperature",
        "value": 223
      },
      {
        "code": "va_humidity",
        "value": 39
      },
      {
        "code": "battery_percentage",
        "value": 100
      },
      {
        "code": "temp_sampling",
        "value": 6
      },
      {
        "code": "temp_unit_convert",
        "value": "c"
      }
    ],
    "sub": false,
    "time_zone": "+03:00",
    "uid": "eu164xxxxxxxxxxxx5HE",
    "update_time": 1685239587,
    "uuid": "15xxxxxxxxxxx9c9"
  },
  "success": true,
  "t": 1685xxxxx7614,
  "tid": "78xxxxxxxxxxxxxxxxxxxxxxxxxxxx2a"
}

The data-keys has been changed (replaced with "xxxxx").

OTA is present. I haven't figured out how to program and where the keys are in the cloud yet...
There is a Telink SDK - ble_sdk_multimode_tuya. The old version. The SDK has OTA sources (ble_sdk_multimode_tuya\tuya_components\tlsr\tuya_ota.c).

pvvx · 2023-05-28T04:59:55Z

Apologies for the mix between 0 indexed (bytes) and 1 indexed (bits), I guess I wasn't fully awake yet....

/*
 *  MHO-C122 LCD buffer:  byte.bit

         --0.4--         --1.4--            --2.4--
  |    |         |     |         |        |         |
  |   0.0       0.5   1.0       1.5      2.0       2.5
  |    |         |     |         |        |         |      o 3.0
 0.3     --0.1--         --1.1--            --2.1--          +--- 3.0
  |    |         |     |         |        |         |     3.0|
  |   0.2       0.6   1.2       1.6      2.2       2.6       ---- 3.1
  |    |         |     |         |        |         |     3.0|
         --0.7--         --1.7--     *      --2.7--          ---- 3.2
                                    2.3
           --5.3--         --4.3--              1.3      1.3            
 (|)     |         |     |         |            / \      / \      
 3.7    5.6       5.2   4.6       4.2     1.3(  ___  3.6 ___  )1.3
         |         |     |         |            1.3  / \ 1.3      
 BLE       --5.5--         --4.5--                   ___          
 4.7     |         |     |         |                 3.5          
        5.4       5.1   4.4       4.1     	
 BAT     |         |     |         |                  %
 5.7       --5.0--         --4.0--                   3.4

None: 3.3 ?

*/

pvvx · 2023-05-28T08:44:54Z

Added a test version of MHO-C122.
So far, flash programming is only via hardware - SWS.
TelinkMiFlasher.html does not work with the original MHO-C122. With firmware MHO_C122_v43.bin something will work...
Check if everything is correct with the display.

FaBjE · 2023-05-28T10:37:09Z

What is the address of the LCD controller?

12:30:06 PM: Settings 02 was send successful
12:30:07 PM: Sensor: I2C addres 0x70, LCD driver: I2C addres 0x3C

And how are things with Tuya OTA?
Could not tell you. I tried an OTA in the app, but there was "no update available".

Whoops. I guess i was really still sleeping...
I checked and yes your correction is right.

Check if everything is correct with the display.

Thanks so much! I just can't find the time...
I will test this right now and report back.

FaBjE · 2023-05-28T14:45:38Z

@pvvx
I tested the LCD driver, it had some issues unfortunately.
But I manged to find them and submit a pull request with fixes: #344
Afaik it works good now, It's on my desk and I will monitor it.

…6161613

pvvx · 2023-05-28T17:26:41Z

To complete work with MHO-C122(C121), an OTA is required.
This is not the first thermometer with TUYA BLE PROTOCOL VERSION 4.
I haven't seen any solutions for the Tuya BLE (new version) OTA.
Also, there is no integration local BLE Tuya in "HA".

https://fcc.report/FCC-ID/2AWMOMHOC122

pvvx · 2023-05-29T12:40:55Z

The description of the OTA protocol is in the cloud.

But you need to register.

https://developer.tuya.com/en/docs/iot-device-dev/OTA_BLE

It seems to give out all the keys.

It remains to understand the encryption method.

FaBjE · 2023-05-29T16:19:03Z

https://developer.tuya.com/en/docs/iot-device-dev/OTA_BLE?id=Kawer1ehuv8si seems freely available to me.
The example document at the bottom: https://images.tuyacn.com/smart/docs/OTA-update-sample.docx seems to list an example how to implement the tuya way in the MCU.
Maybe this helps you to implement it in the TelinkFlasher page?

pvvx · 2023-05-30T00:16:50Z

Full sample of Telink SDK Tuya.
https://github.com/pvvx/pvvx.github.io/blob/master/MHO_C122/bin/ble_sdk_multimode_tuya.zip

But this is an old version of Tuya. Was available on Telink official website earlier.
It is assembled in Telink IDE, works, registers in applications on a smartphone...

pvvx · 2023-05-30T00:39:11Z

Maybe this helps you to implement it in the TelinkFlasher page?

There is still a lot to figure out.

Add to the firmware the initial correction of the OTA download to another area.
Restoring Tuya firmware.
Request keys from the user or from the cloud
But the main thing is how to establish a connection with the cipher.

I didn't find anyone doing this. Disassembled the old version and with Wi-Fi. I haven't seen anyone who could handle the new version of Tuya.

PS: And for the whole summer I usually take a break from working at computers...

pvvx · 2023-05-30T01:50:08Z

I found the source package tuya_ble_sdk_Demo_Project_tlsr8253 in the archive.
In the SDK, libs Tuya on most ARM:

libtuya_ble_sdk_lib_tlsr825x.a
tuya_ble_sdk_lib_arm_m0.lib
tuya_ble_sdk_lib_arm_m3.lib
tuya_ble_sdk_lib_arm_m4.lib
tuya_ble_sdk_lib_arm_m4f.lib
tuya_ble_sdk_lib_arm9e-s_little_endian.lib

FaBjE · 2023-05-30T08:32:57Z

Maybe this helps you to implement it in the TelinkFlasher page?

There is still a lot to figure out.
1. Add to the firmware the initial correction of the OTA download to another area.

2. Restoring Tuya firmware.

3. Request keys from the user or from the cloud
   But the main thing is how to establish a connection with the cipher.
I didn't find anyone doing this. Disassembled the old version and with Wi-Fi. I haven't seen anyone who could handle the new version of Tuya.

I think the most beneficial one is to "update" from stock tuya firmware to "atc firmware"
Going back to Tuya firmware would be a "nice to have" imho. But I don't think it will be a much used feature.

PS: And for the whole summer I usually take a break from working at computers...

You should definitely do that too :)

FaBjE · 2023-06-10T09:53:44Z

I've been running this firmware: https://github.com/pvvx/ATC_MiThermometer/raw/20a087dcc2c234f48790ee618d7273444288a2b9/MHO_C122_v43.bin on three units now for two weeks.
Without any problems. So I'm declaring this "finished/stable"

For the initial firmware update a programmer is needed.
After the initial 'convert' the updates can be done over BLE using the telink flasher page.

cardshare007 · 2023-06-17T19:26:32Z

Thanks mate, will try with a battery and let you know the results

pvvx · 2023-06-17T19:31:35Z

USBCOMFlashTx is the easiest option when there is nothing more....

USBCOMFlashTx.html has no feedback. Perhaps the firmware will be executed unsuccessfully. In this case, repetition is required.
And the second problem is that the chip may be in sleep mode. For reliable programming, it is necessary to turn on the power during activation (ATime) or use a reset signal from the chip.
After such programming, it is necessary to make a new OTA, since there is no guarantee of correct firmware using 'USBCOMFlashTx'.

NH-Networks · 2023-06-18T09:18:30Z

Tried on breadboard yesterday with ch340 of wittyboard gnd sws and rst connected, but cant seem to flash new firmware.. do i need to set it in flash mode somehow? Every try i did it still had original firmware afterwards

cardshare007 · 2023-06-18T10:36:13Z

cardshare007 · 2023-06-18T10:39:17Z

What I did:

tried with a battery and only connect SWS and GND: nothing happens
see the picture: I also tried to connect the VCC on the 3.3: no result
I don't use FTDI but a wchusbserial1420

Still nothing seems to happen - please let me know if there are any further ideas. Thanks a lot for your support!

cardshare007 · 2023-06-18T10:43:34Z

@FaBjE you didn't use the html page to flash, but how did you flash the thermometer? I saw in one of your first posts that you used python script ?

I use the https://github.com/pvvx/TlsrComSwireWriter from the repository. But I think you also need to connect the RX for that. Using a resistor https://github.com/pvvx/TlsrComSwireWriter#telink-swire-simulation-on-a-com-port

but I think the middle is the sws or am I missing something?

Yes middle connection pad, but his lower wire.

What I didn't do is use the battery to power it. Is this necessary?

Yes, see pvvx his explanation.

If RX. if FTDI is used, it checks the bit frame, but it does not match the 1-wire Telink

Thanks for explaining

I was struggling a bit to get this to work since I think python on my Mac is giving some troubles. Also, I see a different way of connecting the devices, I havn't been using resistors and not sure how to do this. Let me know if this is absolutely a necessity and I will check this direction...

FaBjE · 2023-06-18T12:42:04Z

do i need to set it in flash mode somehow

Yes, programming mode is achieved by sending a "magic sequence" on the SWS line.
This must be done directly after power-up. Therefore I / the script uses the "RTS" line to switch power on the right moment.
You can either switch the power yourself and tune with the "activation time" or let the script do it for you using the RTS line.
My USB > UART converter was able to supply enough current over this line to power the programming circuit, but there is no guarantee.
I only used the script from the repository:
\python.exe TLSR825xComFlasher.py -p COM24 -t 50 wf 0 .\ATC_Thermometer.bin

Let me know if this is absolutely a necessity and I will check this direction...

Well it is not an absolute necessity, but the "TX only" method, is a bit risky.
The resistor is used to make from a 1 signal wire "uart" (The SWS protocol), a two-wire signal for a normal USB->UART converter.
When only the TX is connected the webpage/script just sends the data hoping the microcontroller accepts it. (Having no clue if it does or not)

With the resistor (and the RX line connected) the Python script from this repository is able to receive the reply from the micro-controller and check if it has accepted the data or not.

To all of you, I had a lot of struggles getting this to work either. It is simulating a (expensive) programmer on cheap hardware. So it is all a bit "tongue at the right angle" and hoping it works stuff.
Sometimes I just have reconnect the USB device and re-run the script and it does work for some magic reason.

cardshare007 · 2023-06-18T15:07:03Z

Thanks mate, seems a bit more complex than I initially thought. I will give it another shot next weekend, but for now I'll leave it. I also hope the OTA will appear in a few months, seems to be my best bet ;-)

rpvandoorn · 2023-07-10T09:20:01Z

Hi all,

Just for my understanding. Can I already use the BLE updater for the C122 ?

Thanks all for you efforts on this project.

pvvx · 2023-07-11T17:03:26Z

I will start considering the OTA option (firmware update via Bluetooth) only after the end of summer, when we run out of warm weather.
And it is desirable that by that time someone has support for receiving advertising the "Tuya" format. Otherwise, support for BLE advertising in the "Tuya" format will never appear in anyone's open-source.

TrevorVr · 2023-11-27T19:33:48Z

I will start considering the OTA option (firmware update via Bluetooth) only after the end of summer, when we run out of warm weather. And it is desirable that by that time someone has support for receiving advertising the "Tuya" format. Otherwise, support for BLE advertising in the "Tuya" format will never appear in anyone's open-source.

Hi! It's been pretty chilly lately, any chance of a Ota update for these? :)

pvvx · 2023-11-28T18:01:40Z

You forgot about the second point of the conditions.
Nobody wants to deal with Tuya.
Closed rospogrigio/localtuya#1166 as completed.
custom-components/ble_monitor#1063
...

christiaandouma · 2023-12-01T19:31:31Z

Nice work so far. I got two of c122 flashed. They work and can connect with smart life from tuya! After a minute or two they go offline and don't report their status anymore untill i remove the battery and readd them in the app.

Just wondering if we can expect zigbee because that is something thats not dependend on the smart life app and online access. Next to that it would be easy to integrate into home assistant.

Was looking at https://github.com/pvvx/ZigbeeTLc but don't seem to get it to work

Anyway thanks so far!

pvvx · 2023-12-01T21:23:46Z

Was looking at https://github.com/pvvx/ZigbeeTLc but don't seem to get it to work

What didn't work?
I don’t have an MHO-С122 and have nothing to test it on.
And there is an even more exotic option - https://github.com/pvvx/BZdevice
https://github.com/pvvx/BZdevice/raw/master/bin/1141-020b-01113001-ZMHOC122.zigbee
But there are still problems with BLE OTA...

christiaandouma · 2023-12-01T23:33:50Z

@pvvx I was able to flash with https://pvvx.github.io/ATC_MiThermometer/USBCOMFlashTx.html and the tuya binary. I couldnt flash the zigbee binary using the same url. How should I flash with the zigbee version ?

Monacoslo · 2023-12-04T08:10:39Z

This is for TH05?

pvvx · 2023-12-04T09:10:21Z

This is for TH05?

MHO-С122

pvvx/ZigbeeTLc#22

TH05 - > SoC: PHY6222QC-W04I - Doesn't have an SDK for GCC. Only commercial version of the compiler.

almirus · 2023-12-15T20:22:08Z

@pvvx это не оно? https://github.com/SoCXin/PHY6222

pvvx · 2023-12-15T21:12:59Z

No. This is the SDK from the PHY website shown earlier in the link.
But http://wiki.phyplusinc.com/ is not available.

https://github.com/SoCXin/PHY6222 использует Keil_v5\UV4\UV4.exe
https://developer.arm.com/documentation/101454/0103/License-Agreements-and-Terminologies/License-Agreement-MDK-v5-39-and-above

almirus · 2023-12-16T08:41:12Z

@pvvx еще выпросил такое https://drive.google.com/file/d/1ampd3RjbV4Fp-GXDELiUjieXbbrWp-Hx/view?usp=drive_link

pvvx · 2023-12-16T09:31:35Z

christiaandouma · 2023-12-23T23:11:47Z

@pvvx @FaBjE I was able to flash with https://pvvx.github.io/ATC_MiThermometer/USBCOMFlashTx.html and the tuya binary. I couldnt flash the zigbee binary using the same url. How should I flash with the zigbee version ?

Hi @pvvx I am a bit lost of the flasher pages give me a
00:03:06: Searching for devices
00:03:10: Connecting to: C121
00:03:11: Not found Telink OTA service!

What am I doing wrong (am I doing something wrong?)
I did manage to usb flash it using https://pvvx.github.io/ATC_MiThermometer/USBCOMFlashTx.html but there is no Zigbee binary to flash from this website.

pvvx · 2023-12-23T23:14:21Z

https://github.com/pvvx/ZigbeeTLc

christiaandouma · 2023-12-24T09:43:22Z

@pvvx same issue. Give a

Not found Telink OTA service!

pvvx · 2023-12-24T12:04:04Z

TelinkMiFlasher does not work with the original Meawow MHO-C122 firmware. Firmware is carried out using wires...
Further OTA will work in TelinkMiFlasher.

christiaandouma · 2023-12-24T13:47:09Z

Ok I did the flash using wires. After flashing tuya app sees the device but TelinkMiFlasher still don't work after and gives the same message like before.

…

On Sun, Dec 24, 2023, 13:04 Victor ***@***.***> wrote: TelinkMiFlasher does not work with the original Meawow MHO-C122 <https://pvvx.github.io/MHO_C122/> firmware. Firmware is carried out using wires... Further OTA will work in TelinkMiFlasher. — Reply to this email directly, view it on GitHub <#339 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKZTDY5V3SV2CFW7Q7CN733YLAK37AVCNFSM6AAAAAAYAOVNRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGUYDANJRGQ> . You are receiving this because you commented.Message ID: ***@***.***>

FaBjE mentioned this issue May 28, 2023

MHO-C122 LCD Fixes #344

Closed

pvvx added a commit that referenced this issue May 28, 2023

https://github.com/pvvx/ATC_MiThermometer/issues/339#issuecomment-156…

b5c61fc

…6161613

pvvx mentioned this issue May 28, 2023

Support new Tuya BLE? custom-components/ble_monitor#1063

Open

pvvx mentioned this issue Jun 7, 2023

phy6222 controller support. #268

Closed

pvvx mentioned this issue Jul 13, 2024

Another TY0201 by _TZ3000_bjawzodf with display pvvx/ZigbeeTLc#107

Open

FaBjE mentioned this issue Jul 26, 2024

MHO-C122: No info on LCD pvvx/ZigbeeTLc#109

Open

pvvx mentioned this issue Oct 22, 2024

LYWSD002MMC - TLSR8250 based! pvvx/BZdevice#5

Open

pvvx mentioned this issue Nov 16, 2024

TH03 custom firmware pvvx/ZigbeeTLc#129

Open

Meawow MHO-C122 (2AWMOMHOC122) support #339

Meawow MHO-C122 (2AWMOMHOC122) support #339

Comments

FaBjE commented May 13, 2023 • edited Loading

Introduction

Meawow MHO-C122 (2AWMOMHOC122)

Exteriour

Interiour

Software

ToDo List

AvA1970 commented May 13, 2023 • edited Loading

killabeenl commented May 17, 2023

NH-Networks commented May 19, 2023

ZekiZico commented May 20, 2023

FaBjE commented May 20, 2023 • edited Loading

Things I have learned

ZekiZico commented May 20, 2023

NH-Networks commented May 20, 2023 via email

FaBjE commented May 21, 2023

Things I Learned

pvvx commented May 21, 2023

pvvx commented May 22, 2023 • edited Loading

pvvx commented May 23, 2023 • edited Loading

FaBjE commented May 26, 2023 • edited Loading

pvvx commented May 27, 2023 • edited Loading

pvvx commented May 28, 2023 • edited Loading

pvvx commented May 28, 2023 • edited Loading

pvvx commented May 28, 2023 • edited Loading

FaBjE commented May 28, 2023

FaBjE commented May 28, 2023

pvvx commented May 28, 2023 • edited Loading

pvvx commented May 29, 2023

https://developer.tuya.com/en/docs/iot-device-dev/OTA_BLE

FaBjE commented May 29, 2023

pvvx commented May 30, 2023 • edited Loading

pvvx commented May 30, 2023 • edited Loading

pvvx commented May 30, 2023 • edited Loading

FaBjE commented May 30, 2023 • edited Loading

FaBjE commented Jun 10, 2023

cardshare007 commented Jun 17, 2023

pvvx commented Jun 17, 2023 • edited Loading

NH-Networks commented Jun 18, 2023

cardshare007 commented Jun 18, 2023

cardshare007 commented Jun 18, 2023

cardshare007 commented Jun 18, 2023

FaBjE commented Jun 18, 2023

cardshare007 commented Jun 18, 2023

rpvandoorn commented Jul 10, 2023

pvvx commented Jul 11, 2023

TrevorVr commented Nov 27, 2023

pvvx commented Nov 28, 2023

christiaandouma commented Dec 1, 2023 • edited Loading

pvvx commented Dec 1, 2023

christiaandouma commented Dec 1, 2023

Monacoslo commented Dec 4, 2023

pvvx commented Dec 4, 2023 • edited Loading

almirus commented Dec 15, 2023

pvvx commented Dec 15, 2023 • edited Loading

almirus commented Dec 16, 2023

pvvx commented Dec 16, 2023 • edited Loading

christiaandouma commented Dec 23, 2023 • edited Loading

pvvx commented Dec 23, 2023

christiaandouma commented Dec 24, 2023

pvvx commented Dec 24, 2023

christiaandouma commented Dec 24, 2023 via email

FaBjE commented May 13, 2023 •

edited

Loading

AvA1970 commented May 13, 2023 •

edited

Loading

FaBjE commented May 20, 2023 •

edited

Loading

pvvx commented May 22, 2023 •

edited

Loading

pvvx commented May 23, 2023 •

edited

Loading

FaBjE commented May 26, 2023 •

edited

Loading

pvvx commented May 27, 2023 •

edited

Loading

pvvx commented May 28, 2023 •

edited

Loading

pvvx commented May 28, 2023 •

edited

Loading

pvvx commented May 28, 2023 •

edited

Loading

pvvx commented May 28, 2023 •

edited

Loading

pvvx commented May 30, 2023 •

edited

Loading

pvvx commented May 30, 2023 •

edited

Loading

pvvx commented May 30, 2023 •

edited

Loading

FaBjE commented May 30, 2023 •

edited

Loading

pvvx commented Jun 17, 2023 •

edited

Loading

christiaandouma commented Dec 1, 2023 •

edited

Loading

pvvx commented Dec 4, 2023 •

edited

Loading

pvvx commented Dec 15, 2023 •

edited

Loading

pvvx commented Dec 16, 2023 •

edited

Loading

christiaandouma commented Dec 23, 2023 •

edited

Loading