Shelly TRV without CoIoT/COAP -

I received my first TRV last week. Setting it up worked for the very basics, but I am failing to get it integrated into HomeAssistant using the Shelly integration. It was discovered, but I can't connect to it to configure the discovered device. When debugging, my packet sniffer shows that the HomeAssistant node connects to the TRV using HTTP (get /shelly and get /settings). But when it tries to connect via COAP the TRV responds with a port closed error. And when I use the browser to pull the /settings, it indeed reports

"coiot":{"enabled":false,"update_period":3600,"peer":""}

A bit further, the hwfinfo is reported as hardware revision to be a development prototype.

"hwinfo":{"hw_revision":"dev-prototype","batch_id":0}

Does anybody else have this hardware revision? And does anybody else see CoIoT disabled?

Ok, in the meantime, I found the switch to enable the CoIoT in the device's own web UI (not the app, not the cloud). It now shows up in HomeAssistant, but as read-only, i.e. I cannot use it an actuator in any scene or automation. Also, in the Shelly Cloud, it is not possible to use it as an action in a scene...

This contradicts the advertised capabilities, at least I don't see any other obvious way to trigger a TRV to close the valve based on a Shelly Door&Window detecting an open window...

Any ideas?