Here’s a bit more news…
I emailed support at MOES and to their credit they responded within 24 hours.
I’m not sure their initial response will help us much…
They recommend using their products with the SmartLife or TUTA app and not with HA as it’s an open source platform. They continue on to say we should “consult professionals” at www.zigbee2mqtt.io
I suppose we can take inference that they are not aware of any inherent hardware issues or they would have mentioned it.
I’m going to log an issue with zigbee2mqtt.io and see if anyone knows anything over there.
In the meantime - just a thought - do any of us have the ability to swap their TRV’s onto the SmartLife/TUYA app using a Zigbee Gateway ? - Just to see if this problem exists on that platform.
I would do it myself but my setup spans a large area so a single gateway is not going to handle the distances involved.
I have a Tuya Zigbee Hub I bought for my dad but he never used, let me look for it now.
Ok, I paired it easily with the Tuya Zigbee Gateway, this is the main screen:
And those are all settings:
I tried to play a bit with the settings and the TRV seems to correctly react to the changes.
I tried to see what changes in the ZHA device when I do changes in the Tuya app and it is not reacting to temperature change.
In summary:
Change in Tuya - Device updates - ZHA not
Change in Device - Tuya updates - ZHA not
Change in ZHA - Device not - Tuya not
I guess pairing it with the Tuya device something stopped in the link with ZHA.
I’ll keep it in Tuya and monitor how it reacts for some time.
Great stuff ! Yes, keep an eye on it.
I have just posted into the Github forum for Z2M lets see if anything useful comes back from that as well.
“Great” to see more people having the same issue.
Let’s hope we’ll find the solution.
Any update on how the TRV’s perform when connected to the Tuya Zigbee Gateway?
Is it a Gateway thing or a trv thing?
Is the issue now resolved?
Sorry for the delay in responding to this issue. As far a I am aware the issue still exists (well, it does for me !).
For the last couple of weeks I’ve been involved with alpha testing of Z2M firmware working directly with the author. It’s not quite ready for beta testing yet but when it is I suggest we all upgrade to it first and then take another look at this TRV issue.
I will post again as soon as I have any more information to share.
Thx for the update Nick.
Same issue on z2m with Sonoff ZBDongle-E
I had a mix of Hive TRV and 3 x Moes BRT-100, never had a single issue with them not responding, bought 8 more Moes BRT-100 and now I am having the same connectivity issues. I’m going to figure out if its the same ones, but i have a feeling its a signal issue with them.
I found that this issue occurs when one of my plugs are plugged to ungrounded socket TS011F_plug_1/BSD29_1, tested with many backup plugs. After moving that one plug to grounded socket TRVs seems to work correctly.
So what you’re saying is: That using the TS011F_plug_1 in ungrounded socket results in the TRV’s having the issues? So everybody who’s having these issues, is using a TS011F_plug_1 in a ungrounded socket?
For now ~10 days without issues after removing this plug (before I had problems every 3-4 days).
I think it’s something else. I’ve started to have these issues recently, and I have only 2 ZB devices in my “network” except SkyConnect coordinator (this TRV and reflashed Xiaomi temperature/humidity sensor).
It refuses to accept commands quite randomly, and also interesting thing is that it has LQI ~150-160 in Z2M dashboard, but on the map it’s random - sometimes 0, sometimes value from dashboard (150-160).
So not sure if I maybe need to buy a router and place it in the middle between coordinator and TRV, but I can’t be sure it’s really related to signal strength 
Is it published anywhere on github? Can community help with testing / development?
Haven’t forgotten this thread. Still in alpha test with the Z2M firmware which is really refusing to play nicely. I promise I’ll be back here as soon as I have an update.
Still not forgotten this ! - I won’t go into detail here but rest we have been testing everyday since my last post. The Z2M issue has put up a fight at every turn and it’s not quite over yet ! - Days now I hope ! Will report back when I will hopefully have some better news.
So happy the summer is coming. 
Er, well, yes ! - Please believe me when I tell you we are still testing - I kid you not - I (and other alpha testers) have installed and tested over 30 firmware iterations over these last few months. However I think we are very very close to a breakthrough.
I’m reliably informed if the current iteration holds firm then the cause of ll these Z2M failures is nailed !
And trust me there will be no one more pleased than me to crack this TRV issue we have all suffered !
Hang in there good buddies !