@richrobuk Unfortunately, that’s just how it works. Neither the valve display nor the Kasa app shows the actual status of the valve. The display text is "hardcoded" to say "heating to xx°C," whether the valve is open or closed. Ideally, I’d like to see general information indicating whether it’s "on" or "off," along with how much it’s currently open. See my thread here: https://community.tp-link.com/en/smart-home/forum/topic/714708?replyId=1439292

You might find this thread interesting: https://community.tp-link.com/en/smart-home/forum/topic/706792

  @Wayne-TP 

That is the problem precisely. WHY doesn't it show "THE CHANGE IN MODE"? You state yourself "But the device itself switches back and forth between heating and pause heating according to the set temperature."

I need this information to automate, If Mode = 'Heat' then Action.... What is the point in a status that indicates 'Heat' when it's heating and 'Heat' when it's not heating? Which is exactly what we currently see in Google Home..

  @Wayne-TP 

Copy of part of an email thread I am having with TP Link.

Hi TP-Link & all

Trigger: >25℃

 

Condition：6:00-7:30

 

But what if I decide to shift the schedule from 7:30 to 8:00? I then need to change the schedule for the TRV set point AND edit the rule...

 

Can you tell me what is the point of the 'Mode' characteristic on the TRV? It always says 'Heat' regardless of the state (Mode) of the TRV. As I have already pointed out, if this changed (when the TRV is not calling for heat) from 'Heat' to 'Idle/Closed/Off' that would work. In the Kasa app you can see that the app recognises the state... The 3 wavy lines turn Grey when the TRV is not calling for heat. Please make this data available to the user.

So why can the 'Mode' not change based on what ever data is driving this change in the Kasa app..

 

It feels as if TP is doing all they can to avoid recognising that this is an error, and trying everything to deflect the feedback. Why can you not fix this? If you fix this you have a Powerful product, without the fix, you have just another smart TRV...

 

Regards Richard

  @richrobuk 

Just use Home Assistant for boiler automation, as of now it likely is the only possible way until TP-Link improve external integrations. Heating status is broken in Google Home, broken via Matter, broken in Kasa app and correct in Tapo app (but there are no compatible switches for the boiler).

HA would only turn on/off the boiler based on TRV heat demand. Temperature changes and schedule could be done in any other way, also manually on the knob.

  @Trobalabau 

Hi Thanks for answering.. I get the feeling TP just don't want to admit it's broken..(and such an easy fix too).

I'm looking at HA. It's been a while since I've done any coding. How easy is it to get this coded/automated in HA? I've no experience with HA at all...

  @richrobuk 

Easy, if you have any experience e.g. with booting Windows installer, entering UEFI settings etc. - just basic computer literacy. I suggest cheap low-power Lenovo, HP, Wyse, Fujitsu thin client for like 30-40$.

Later on, you just need to know a few HA-specific terms like what is an "entity" etc.

TP-Link integration can be added directly from HA. Automation rules usually require no coding at all, but it might be easier to edit larger condition trees in code than visual editor. While the main mode of TRV is always "heating" (or "off"), rule can use hvac_action instead (heating or idle). I can share my automation rule later, after I finally change it from periodic status query to trigger-based.

  @richrobuk 

I have achieved this using google home script editor.. have you tried this?

I can post some more info later 

  @JMRewop 

Would love to know how... I couldn't find it . Please do share..