core icon indicating copy to clipboard operation
core copied to clipboard

Reset missing on SOLAX sensor

Open jcwessels opened this issue 2 years ago • 9 comments

The problem

When using the default Energy dashboard, the current power production for today is not shown. In the configuration screen for the dashboard, the following error message is shown: The following entities have a state class (state class) 'measurement' but 'last_reset' is missing: sensor.solax_73dc0aae_today_s_energy****

What version of Home Assistant Core has the issue?

core-2023.8.2

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

Solax

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

The standard integration is used without any modification. The value is displayed on the normal dashboard, but not on the energy dashboard.

jcwessels avatar Aug 16 '23 13:08 jcwessels

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

Code owner commands

Code owners of solax 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 solax Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


solax documentation solax source (message by IssueLinks)

home-assistant[bot] avatar Aug 16 '23 13:08 home-assistant[bot]

Hallo, any news on this problem? I have an old solax inverter that has the same problem

LolloKappa avatar Oct 11 '23 18:10 LolloKappa

No news yet, no response at all.Verstuurd vanaf mijn iPadOp 11 okt 2023 om 20:28 heeft Lorenzo Cossu @.***> het volgende geschreven: Hallo, any news on this problem? I have an old solax inverter that has the same problem

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

jcwessels avatar Oct 11 '23 18:10 jcwessels

Same problem here :(

skank01 avatar Nov 01 '23 14:11 skank01

I think state_class should be total_increasing instead of measurement

skank01 avatar Nov 01 '23 14:11 skank01

All After changing state_class; error is gone and visible in energy dashboard

skank01 avatar Nov 01 '23 15:11 skank01

Thanks, when are we able to use this?Verstuurd vanaf mijn iPhoneOp 1 nov 2023 om 16:08 heeft skank01 @.***> het volgende geschreven: All After changing state_class; error is gone and visible in energy dashboard

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

jcwessels avatar Nov 01 '23 15:11 jcwessels

All After changing state_class; error is gone and visible in energy dashboard

Where you change it?

marcocamy avatar Nov 29 '23 21:11 marcocamy

This issue is affecting me, I hope the PR can be accepted soon.

bradnak avatar Feb 25 '24 23:02 bradnak

I just checked my full logs, it looks like today_s_energy, month_s_energy, grid_exported_energy and grid_imported_energy are all throwing the error that it is the wrong state class. I wondered whether this was stopping me from adding the Export and Import to the Energy Dashboard, but "Today's Energy" works as a Solar Production sensor, despite being errored on my server. I'm happy to do some more testing if required.

bradnak avatar Mar 05 '24 07:03 bradnak

is there anything that I can do to speed up the process?

jcwessels avatar May 13 '24 09:05 jcwessels

I guess you could review and/or test #114743. Who knows, you might do it at just the right time to get someone important to look at it.

Darsstar avatar May 14 '24 19:05 Darsstar

For as far as I can tell, code looks good. Not able yet to test the actual code in production.

jcwessels avatar May 19 '24 17:05 jcwessels

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.