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

Shelly HT devices reporting "state class not supported" and "No states available" Ref issue: #84009 #107973

Closed
werkstrom opened this issue Jan 13, 2024 · 5 comments · Fixed by #108052

Comments

@werkstrom
Copy link
Contributor

The problem

Appears same or alike problem as reported in #84009.

  • Shelly HT devices reports "state class not supported" and "no states available". It does so for all temperature, and humidity entities of the Shelly HTs.
    image

  • "States" shows no state_class:
    image

  • Statistics card does not show data. While it has been working for several years.
    image

  • Units appear to be working correctly:
    image

  • Data is present i DB.
    image

  • Am using the core integration:
    image

  • Issue appears to start in December. And units appear to have been dropping of since then.
    image

  • Nothing found in the log book for the devices

  • While this was working on 2023.12.x, the issue also started on 2023.12.x.

What version of Home Assistant Core has the issue?

core-2023.12.x -> 2024.1.3

What was the last working version of Home Assistant Core?

core-2023.12.X

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Shelly

Link to integration documentation on our website

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

Diagnostics information

config_entry-shelly-e3a62a399e109eb76cbafe49969ab02c.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Nothing found in the logs at all

Additional information

No response

@home-assistant
Copy link

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)

@werkstrom
Copy link
Contributor Author

Might well be duplicate of #107530, in which case this issue can be closed.

@thecode
Copy link
Member

thecode commented Jan 13, 2024

We identified the root cause for this in #107530 while the subject is different both issues are due to the same cause, we are working on a fix but due to the change needed it won't be before 2024.2

@thecode
Copy link
Member

thecode commented Jan 13, 2024

Might well be duplicate of #107530, in which case this issue can be closed.

Since the subject is different lets keep it open so it will be visible they are related, both will be closed once fixed

@werkstrom
Copy link
Contributor Author

All units statistics data now appear to work as of 2024.1.4 🎉🤩

@github-actions github-actions bot locked and limited conversation to collaborators Feb 20, 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.

6 participants