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

EVE Thermo Temperature Offset #138170

Closed
NrZer00 opened this issue Feb 9, 2025 · 2 comments · Fixed by #140579
Closed

EVE Thermo Temperature Offset #138170

NrZer00 opened this issue Feb 9, 2025 · 2 comments · Fixed by #140579

Comments

@NrZer00
Copy link

NrZer00 commented Feb 9, 2025

The problem

EVE Thermo firmware: 3.5.1, tested on multiple EVE Thermo

Since 2025.2.1 I noticed that I was able to set a temperature offset for my EVE thermostats. Before the update this was only possible through the EVE app.
When I started writing an automation for temperature offset calibration I noticed that the value range was from -2,5°C to +2,5°C. I am able to set it higher or lower in the gui without an error or a red mark around the input, but when you reload the page it shows the previous value, so values higher or lower to that range are not stored at all. In the EVE app however the offset range is from -5°C to +5°C.
If I set the offset via the eve app to let’s say -5°C Homeassistant will show only up to -2,5°C.

What version of Home Assistant Core has the issue?

core-2025.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

matter

Link to integration documentation on our website

https://www.home-assistant.io/integrations/matter

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Feb 9, 2025

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of matter can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign matter Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


matter documentation
matter source
(message by IssueLinks)

@martin-olsen
Copy link

Hey

I ran into samme issue. I don't know anything about how these things work but I would expect native_max_value and native_min_value in this section

MatterDiscoverySchema(
to be set to 50 and -50 instead of 25 and -25.

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

Successfully merging a pull request may close this issue.

2 participants