search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.1k stars 1.68k forks source link

Moes BRT-100-TRV not reporting after OTA update #7941

Closed wizu closed 3 years ago

wizu commented 3 years ago

What happened

Z2M showed me, that my TRV have an OTA update available, so I've updated it's firmware. https://www.zigbee2mqtt.io/devices/BRT-100-TRV.html#moes-brt-100-trv After successful upgrade I couldn't control it any more. I've removed it from Z2M and added again serveral times, but it didn't help. Not it only reports: { "child_lock": "UNLOCK", "eco_mode": "OFF", "linkquality": 34, "update": { "state": "idle" } } and there is nothing abnormal in the logs, about this device. Changing child lock from Z2M works, but nothing more.

Debug info

Zigbee2MQTT version: 1.20.0 commit: 41b67fd Adapter hardware: CC2538 + CC2592 Adapter firmware version: zStack30x 20200211

CVKBaca commented 3 years ago

I have the same problem. TVR does not respond after firmware upgrade but nothing abnormal in the logs..

Zigbee2mqtt version: 1.20.0-1 adapter: CC2652RB development stick with zigbee2mqtt firmware

vladi1234 commented 3 years ago

Hi, whether thermostat itself works? And what firmware version now shows thermostat?

wizu commented 3 years ago

Termostat works ok and show firmware U1, or UI

vladi1234 commented 3 years ago

Does z2m pairing work correctly?

wizu commented 3 years ago

Yes, I have tried that several times and it worked every time, but no difference.

vladi1234 commented 3 years ago

I need more information.

Bildschirmfoto vom 2021-07-12 22-46-23

I need result.

CVKBaca commented 3 years ago

