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

Gen 1 shelly devices including but not limited to HT sensor not displaying Fahrenheit only Celsius #107131

Closed
sungla55guy opened this issue Jan 4, 2024 · 16 comments · Fixed by #107683

Comments

@sungla55guy
Copy link

The problem

Since upgrading to 2024.1.0 all my shelly HT sensors only display Celsius and won't update when I change the change the unit of measurement. All of my shelly devices have the latest firmware installed

What version of Home Assistant Core has the issue?

2024.1.0

What was the last working version of Home Assistant Core?

2023.12.4

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

shelly

Link to integration documentation on our website

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

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

@home-assistant
Copy link

home-assistant bot commented Jan 4, 2024

Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of shelly 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 shelly Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


shelly documentation
shelly source
(message by IssueLinks)

@glyndon
Copy link

glyndon commented Jan 4, 2024

Same problem here (using core), and I found a temporary workaround: While attempting to change the scale from C to F, also change the display precision - to anything other than its current state. Then press 'Update' and the scale will be at F.
Until the next restart of HA, at which point one must repeat this action.

@smatthew
Copy link

smatthew commented Jan 6, 2024

Problem still exists in 2024.1.2, and it's pretending ALL readings were always Celsius, completely ruining historical data.

Screenshot 2024-01-06 at 7 33 11 AM

@thecode
Copy link
Member

thecode commented Jan 6, 2024

Please download the diagnostics from the device card in Home Assistant and attach it in a comment.

@glyndon
Copy link

glyndon commented Jan 6, 2024

I have 3 Shelly HT sensors. All do the same thing at every HA restart.
Here is the diag from one of them:

config_entry-shelly-3ed0f9c561fa10dd754b73fc771038ca.json.txt

@thecode
Copy link
Member

thecode commented Jan 6, 2024

According to the diagnostics everything is correct in your setup, lets wait for someone to try to investigate or information from other affected devices so maybe we can figure out the problem.

@glyndon
Copy link

glyndon commented Jan 6, 2024

Note that one can work around it in the UI by changing more than just 'range', then the setting sticks until restart.
It's ignored otherwise - click 'Update' and nothing is changed. This is new behavior since 2024.1.0, and a new incorrect UI behavior (to immediately ignore a setting change unless another setting is also changed).

I'm mentioning this in hope that it provides a hint pointing to the locus of the bug.

@exactmike
Copy link

same issue here with multiple HTs

@JasonJanelle
Copy link

I'm also having the issue with all 6 of my HTs.

@toolman196
Copy link

I also have this same problem I think I notice it when 2023.12 release to 2024.1 beta release like to one has said that we can manual change from C to F and will be fine until restart of HA. I have also removed all Shelly H&T re-added them back in everything is fine until I restart HA. It is larger than just Shelly's H&T just noticed that one of the flood sensor from Shelly is also reporting temp in C and not F in HA. All Shelly are configured to report in F and not C. I am not really monitoring that temp sensor have not noticed it.

@doabbs
Copy link

doabbs commented Jan 8, 2024

Seeing this with all Shelly H&T as well as H&T Plus. 2024.1.2

@glyndon
Copy link

glyndon commented Jan 9, 2024

FWIW, I just tested with just-released aioshelly==7.1.0 (and confirmed that it stayed at that version, having edited .../shelly/manifest.json to accept it).

No change WRT this problem.

@bieniu
Copy link
Member

bieniu commented Jan 9, 2024

I spent some time on this problem yesterday and I can actually reproduce it, but so far I haven't found the cause. There were no changes related to unit conversion in the Shelly integration and the problem only applies to sleeping devices, so I suspect that the issue occurs when restoring the state from registry when starting Home Assistant.

Please do not comment "same issue here", 👍 in the open post is enough.

@bdraco
Copy link
Member

bdraco commented Jan 9, 2024

I ordered one of these devices to try to find the root cause, should be here next week

@tomeralgai
Copy link

Came here to say that this same thing is happening with shelly flood as well.

One way around is to change the temp to kelvin and then back to fahrenheit. But this is annoying and needs to be done after every update.

@bdraco bdraco changed the title shelly HT sensor not displaying Fahrenheit only Celsius Gen 1 shelly devices including but not limited to HT sensor not displaying Fahrenheit only Celsius Jan 9, 2024
@bdraco
Copy link
Member

bdraco commented Jan 9, 2024

We found the root cause of this issue. A short term fix is forthcoming until a longer term redesign to solve some underlying issues can be made.

@github-actions github-actions bot locked and limited conversation to collaborators Feb 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.