MQTT; Web-Socket; HTTP BLU TRV API's who is ?

[xvs03]

Hello, I have an (old) Shelly TRV with WIFI only. This has the interfaces and protocols mentioned in the topic. For this reason, I have decided to use Shelly again. Now I am shocked to discover that the APIs mentioned are not supported. So I can't send TRV commands to the gateway with a simple browser or the MQTT Explorer. It's funny, with the old TRV it works, it gets the valve position via my OpenHAB system and that processes the actual temperature from an ESP DIY sensor. So we are now at the beginning of winter and I would like to see the same APIs provided as with the old TRV. Otherwise the device is useless for my smart home system and actually for any smart home system I would be really disappointed as a loyal Shelly Fan. We need open interfaces! Please...

Edited November 8 by xvs03

[Sacha]

HTTP access via BLU Gateway Gen3 is documented here: https://shelly-api-docs.shelly.cloud/gen2/Devices/Gen3/ShellyBluGwG3/

Note regarding the call "http://192.168.33.1/rpc/BluTrv.GetRemoteStatus?id=200"

If you have paired an external BLU H&T to a TRV the temperature of the external sensor will be reported in this field: "current_C". Not the internal one.

What i am missing: GetRemoteStatus should also report the humidity value of the Blu H&T!

Greetings

Sacha

 

[xvs03]

Thanks for the answer Sacha, but the only method that can set the temperature is the

BluTrv.Call example with the TRV.SetTarget command

http://192.168.33.1/rpc/BluTrv.Call?id=200&method="TRV.SetTarget"&params={"id":0,"target_C":22}

This method probably sends a new target temperature.

But I am still missing the method for giving the valve position in % as in the old TRV.

According to BLU Devices, this should be the TRV.SetPosition method.

I have changed the example to this method.

http://192.168.33.1/rpc/BluTrv.Call?id=200&method="TRV.SetPosition"&params={"id":0,"pos":100}

I will try this out next week with the HTTP request.

Thank you for now, I'll get back to you with the report