Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tolerance for quick turn on/off not respected? #1567

Closed
MaJerle opened this issue Jan 13, 2025 · 2 comments
Closed

Tolerance for quick turn on/off not respected? #1567

MaJerle opened this issue Jan 13, 2025 · 2 comments
Assignees
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@MaJerle
Copy link

MaJerle commented Jan 13, 2025

Description

I have my tolerance set to 0.3 degrees which should not trigger the thermostat to go on until temperature drops to below target - 0.3. But I am noticing that it goes on immediately as soon as temp goes below target.

This is annoying since it can change the state every 10 minutes or so, draining the battery.

Steps to Reproduce

  1. Create BT
  2. Set tolerance
  3. Try

Expected behavior:

When tolerance is set (in my case 0.3) I'd expect the values are respected.

Actual behavior:

The thermostat goes on as soon as temperature goes below the target, not respecting the tolerance values.
In my case, heating is turned on as soon as temperature goes to 21.9 while set to 22.

Versions and HW

Home Assistant: 2025.01
Better Thermostat: 1.6.1

TRV(s): SONOFF TRVZB

Debug data

diagnostic data
I can't download the diagnostic data, but I can provide my configuration:

image
image

graphs

This is my history graph, BT for the office

image

Additional Information

@MaJerle MaJerle added the new bug incoming bug issue label Jan 13, 2025
@MaJerle
Copy link
Author

MaJerle commented Jan 13, 2025

Here is another example of my bedroom thermostat, which has same config but also triggers at 0.1 decrease:
image

@folfy
Copy link
Collaborator

folfy commented Jan 13, 2025

Duplicate of #1314

@folfy folfy marked this as a duplicate of #1314 Jan 13, 2025
@folfy folfy closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2025
@folfy folfy added bug Something isn't working duplicate This issue or pull request already exists and removed new bug incoming bug issue labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants