Tuya Climate integration for Pioneer has wrong temp set

jhandel commented 1 year ago

The problem

When using Tuya to integrate with a Pioneer Heatpump the Set Temp needs to be divided by 10 when using temp_set or allowed to switch to temp_set_f as temp_set_f shows the correct information.

What version of Home Assistant Core has the issue?

2023.7.2

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

Tuya

Link to integration documentation on our website

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

Diagnostics information

tuya-742074a825fccd869aaa53f82a284332-Mini Split-5d5059b2323e4379ee8089b08eb019d1.json (2).txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Please switch the driver to use temp_set_f or divide temp_set by 10 for display and use by the rest of HomeAssistant.

home-assistant[bot] commented 1 year ago

Hey there @tuya, @zlinoliver, @frenck, mind taking a look at this issue as it has been labeled with an integration (tuya) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `tuya` 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 tuya` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

tuya documentation tuya source _{^{(message by IssueLinks)}}

nickbouressa commented 1 year ago

I am seeing the same issue on 2023.9.1 although the scaling seems more wrong. For example a set point on HA of 163 corrisponds to 74F.

issue-triage-workflows[bot] commented 11 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

nickbouressa commented 11 months ago

Hi, do not close this issue. It is not resolved. The issue remains as discribed above.

Core 2023.12.1 Supervisor 2023.11.6 Operating System 11.2 Frontend 20231208.2

gsrpoweredsi commented 10 months ago

I have the same issue.

issue-triage-workflows[bot] commented 7 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

gsrpoweredsi commented 7 months ago

This is still an issue. I have 3 Pioneer mini splits in my Tuya account, integrated in HA, shows the set temp correctly in F but the actual/ambient temp shows the incorrect F temp like 174 degrees because of this issue.

Camwise1 commented 6 months ago

I just added a mini split to my Tuya account and agree the climate control values are incorrect. I manually set my mini split to 61 degrees F. In HASS it shows a setting of Cool to 142F. Display of Current Temp is accurate though.

issue-triage-workflows[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Camwise1 commented 3 months ago

This is still an active and annoying issue

issue-triage-workflows[bot] commented 2 weeks ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / core