search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.4k stars 30.3k forks source link

Can't change temperature or humidity units in the UI #76158

Closed vaibhav2912 closed 1 year ago

vaibhav2912 commented 2 years ago

The problem

I upgraded to HA core 2022.8 today which introduced the bluetooth integration.

I added my Govee H5075 using this integration but I am not able to change the temperature unit from °F. It is stuck on °F. I can't change it to °C or K.

This started out as an issue with bluetooth integration but we realized that this is an issue with Home Assistant itself. Units for temperature and humidity entities can't be changed in the UI.

For more details, see this post: https://github.com/home-assistant/core/issues/76158#issuecomment-1204496877

What version of Home Assistant Core has the issue?

2022.8

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

Link to integration documentation on our website

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

govee_ble documentation govee_ble source (message by IssueLinks)

probot-home-assistant[bot] commented 2 years ago

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (govee_ble) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

bdraco commented 2 years ago

The temperature is reported in your instances native units. You'll need to change them and restart to see C

vaibhav2912 commented 2 years ago

The temperature is reported in your instances native units. You'll need to change them and restart to see C

I tried changing it to C and also K using the dropdown menu on the entity options. When I click update, the entity options menu goes away but the unit is left at F. Also did a restart. Still see F as the unit.

bdraco commented 2 years ago

The integration itself reports in C so its got to be your system config at http://...../config/general

Screen Shot 2022-08-03 at 10 38 57 AM
vaibhav2912 commented 2 years ago

I don't want to change my system config to C. I want just this one sensor to report in C. Is this not possible?

vaibhav2912 commented 2 years ago

Changing my system to C also changed the sensor reporting to C but as I said above, I prefer to only have this one sensor report in C. Everything else I would still like to be in F.

bdraco commented 2 years ago

This is not possible. The integration is reporting it in C, but it will get show in the native units the system is configured to use. There is no way to change this.

bdr99 commented 2 years ago

If there is no way to set the unit for an individual sensor entity, then why does each sensor entity have its own "Unit of Measurement" drop-down menu?

image

vaibhav2912 commented 2 years ago

Sorry for this question but did something change recently in Home Assistant?

Also I had this same exact govee sensor working with ble_monitor integration. In that as well I had changed the unit to C but now when I try to do the same, it doesn't work.

I have aqara zigbee temperature sensor that I remember setting to C and it is still in C even when my system is in F. Now when I try to change that to F, it doesn't work. image

bdraco commented 2 years ago

If there is no way to set the unit for an individual sensor entity, then why does each sensor entity have its own "Unit of Measurement" drop-down menu?

I don't think that will change how the underlying entity reports. It probably works for everything but temps

vaibhav2912 commented 2 years ago

If there is no way to set the unit for an individual sensor entity, then why does each sensor entity have its own "Unit of Measurement" drop-down menu?

I don't think that will change how the underlying entity reports. It probably works for everything but temps

I am pretty sure this used to work for temperature entities. I had this same sensor working with ble_monitor integration and I had changed the unit to C. I have removed that integration now to use this new integration so I don't have the proof of that. But see in my reply above. I have a aqara zigbee sensor that I was able to change to C when I added this sensor some time ago but now when I try to change the unit to F or K, it doesn't work.

vaibhav2912 commented 2 years ago

Changing units for entities is definitely broken. I tried changing unit for humidity. This also doesn't work.

https://user-images.githubusercontent.com/20019445/182713956-e72188f8-8c73-4075-b433-eed4b133f9a5.mp4

ecard0 commented 2 years ago

Will this be fix soon ? Thanks :)

mathmaniac43 commented 2 years ago

I am experiencing this same issue. I have several machines with Glances running on them. My native temperature unit (which I use for ambient temperature) is F, but I converted all of the Glances units to C several HA releases ago. I am running 2022.8.4, and just added a new computer with Glances, but its units are stuck with F despite my trying to change them, exactly what @vaibhav2912 was seeing.

chronicrebellion commented 2 years ago

I can also confirm this issue on 2022.8 and later.

I had to revert back to 2022.7.7 to allow for changing of temperature entities' unit of measure (also from Glances)

chronicrebellion commented 2 years ago

@emontnemery was wondering if you had any insight on this?

erikpendragon commented 2 years ago

same issue 2022.9.0, has not resolved the issue. is this a front end issue or core?

vaibhav2912 commented 2 years ago

same issue 2022.9.0, has not resolved the issue. is this a front end issue or core?

How can I check if this is frontend issue or core?

meminens commented 2 years ago

I cannot replicate this issue on 2022.9.1. Have you tried it with 9.1?

erikpendragon commented 2 years ago

Home Assistant 2022.9.1 Supervisor 2022.09.0 Operating System 9.0.rc2 Frontend 20220907.0 - latest

This is what I am running now, but I have had this problem for a couple months now, it worked the first month it was released but not after that.

chronicrebellion commented 2 years ago

The last version where changing the temperature units worked for me was 2022.7.7 All versions afterwards (including 2023.9.1) has broken this functionality

I am using Glances temperature entities to test.

erikpendragon commented 2 years ago

Home Assistant 2022.9.4 Supervisor 2022.09.0 Operating System 9.0 Frontend 20220907.2 - latest

fixed this issue for me.

chronicrebellion commented 2 years ago

I can concur. I updated my Home Assistant Core container to 2022.9.4 and temperature units can be changed once again.

vaibhav2912 commented 2 years ago

Home Assistant 2022.9.4 Supervisor 2022.09.0 Operating System 9.0 Frontend 20220907.2 - latest

fixed this issue for me.

Home Assistant 2022.9.4 Supervisor 2022.08.6 Operating System 8.5 Frontend 20220907.2 - latest

I am also on 2022.9.4 now and the problem is resolved.

@erikpendragon, I se you are on supervisor 2022.09.0 and operating system 9.0. I see those releases in the GIT repository but when I check for updates, I don't get an option to update to those releases.

These releases are also not in beta they are public releases but I still don't get an option to upgrade to latest supervisor and OS versions.

Is it may be because you on the beta channel and beta channel users have early access to these releases?

erikpendragon commented 2 years ago

@vaibhav2912 i am on the beta release path.

vaibhav2912 commented 2 years ago

@vaibhav2912 i am on the beta release path.

Thanks for confirmation.

I don't know who can help here but my concern is that if this was fixed by chance then this issue might come back in later releases.

Is there a way to check what the problem was and what fixed it?

github-actions[bot] commented 1 year 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.

vaibhav2912 commented 1 year ago

The issue is solved since HA 2022.9.4. I am now on HA 2022.12.8 and units change works so the issue is resolved.