Skip to content

Conversation

@MiguelDomingues
Copy link
Contributor

This device is a slightly different from the existing one at custom_components/tuya_local/devices/earu_k6h3aw_thermostat.yaml

Below is a screenshot of the device after adding it in the integration:
image

@github-project-automation github-project-automation bot moved this to 👀 In review in Tuya Local Oct 27, 2025
Removed the 'Working week' select entity configuration from the thermostat YAML file.
@MiguelDomingues
Copy link
Contributor Author

@make-all I've removed the duplicated entity 'Working week' can you trigger the workflows again please

make-all added a commit that referenced this pull request Oct 31, 2025
PR #3898, with reference back to #2602 for improvements and confirmation
@make-all
Copy link
Owner

I think this can be merged with the existing config

@make-all make-all closed this Oct 31, 2025
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Tuya Local Oct 31, 2025
@MiguelDomingues
Copy link
Contributor Author

Don't think it can be merged without breaking the existing one.

Besides several differences in the range values (min/max), there is this one that, in my opinion, could break the existing device: id 1 (mode) in existing device has program/manul/eco, while this new device has auto/manual/eco

make-all added a commit that referenced this pull request Nov 2, 2025
K6RH-3A goes to 95.0, while the original only goes to 90.0.
But the maximum temperature can be set separately, so we can expand this
range without causing any issue for the more limited model.

PR #3898
make-all added a commit that referenced this pull request Nov 2, 2025
K6RH-3A goes to 95.0, while the original only goes to 90.0.
But the maximum temperature can be set separately, so we can expand this
range without causing any issue for the more limited model.

PR #3898
@make-all
Copy link
Owner

make-all commented Nov 2, 2025

Did you try the updated config?

The preset_mode is actually the same, auto is mapped to program to take advantage of existing translations.
The only real differences are:

  • slight differences in additional entities, taken care of by putting them all in as optional and making them hidden if unavailable.
  • different capitalisation of ALL/all in sensor selection enum.
  • difference in upper temperature range. Initially I ignored this because I am not sure anyone really needs to set their thermostat between 90 and 95 degrees F, but since the logic to detect which model it is already exists for the ALL/all handling, I just changed it to reuse that logic for the temperature range as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants