Closed apbarratt closed 2 weeks ago
Hi! Just wanted to say that I have the same heating/warming values but for hvac_action_dp 3
Brand and model of my thermostat is Magnum MRC
I have done a lot of work qualifying my DPs and I think I've found the issue. My HVAC options are not Heat/Warming
but rather heating/warming
.
To be honest, I'd much prefer some ability to map these options too, especially as warming
is not really accurate when the underfloor heating hasn't been on for quite some time.
An ideal solution would be one matching the select entity, where I can type heating;warming
as options and map these to more realistic Heat;Idle
that I'd expect from other thermostats such as my Nest.
I have managed to resolve the issue by adding these options to the code base and have opened a PR: https://github.com/rospogrigio/localtuya/pull/1177
Thanks for your followup @apbarratt. Yes for me heating means the thermostat is actually heating the floor while warming means it's idle
The problem
Hi guys, I have an unusual smart thermostat for my underfloor heating that works far better using localtuya than it does using the official tuya integration. When using the official integration for instance, the only data available is on/off (represented by "heating / cooling" or Off, despite having no kind of cooling feature" and the target temperature. Through Local Tuya, I am able to show the current temperature, the hvac mode (as heat/off) and the target temperature. It'd be neat to be able to also show the additional floor temperature but not a big deal right now.
The issue I'm having is the so called hvac_action. On my device this is represented as heating or warming. With warming being what is shown when no heating is on, regardless of whether it's been on at all.
Anyway, I've been able to set this up in my configuration, I've got hvac_action_dp set to 118 (which has a value of "warming" or "heating" as noted. And I've set hvac_action_set to "Heat/Warming".
However, when I look at this thermostat's list of attributes, hvac_action simply isn't there where on other thermostats provided by other integrations it is. I'm not entirely sure if this is a localtuya issue or something else.
Environment
Steps to reproduce
{{ states.climate.your_thermostat }}
hvac_action
is not shown in the object.Configuration
configuration.yaml
orconfig_flow
DP dump
I think that's in the stuff above though I'd note I can never actually get this to update past the state it was when I first configured the component.
Provide Home Assistant taceback/logs
Additional information