-
Notifications
You must be signed in to change notification settings - Fork 526
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
fix for caldo up t wifi #2033
fix for caldo up t wifi #2033
Conversation
fan modes cannot be connected with presets, device does not like work like this.
I don't see how this is an improvement |
I see you have changed the dps_val for fan speed, but can you provide a local log to show one of these values? Because if it is just taken from the iot.tuya.com developer portal, there can be differences between cloud and local values like this. I have to assume the originally supplied values were correct in absence of any evidence. |
@make-all this is improvement in a way that previous version simply did not work with this device. I was originally adding this device in PR 1296, but after modification you did and that were merged it did not work. This PR is fixing that. |
|
dps: | ||
- id: 1 | ||
type: boolean | ||
name: hvac_mode | ||
mapping: | ||
- dps_val: true | ||
value: heat | ||
value: "heat_cool" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a heater, there is no reason to change this from heat to heat_cool, as it is not capable of automatically switching between heating and cooling.
@@ -4,20 +4,18 @@ products: | |||
name: Olimpia Splendid Caldo Up T | |||
primary_entity: | |||
entity: climate | |||
translation_only_key: heater | |||
dps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no good reason to remove the translation_key.
- dps_val: false | ||
value: "off" | ||
- id: 2 | ||
type: integer | ||
name: temperature | ||
unit: C | ||
range: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing the unit is not just without reason, it breaks the integration on HA 2024.6 and later, which requires the unit to be set.
value: none | ||
- dps_val: "1" | ||
- dps_val: "level_1" | ||
value: "fan only" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fan_only is not a standard preset name. I think this is better left as "none", which conveys that compared to "comfort" and "boost", it provides no heating.
The device apparently uses level_1..level_3, not the "0".."2" that was originally included in the PR. PR #2033
The device apparently uses level_1..level_3, not the "0".."2" that was originally included in the PR. PR make-all#2033
- rename human_presence_sensor.yaml to more specific name. There is no evidence that is is generic enough to go without some identifier. PR make-all#2153, make-all#2150, make-all#2146, make-all#2145, make-all#2143, make-all#2137, make-all#2136, make-all#2134, make-all#2116, PR make-all#2087, make-all#2033
No description provided.