Issues with Zemismart M6 Hub exposing Thermostatic Radiator Valve to Apple HomeKit

[fangping.guo]

The mapping configuration has been updated. Please test it again.

[kafarek]

Thank you. I have again restarted gateway and readded Valve subdevice. It is still not working as expected, but it's almost there.
When I set to Off mode via HomeKit, and then exit HomeKit app and go back - the device is "not responding". I can change Off mode to Heat mode in HomeKit if I open the accessory, but I cannot do this change using the icon in the Room or Summaries View.
Please check the video below. From 01:39 you can see this behavior as I click on the icon (the temperature value) to set the mode to Off, exit HomeKit app and go back - the accessory is not responding.

Current Valve virtual ID: bfd0e02948c5731020dh6b

[fangping.guo]

Hello, due to my company's network firewall, I cannot access YouTube. Could you please upload the video as an attachment?

Regarding the unresponsive issue you mentioned, due to the opacity of Apple's environment, it's difficult for us to completely locate and resolve this problem. Have you encountered similar issues in other ecosystems (such as Home Assistant)?

[kafarek]

Hello
I have added video as attachment in zip format (I cannot upload mp4 directly as attachment to this forum).

I don't have currently any other ecosystems configured that I can test this behavior.

Please check the video from attachment and let me know if there is something you can do with this unresponsive issue. Thank you.

[fangping.guo]

Between the time when the device was added and when you completed your operation, the device's two-way state synchronization was working properly. The device is only recognized as unresponsive by Apple Home when it is in the "off" mode. Even so, I can see that you were still able to switch it to heating mode, and the status was successfully synchronized to the Tuya app.

I fully understand the phenomenon described in the video. I will do my best to try and find a suitable device to reproduce and debug this issue. However, since the cause is unknown, I cannot guarantee a timeline for resolution. Thank you for your understanding.