Closed wizu closed 3 years ago
@jmarfer Then try this:
- For this you have to use the 'manual' position.
- Set 'current_heating_setpoint' 35°C room target temperature.
- Set 'eco_temperature' to '0', or '5' in any case less than the target room temperature.
- 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
Perfect @vladi1234, now it works for me. There has been a time when the 'current_heating_setpoint' dropped to 35 and I did not understand why. I will follow up.
One last thing. By putting the switch indicated in the climate, it works the other way around, that is, when it has to heat the valve it closes and when it has to go off the valve opens. Can I reverse this?
@jmarfer If you write automation scenario, it doesn't really matter 'on' or 'off'. I don't think you can optically swap things around.
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)...
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?
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?
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.
https://github.com/Koenkk/zigbee2mqtt/issues/7941#issuecomment-913752102
That can still take a while.
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?
On November 1st, PR will be merged.
Thank you for update!
@wizu worked for you with OTA update?
@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
@wizu Super! Thanks!
I can confirm too, upgrade went through okay, everyrhing seems to work.
Thanks!
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
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!
"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.
Hi Vladi,
Understood.
Thanks a lot for the reply!
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. ;)
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 ;-(
Today my thermostat was broken too...
One more broken... @Koenkk please disable OTA for these TRVs!
@HrzM83 will be disabled in the 1 November update.
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
Has anyone the ability to check if this is still an issue or are these devices destined to obsolete themselves with no updates?
Thanks
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.
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