sorry I dont see fw version :( [image: image.png]

po 12. 7. 2021 o 21:13 vladi1234 @.***> napísal(a):

Hi, whether thermostat itself works? And what firmware version now shows thermostat?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/7941#issuecomment-878527096, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASPMHLT4VMTWPJEX2FPY3ALTXM5EBANCNFSM47ZLL3KA .

wizu commented 3 years ago

Read result of 'genBasic': {"appVersion":87,"zclVersion":3,"stackVersion":0,"hwVersion":1,"manufacturerName":"_TZE200_b6wax7g0","modelId":"TS0601","dateCode":"","powerSource":3}

vladi1234 commented 3 years ago

Read result of 'genBasic': {"zclVersion":3,"appVersion":64,"stackVersion":0,"hwVersion":1,"manufacturerName":"_TZE200_b6wax7g0","modelId":"TS0601","dateCode":"","powerSource":3}

On my thermostat "appVersion" is: 64. I did not update.

CVKBaca commented 3 years ago

image

vladi1234 commented 3 years ago

Moes BRT-100-TRV thermostat does not have a firmware update yet. I think the thermostat got the wrong firmware update from Tuya.

Look here: https://github.com/Koenkk/zigbee-OTA/commit/8c9017844d110ea8d499da0158e0e4c85d8aa1d5

wizu commented 3 years ago

Is there a way to get it back to old firmware? @Koenkk

vladi1234 commented 3 years ago

Tuya and Moes have the same "modelId": "TS0601". That is not right. We have to speak to @Koenkk that he differentiates according to "manufacturerName": "_ TZE200_b6wax7g0" and not according to "modelId": "TS0601".

vladi1234 commented 3 years ago

Tuya and Moes also have the same "manufacturer code": 4098,

vladi1234 commented 3 years ago 
{
    "id": 17,
    "type": "EndDevice",
    "ieeeAddr": "0xcc86ecfffebxxxxx",
    "nwkAddr": 53108,
    "manufId": 4098,
    "manufName": "_TZE200_b6wax7g0",
    "powerSource": "Battery",
    "modelId": "TS0601",
    "epList": [
        1
    ],
    "endpoints": {
        "1": {
            "profId": 260,
            "epId": 1,
            "devId": 81,
            "inClusterList": [
                0,
                4,
                5,
                61184
            ],
            "outClusterList": [
                25,
                10
            ],
            "clusters": {
                "genBasic": {
                    "attributes": {
                        "65503": "�f|(\u0012�f|(\u0012",
                        "65506": 31,
                        "65508": 0,
                        "modelId": "TS0601",
                        "manufacturerName": "_TZE200_b6wax7g0",
                        "powerSource": 3,
                        "zclVersion": 3,
                        "stackVersion": 0,
                        "hwVersion": 1,
                        "dateCode": "",
                        "appVersion": 64
                    }
                },
                "genDeviceTempCfg": {
                    "attributes": {}
                },
                "genLevelCtrl": {
                    "attributes": {}
                },
                "msTemperatureMeasurement": {
                    "attributes": {}
                }
            },
            "binds": [
                {
                    "cluster": 0,
                    "type": "endpoint",
                    "deviceIeeeAddress": "0x00124b0022812735",
                    "endpointID": 1
                },
                {
                    "cluster": 61184,
                    "type": "endpoint",
                    "deviceIeeeAddress": "0x00124b0022812735",
                    "endpointID": 1
                }
            ],
            "configuredReportings": [],
            "meta": {}
        }
    },
    "appVersion": 64,
    "stackVersion": 0,
    "hwVersion": 1,
    "dateCode": "",
    "zclVersion": 3,
    "interviewCompleted": true,
    "meta": {},
    "lastSeen": 1626155319566
}
github-actions[bot] commented 3 years ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

wizu commented 3 years ago

problem still exists

CVKBaca commented 3 years ago

I confirm the same problem. I also found out that after the OTA firmware update, it is no longer possible to set the device to pairing mode. I tried to reset the device manually via the AE function and entering a value "01", but even that didn't help.

bruvv commented 3 years ago

https://github.com/Koenkk/zigbee2mqtt/discussions/5748#discussioncomment-1119126 crosslinking this too.

vladi1234 commented 3 years ago

Explanation of problem:

Moes BRT-100-TRV thermostat doesn't have its own firmware update yet. Our Moes BRT-100-TRV thermostat got the wrong firmware update from unknown Tuya thermostat.

Because both manufacturers Tuya and Moes have the same "modelId" and "manufacturerCode". Tuya "modelId": "TS0601", "manufacturerCode": 4098 Moes "modelId": "TS0601", "manufacturerCode": 4098

zigbee-OTA only recognizes according to "modelId" and "manufacturer code". This means that all Tuya and Moes termostats get the wrong upgrade. Specifically this "https://github.com/Koenkk/zigbee-OTA/raw/master/images/Tuya/1615190575-si32_zg_uart_connect_sleep_ZS5_ty_OTA_1.1.7.bin" file.

zigbee-OTA / index.json

    },
    {
        "fileVersion": 87,
        "fileSize": 234174,
        "manufacturerCode": 4098,     <-------------<<<<<<<<<<<<<<<
        "imageType": 5634,
        "sha512": "1113486a67403d922fc4a462b7477e0a0986fa8862a89b74ab8c5eac7b4ecb31c30f1da9ae1bbc1d6d50ae1fed66d38c37a1834ab71fd384c0555002783aba13",
        "url": "https://github.com/Koenkk/zigbee-OTA/raw/master/images/Tuya/1615190575-si32_zg_uart_connect_sleep_ZS5_ty_OTA_1.1.7.bin",
        "path": "images/Tuya/1615190575-si32_zg_uart_connect_sleep_ZS5_ty_OTA_1.1.7.bin"
    },
    {

That is not right!!!

I've already asked the right people about it, but I haven't received an answer yet. I would like to know which thermostats are these files for? https://github.com/Koenkk/zigbee-OTA/pull/43#issuecomment-888394556

@Koenkk must change "zigbee-OTA" so that it differentiates according to "manufacturerName": "_ TZE200_b6wax7g0" and not just according to "modelId": "TS0601" and "manufacturerCode": 4098

Koenkk commented 3 years ago

@vladi1234 disabled the OTA update for now. (https://github.com/Koenkk/zigbee-OTA/commit/4af6b2a99517f57c0111566a9735b40ecdbc2af7)

MattWestb commented 3 years ago

The interesting is wot image type the TRV was reporting before the update and wot is reporting after then requesting one new OTA file.

"imageType": 5634, is the image type in the OTA file and shall being matches with the device is reporting or its being one "converting" of the device type by the file.

The model name is not in the file locked only manufacture code and image type for the OTA file. Some device is using the same OTA image but have different device name like IKEA On/Off and Open /Close buttons is having the same firmware with the same image type and manufacture code but have different data setting in the device and is having different model names in the basic cluster (and completely different clusters and function).

vladi1234 commented 3 years ago

Hello!

The OTA update for unknown TS0601_thermostat is deactivated for the time being!

That's fine, so you can't break thermostats anymore!

But, there are already thermostats that have received faulty updates (defective).

You can try to read firmware from good thermostats.

And then restore firmware on broken thermostats.

The question: Who can try to read firmware?

MattWestb commented 3 years ago

You need one SWD / J-Link probe (if its one EFR32MG21 chip you need one real J-Link) for reading the flash of the Zigbee module and if can dumping the internal flash pleas also dumping the "user data" that can having device specific setting for the device.

One working method: https://github.com/MattWestb/IKEA-TRADFRI-ICC-A-1-Module/tree/master/Flashing-MG

I have dumped the tuya ZBGW (ist one EFR32MG1B) and one tuya LED Strip controller with EFR32MG21 and they was not debug locked so dumping was working OK :-))

pawol commented 3 years ago

Is it possible to force an update manually for HY-368 (white moes clone) by means of zigbee2mqtt?

Here is binary and I know that it works well with my TRVs. https://github.com/Koenkk/zigbee-OTA/tree/master/images/Tuya

At the moment it looks that OTA update is locked in zigbee2mqtt

vladi1234 commented 3 years ago

Is it possible to force an update manually for HY-368 (white moes clone) by means of zigbee2mqtt?

Here is binary and I know that it works well with my TRVs. https://github.com/Koenkk/zigbee-OTA/tree/master/images/Tuya

At the moment it looks that OTA update is locked in zigbee2mqtt

What "manufacturerName:" does "HY-368" TVR have? Do you mean this "1615190575-si32_zg_uart_connect_sleep_ZS5_ty_OTA_1.1.7.bin" file?

I would like to try to create PR for the final solution.

pawol commented 3 years ago

"1615190575-si32_zg_uart_connect_sleep_ZS5_ty_OTA_1.1.7.bin"" should be fine for this TRV: https://allegro.pl/oferta/tuya-inteligentna-glowica-termostatyczna-na-wifi-9665242363

At the moment I have 3 pieces of TRV updated (earlier by zigbee2mqtt - it was working) and 1 not updated yet. I would like to do it but OTA is locked now

vladi1234 commented 3 years ago

I still need to know which "manufacturerName:" has "HY-368" TVR?

For example: Bildschirmfoto vom 2021-09-03 13-48-06

bruvv commented 3 years ago

afbeelding Can I be of any help @ vladi1234

wizu commented 3 years ago

Model Zigbee TS0601 zigbee_manufacturer _TZE200_cwnjrr72

And I also have _TZE200_ckud7u2l

Thats two of my HY-368

pawol commented 3 years ago

Since August 2021 an OTA update worked OK with it: trv

Now I get after OTA update: image

bruvv commented 3 years ago

Well this is what it is showing on my end in the OTA field: afbeelding

vladi1234 commented 3 years ago

Thanks!

vladi1234 commented 3 years ago

Model Zigbee TS0601 zigbee_manufacturer _TZE200_cwnjrr72

And I also have _TZE200_ckud7u2l

Thats two of my HY-368

@wizu are you sure that the _TZE200_cwnjrr72 and _TZE200_ckud7u2l are compatible?

wizu commented 3 years ago

I bought 10 of _TZE200_cwnjrr72 a week ago and they look the same. But had no chance to update it so I don't know if they will work with this firmware - I think they will. I will try to update one of them when the OTA will be available.

wizu commented 3 years ago

@vladi1234 so yes, let's assume that they are compatible and I will check that on my own TRV.

MattWestb commented 3 years ago

Keep in mind that most tuya TRVs is coming with 2 different Zigbee modules TZE200 and TYST11 and can having the same tuya MCU and if flashing the wrong version is very likely not working or braking the zigbee module or changing the comport so it cant communicating with the tuya MCU.

Also the Zigbee OTA file is only updating the Zigbee module on TS0601 device and not the tuya MCU that must being done with tuya (DP) commands.

So updating the Zigbee module is not helping with problems in the tuya MCU that is the TRV controller only fixing "zigbee problems" like bad cluster setting or reporting settings from zigbee cluster (that is barley not used on this devices) then the tuya MCU is only using the Zigbee module as one "tunneling" device for its communication with tuya cloud.

artkrz commented 3 years ago

I think z2m should have an option to mark device with "ignore fw update checks" or something similar. If device works well enough it doesn't have to be updated.

vladi1234 commented 3 years ago

Ich denke, z2m sollte eine Option haben, um das Gerät mit "Ignore fw update checks" oder ähnlichem zu markieren. Wenn das Gerät gut genug funktioniert, muss es nicht aktualisiert werden.

Bildschirmfoto vom 2021-09-05 09-21-34

You can switch off here.

If the device works well enough, it doesn't need to be updated. ------> Then just don't do it!

vladi1234 commented 3 years ago

First part of my OTA update PR has already been merged with z2m, but the second part of PR has to wait another 2 months, then it will be merged. Reason see here: https://github.com/Koenkk/zigbee-OTA/pull/50#issuecomment-913736281

wizu commented 3 years ago

Great, thanks @vladi1234

CVKBaca commented 3 years ago

is there any chance of repairing malfunction devices (_ TZE200_b6wax7g0) in the future with correct firmware via OTA update?

vladi1234 commented 3 years ago

The possibility exists only if we have OTA update file.

muddy79 commented 3 years ago

First part of my OTA update PR has already been merged with z2m, but the second part of PR has to wait another 2 months, then it will be merged. Reason see here: Koenkk/zigbee-OTA#50 (comment)

Well, I understand the reason, but it means there will be people like me who are unable to update their MOES TS0601 devices (_TZE200_ckud7u2l), which is crucial to get them working properly: without update, the device goes to sleep state and it's not possible to use it via HA. I've just installed 6 of them, the heating season is about to start at my area, and I just found out the OTA update is not possible... :( Any suggestions?

MattWestb commented 3 years ago

OTA can checking the version of Z2M and if its old its blocking the update and if in pace with Z2M is allowing the update but its need some more code being added and all use dont need waiting so long.

Safs commented 3 years ago

Is any news about TS0601 update?

jmarfer commented 3 years ago

Good Morning. I cannot use this valve for my automations because it does not show system mode (to be able to switch HVAC between heat, auto and off). Would this be contemplated in the next update? When is it expected?

Thanks

vladi1234 commented 3 years ago

Moes BRT-100-TRV thermostat does not have to have a 'system mode' either. It works very well in any automation scenario.

  1. For this you have to use the 'manual' position.

  2. Set 'current_heating_setpoint' that what you need room target temperature.

  3. Set 'eco_temperature' to '0', or '5' in any case less than the target room temperature.

  4. To switch off the heating you have to use 'eco-mode_on' and to switch on 'eco-mode_off'.

eco-mode_on = off eco-mode_off = auto boost_heating_on = heat (1 - 15 minutes adjustable)

In any case, I am very satisfied with it.

jmarfer commented 3 years ago

boost_heating_on

Thanks for the quick reply.

Actually I need to create a thermostat and dispense with the valve temperature sensor, using an external one. I only need a valve opening and closing switch. With another valve I have succeeded but with this I am not capable.

Following your indications, when I put "boost_heating_on = heat" the valve changes but in a while it returns to its original position.

Is there a way to get a "clean" valve open / close switch to use in a climate?

Thanks again

vladi1234 commented 3 years ago

@jmarfer Then try this:

  1. For this you have to use the 'manual' position.

  2. Set 'current_heating_setpoint' 35°C room target temperature.

  3. Set 'eco_temperature' to '0', or '5' in any case less than the target room temperature.

  4. To switch off the heating you have to use 'eco-mode_on' and to switch on 'eco-mode_off'.

eco-mode_on = off eco-mode_off = on