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

New UI controls incomplete / not working #131

Open
phoenixtechnam opened this issue Dec 9, 2023 · 11 comments
Open

New UI controls incomplete / not working #131

phoenixtechnam opened this issue Dec 9, 2023 · 11 comments

Comments

@phoenixtechnam
Copy link

phoenixtechnam commented Dec 9, 2023

Since HA update to 2023.12.0 my airconditioners based on IRHVAC cannot be controlled properly anymore. Target temperature is not displaying and cannot be be set via UI. See screenshot below:

image

@cociweb
Copy link
Contributor

cociweb commented Dec 9, 2023

Similar to this:
home-assistant/frontend#18950

@phoenixtechnam
Copy link
Author

yes, but the problem is not the missing modes, those can be added via additional card configuration. The real problem is that I cannot set target temperatures anymore. It also seems to mix up the current temperature and the target temperature.

@cociweb
Copy link
Contributor

cociweb commented Dec 10, 2023

As You can see in the legacy ticket, the target temp. is also missing. (The 70F -next to the icon- should be the current temp.)

@cociweb
Copy link
Contributor

cociweb commented Dec 10, 2023

well, I was aware to reproduce by a faulty formed json: if you are not initialize the temperature value, and the default value is null, then it can happen that you miss the +/- buttons and you are not able set the temp. <= Since you are not able to set any target temp, then you will get back null. :D - vicious circle...
As a workaround try to set it at least once with your IR remote, or send a correctly formed mqtt message for tasmota.

@cociweb
Copy link
Contributor

cociweb commented Dec 10, 2023

According to this, there is another way of thinking in my mind...
What if....
if you are not able to set the temp by the thermostat card....
from your default configuration temperature should derive. Have you set default temperature in your yaml config? anyways, it should be set other than 'null' by default....
So 3 option can pops up:
a) the new thermostat card overwrites the default target_temp value with 'null'
b) the default values are not working somehow as here reported
c) somehow Tasmota returns 'null' value instead of None and it is not handled well here

Eg:

{"StateMode": "SendStore", 
....
"Power": "off", 
"Mode": "off", "
Celsius": "on", 
"Temp": null, 
"FanSpeed": "max",
"SwingV": "auto", 
"SwingH": "off", 
...}

Instead of:

{"StateMode": "SendStore", 
....
"Power": "off", 
"Mode": "off", "
Celsius": "on", 
"Temp": 25, 
"FanSpeed": "max",
"SwingV": "auto", 
"SwingH": "off", 
...}

Some developer opinion would be appreciated!

@phoenixtechnam
Copy link
Author

According to this, there is another way of thinking in my mind... What if.... if you are not able to set the temp by the thermostat card.... from your default configuration temperature should derive. Have you set default temperature in your yaml config? anyways, it should be set other than 'null' by default.... So 3 option can pops up: a) the new thermostat card overwrites the default target_temp value with 'null' b) the default values are not working somehow as here reported c) somehow Tasmota returns 'null' value instead of None and it is not handled well here

Eg:

{"StateMode": "SendStore", 
....
"Power": "off", 
"Mode": "off", "
Celsius": "on", 
"Temp": null, 
"FanSpeed": "max",
"SwingV": "auto", 
"SwingH": "off", 
...}

Instead of:

{"StateMode": "SendStore", 
....
"Power": "off", 
"Mode": "off", "
Celsius": "on", 
"Temp": 25, 
"FanSpeed": "max",
"SwingV": "auto", 
"SwingH": "off", 
...}

Some developer opinion would be appreciated!

min_temp, max_temp and target_temp are all set in my config

@reloadxero
Copy link

here is what i did to restore functionality, you only have to do it once per entity:

  1. In HA go to "Developer Tools"
  2. Select "Services" tab
  3. Select service "Climate: Set target temperature"
  4. Select target climate entity and enter a temperature (any temperature is ok)
  5. Hit "Call Service"

As soon as you make this service call the thermostat entity is going to get the target temperature information, the plus and minus buttons as well as full functionality.

@BigHomie90
Copy link

Thank you @reloadxero ! Even after HA restart, works as it should.

@phoenixtechnam
Copy link
Author

Thank you @reloadxero, confirmed working

@Michel01975
Copy link

Thank you @reloadxero

@parcox
Copy link

parcox commented Feb 18, 2024

here is what i did to restore functionality, you only have to do it once per entity:

  1. In HA go to "Developer Tools"
  2. Select "Services" tab
  3. Select service "Climate: Set target temperature"
  4. Select target climate entity and enter a temperature (any temperature is ok)
  5. Hit "Call Service"

As soon as you make this service call the thermostat entity is going to get the target temperature information, the plus and minus buttons as well as full functionality.

Thank you @reloadxero, it's working. FYI, I have 3 tasmota-irhvac configured devices, one of them had this issue after HA 2024.2 update.

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

No branches or pull requests

6 participants