Shelly TRV

Hi Aaron. My first Shelly trv has arrived. What do you need from me to try and see if this can be controlled?
Thanks. Simon

Having a bit of a play with this, I think the basics would involve enabling reporting temperature and valve status back into Indigo (and so enabling onwards to Homekit) so that Indigo can change the current set temp. Enabling boost and adjusting the boost minutes would also be handy.

I would be happy to adjust the actual programs in Shelly app for a while, although I would like a clever way to disable the programs via Indigo so that I can enable summer or holiday mode and prevent the heating coming on. (I think this can be done be disabling the schedule?).

It seems quite clever too in that you can address all thermostats together, ie to put into holiday mode (disable all schedules) or individually.

Having a bit of a play with this, I think the basics would involve enabling reporting temperature and valve status back into Indigo (and so enabling onwards to Homekit) so that Indigo can change the current set temp. Enabling boost and adjusting the boost minutes would also be handy.

I would be happy to adjust the actual programs in Shelly app for a while, although I would like a clever way to disable the programs via Indigo so that I can enable summer or holiday mode and prevent the heating coming on. (I think this can be done be disabling the schedule?).

It seems quite clever too in that you can address all thermostats together, ie to put into holiday mode (disable all schedules) or individually.

I'm going to try and take a stab at this today and implement the TRV as an Indigo thermostat with the heat setpoint only.

• I think I will be able to make an Indigo action that will initiate a boost for X minutes.
• I think I can use the "Off" HVAC mode in Indigo to tell the TRV to fully close the valve and disable itself. Going back into the "Heat" mode in Indigo would then send the appropriate commands to the TRV to go back into the automatic valve control mode based on the current temperature.
• If the TRV is running its own schedule, the Indigo UI would show the HVAC mode as "ProgramHeat".

I don't see any reason why you can't also use the Shelly app for your holiday stuff as Indigo will stay in sync with the data it reads from the device.

This might take us a few times of going back and forth until we get everything working as it should since I don't have a TRV myself.

Cheers.
Looking at the schedules, there is a Holiday one, so maybe just being able to change the live schedule program is good enough for an "override " Happy to help work at this.

In the meantime if anyone is reading this and interested in getting one, I have set up a simple Shims device to detect when the valve is open to turn on my boiler which enables this to work (ie actually heat my house) via the Shelly app for schedules and overrides etc until this works through the plugin.

[Edit - I see Karl's direct plugin supports the TRV and actions such as adjusting the setpoint and schedules, but doesnt expose it as a thermostat device so no control from Homekit etc as a standard indigo thermostat device]

Could someone explain how a few of the functions work on the TRV?

How does the "Boost" differ from "accelerated heating"? Does boost just go to 100% open valve for the set duration and ignore the temperature set point during that time?

If that is the case, would it be reasonable to use the Indigo UI "Heat On" HVAC mode setting for this? When changing to this mode - initiate a boost for the default duration. Then, post-boost, automatically switch back to the "Auto Heat/Cool" mode.

Indigo Modes

Screen Shot 2023-01-16 at 8.52.47 PM.png (23.12 KiB) Viewed 237 times

I think accelerated heating changed the logic it uses to determine valve % relative to set point. I don’t think we need an option to change from indigo? Can’t imagine once set is something that needs to be changed.
Yea boost just sets valve to 100% for x minutes. Not sure on its point really, I think I’d rather boost to x temp for y minutes so the room doesn’t get too hot.
As for programs maybe I’d use auto to indicate the schedule is in operation and heat otherwise? Not sure it needs to be set though as of it’s on auto ie a schedule and we change the set point manually then the trv likely reports that the schedule is no longer active and the mode would show heat. ?
As the TRVs aren’t ever off just set to a low set point I think, and is consistent with Jon’s TRV plug-in that can always be on heat or auto rather than use off?

As for operating the boost function happy for that to be an action rather than controlled by the thermostat itself.

Sorry for the delay, but I believe I have the device supported in this branch: https://github.com/AaronLionsheep/Shell ... ue-132.zip

If you are still willing, please give that a try and create a TRV device. It brings in the temperature sensor from the device as well as some additional state information (boost remaining, valve position, battery voltage, battery level, and calibration status).

There are 2 plugin actions: Start TRV Boost and Stop TRV Boost. These can be accessed from the plugin menu if you want to manually execute them. They also appear under the ShellyMQTT folder in trigger actions for any automations. The Start action lets you supply a boost duration, and the state should be updated as this value ticks down over time.

I have unit tests for this device, so I am very confident it works according to the documentation I have available. Please let me know if something doesn't work and I can adjust based on what MQTT messages you re seeing.

One thing to note: actions performed on the device do not immediately update the Indigo device. For example, setting the heat point in Indigo won't set the heat point locally. It will send the command to the device and the device should respond with its updated state. When the device responds with a new state, then Indigo will update the device locally. Basically, Indigo will show the state of the device as the device is rather than what Indigo thinks it should be.