AutoDIY
(Ettore)
August 13, 2025, 11:05pm
1
Hello,
I have set up a modbus climate with success and configuration looks like
modbus:
- name: name
type: tcp
host: IP_ADDRESS
port: 502
climates:
- name: "climate"
device_address: 64
address: 1607
input_type: holding
data_type: int16
max_temp: 30
min_temp: 17
offset: 0
precision: 1
scale: 1
target_temp_register: 1604
target_temp_write_registers: true
temp_step: 1
temperature_unit: C
hvac_mode_register:….
…..
The issue is the value for current temperature have to scaled but not the value for target temperature.
If I setup scale and offset then the target temperature value will not be realistic because of the scaling.
Should I use a template sensor to convert the current temperature attribute?
Then how can I use it in the modbus climate?
Any help appreciated.
You can’t. Use a generic thermostat instead.
AutoDIY
(Ettore)
August 13, 2025, 11:26pm
3
Hello,
well, yes maybe but I am bit confused and lost about how to, the generic thermostat lacks control for fan and modes.
What can I target as device heater, in fact there is no device switch?
In fact I am controlling a fan coil that have hvac modes ( heat, cool etc) and fan speed.
The rest is just target temperature and actual temperature.
There is a PR to include different scaling factor but is not approved yet.
Don’t know, is there a way? Can you point me in the right direction?
Consult with the device manual of the thermostat to see if it supports an external sensor.
If not, setup a generic thermostat to turn the climate mode of the modbus climate entity to “heat” when you want it to heat and “off” when you want it to not heat and adjust the target temperature such that it will heat.
AutoDIY
(Ettore)
August 14, 2025, 12:24pm
5
Hello,
is not a real thermostat, as I said is a fan coil conditioning air (cool/heat)
thanks looking into it.
AutoDIY
(Ettore)
August 19, 2025, 5:11pm
6
Hello,
as everything was working and it was just a visual matter I decided that for the moment I will use cardmod, hiding the climate temperature sensor and showing the template sensor.
Thanks for your help.
AutoDIY
(Ettore)
November 28, 2025, 10:30pm
7
Hello just to follow up the point of my request should be solved with this PR.
dev ← illia-piskurov:curr_temp_scale_and_offset
opened 09:21AM - 21 Aug 25 UTC
## Breaking change
## Proposed change
The documentation previously s… tated that scale and offset only applied to the target temperature.
This was incorrect: in reality they apply to both target and current temperature.
This PR adds the ability to configure separate scale and offset for current and target temperatures.
There are devices that require different scaling for target and current temperatures (for example, Cooper air conditioners). People have also reported this limitation on the forum:
https://community.home-assistant.io/t/wth-why-do-modbus-climate-entities-only-have-one-scale-setting-for-temperature-registers/803414
https://community.home-assistant.io/t/modbus-plataform-climate/323571
This was also discussed in PR: home-assistant/core#135848.
## Type of change
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: fixes https://community.home-assistant.io/t/wth-why-do-modbus-climate-entities-only-have-one-scale-setting-for-temperature-registers/803414
- This PR is related to issue: https://community.home-assistant.io/t/modbus-plataform-climate/323571
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/40770
- Link to developer documentation pull request:
- Link to frontend pull request:
## Checklist
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [x] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
2 different scales in one climate entity for setpoint and current temperature.
Normally will be included in 2025.12.0