Moes BRT-100-TRV not reporting after OTA update

[wizu]

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]

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]

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

[wizu]

Termostat works ok and show firmware U1, or UI

[vladi1234]

Does z2m pairing work correctly?

[wizu]

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

[vladi1234]

I need more information.

I need result.

[CVKBaca]

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 <#7941 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASPMHLT4VMTWPJEX2FPY3ALTXM5EBANCNFSM47ZLL3KA> .

[wizu]

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

[vladi1234]

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]

[vladi1234]

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:
Koenkk/zigbee-OTA@8c90178

[wizu]

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

[vladi1234]

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]

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

[vladi1234]

{
	"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]

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]

problem still exists

[CVKBaca]

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]

#5748 (reply in thread) crosslinking this too.

[vladi1234]

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?
Koenkk/zigbee-OTA#43 (comment)

@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]

@vladi1234 disabled the OTA update for now. (Koenkk/zigbee-OTA@4af6b2a)

[MattWestb]

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]

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]

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 :-))

[vladi1234]

Any information about fix of this issue? I wanted to implement these TRVs in whole house, fortunately I bought only one but at the moment after a while the device is loosing any communication and I can't update the firmware (as I don't have a standalone tuya gateway)...

@sokol07 Which TRV do you mean?

[sokol07]

Good question, I've bought it as "GTZ04 (Moes TS0601)" but it is listed in Z2M as _TZE200_cwnjrr72.
The OTA update is, as mentioned earlier, impossible due to the "No image available for imageType '5634'", which I guess means that the OTA is still disabled for this model?

[vladi1234]

Good question, I've bought it as "GTZ04 (Moes TS0601)" but it is listed in Z2M as _TZE200_cwnjrr72. The OTA update is, as mentioned earlier, impossible due to the "No image available for imageType '5634'", which I guess means that the OTA is still disabled for this model?

OTA update is currently deactivated for this TRV.

#7941 (comment)

That can still take a while.

[sokol07]

Yeah, I've read the topic, I now about the deactivation, I was just curious if you have any forecast about fixing this issue - is it "while" like 2 weeks or more lika 2 months?

[vladi1234]

On November 1st, PR will be merged.

[sokol07]

Thank you for update!

[vladi1234]

@wizu worked for you with OTA update?

[wizu]

@vladi1234 yes, I have updated one of my TRV and it looks like it is working ok. Tommorow I will try to update the rest of them

[vladi1234]

@wizu Super! Thanks!

[oopiicaa]

I can confirm too, upgrade went through okay, everyrhing seems to work.

[vladi1234]

Thanks!

[Coollision]

Hi sorry to poke a closed thread, but I recently acquired a Moes thermostat (HY368 _TZE200_cwnjrr72).
first thing I did was an ota update, and now it only reports its temp (also acts) once an hour even when heating so yeah small room == major overheating. is there a way arround this or a fix? currently it reports version 87

[amarce]

Hi,

The update is not appearing for me, I keep getting the error "No image available for imageType '5634'"

Mine is reported as _TZE200_b6wax7g0 and the firmware build date appears empty under the OTA section.

I'm using the version of zigbee2mqtt that comes with the last home assistant, should I update it or something?

appVersion is 64 BTW, I don't know if it's the last one:

'genBasic': {"appVersion":64}

Thanks a lot!

[vladi1234]

"No image available for imageType '5634'"

No image available Is correct, because Moes BRT-100-TRV "_TZE200_b6wax7g0" thermostat doesn't have its own firmware update yet.

"appVersion" 64 is the last current version.

[amarce]

Hi Vladi,

Understood.

Thanks a lot for the reply!

[henkiejan1]

Hi, i got yesterday this TRV and Zigbee2MQTT report also there is a update available from version 67 to 192. And more importantly it will not brick the device? Is there someone who could say it's safe to upgrade? I upgraded my Tuya TS011F powerplugs also from 67 to 192 without anyproblems. But a thermostat is not a power plug. ;)

[sgilyin]

Hi, i got yesterday this TRV and Zigbee2MQTT report also there is a update available from version 67 to 192. And more importantly it will not brick the device? Is there someone who could say it's safe to upgrade? I upgraded my Tuya TS011F powerplugs also from 67 to 192 without anyproblems. But a thermostat is not a power plug. ;)

DO NOT INSTALL THIS!!!
Today my thermostat was broken after this ota update ;-(

[ilvits]

Today my thermostat was broken too...

[HrzM83]

One more broken... @Koenkk please disable OTA for these TRVs!

[Koenkk]

@HrzM83 will be disabled in the 1 November update.

[falconslag]

Hello,

I've got 2 of my TVR (Moes BRT-100-TRV) which got updated to version192 and I cannot pair them too.

I've contacted Moes Support but I don't expect much from them.

How can I ensure none of my other TVR have the same issue?
I only know 1 is at version 67 with the update button available.
All others display nothing except "idle":
"update": {
"state": "idle"
},

I uderstand the OTA will be disabled the 1st November, but it may be useful for us if a downgraded firmware can be pushed to our TVR (Ex: Version 67) to ensure we won't be blocked in the future when we change battery for example.

And for those which do not pair using standard procedure, if someone can find any combinaison that work, he will be welcome.

Regards

[jonathh21]

Has anyone the ability to check if this is still an issue or are these devices destined to obsolete themselves with no updates?

Thanks

[falconslag]

Hi Jonath21,

I still have 3 of these which cannot be paires after the update and I can't find a way to downgrade them.

BUT as they were new, I manage to have them replaced for free.

If someone has got skill and component to play with them, I can see to send one for testing.

Regards.