[Huisbaasje] When using sensor.gasverbruik_vandaag for Energy dashboard, gas usage between 0:00 and 1:00 is the total of the day before shown negative.

[Calimerorulez]

The problem

Just set up the Huisbaasje integration (for my gas usage, I do not use the electricity function), using sensor.gasverbruik_vandaag for the Energy dashboard, the accumulated gas usage from the day before is shown as negative value between 0:00 and 1:00 the next day, because the value of the sensor is reset at 0:00.

There is no other gas usage sensor provided by the integration to use in the Energy dashboard that I can find.

Is it an option to add total increasing sensors?

What version of Home Assistant Core has the issue?

core-2023.11.1

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

Huisbaasje

Link to integration documentation on our website

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

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]

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

Code owner commands

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

_{^{(message by CodeOwnersMention)}}

---

huisbaasje documentation
huisbaasje source
_{^{(message by IssueLinks)}}

[dennisschroer]

That is strange! I checked my own instance and everything seems to be working fine there.

Do you also see these negative values in the Huisbaasje/Energyflip app?

[floristotle]

I am having the same issue

[Calimerorulez]

@dennisschroer

Mag het in het Nederlands? :)

Ik zie geen negatieve waarden in de Energyflip app. Ik heb het vaker gezien in het verleden in het Energy dashboard, dat als je een sensor koppelt aan het Energy dashboard, die zichzelf om 0:00 uur reset, dat dan de totale waarde van de vorige dag als teruglevering, of liever gezegd, 'omgekeerde' waarde wordt getoond tussen 0:00 uur en 1:00 uur.

Zo kwam ik onder andere dit topic tegen:

https://community.home-assistant.io/t/new-template-sensors-for-energy-start-new-day-with-negative-value/330651

Ik denk dat het Energy dashboard er vanuit gaat dat er een, in mijn geval, gassensor waarde wordt aangeboden die alleen maar stijgt en niet zichzelf om 0:00 uur reset naar 0.

Is het een optie om zo'n sensor toe te voegen, eentje die alleen maar oploopt? Vind ik ook voor andere zaken wellicht handig ;)

[koningdde]

Hallo allemaal,

Ik zie hetzelfde gebeuren, wat mij opvalt is het volgende:
De huisbaasje gasmeter gaat om 23:55 van totaal gebruik naar 0. De elektriciteit meting doet dit ook op hetzelfde moment.

Het gasverbruik in het energie dashboard in het uur tussen 00:00 en 01:00 staat dan op de waarde van de dag ervoor op erin als negatieve waarde.
Het elektriciteit verbruik reageert anders en registreert wel goed.
Wellicht dat er iets verkeerd gaat met de tijden waarop de meters gereset worden of de berekening van het gas verbruik.

Hi All,

The same is happening at my system.
What i see happening:
The huisbaasje gasmeter drops to zero at 23:55. The electrical meter does this also at the same moment.

The gas usage in energy dashboard shows, in the first our between 00:00 and 01:00 the full gas usage from the day before in negative value.
Look like a timing or calculation problem.

Thanks!

[joerimul]

We had the same issue today (since 3 november); the state_class of the gas_today sensor was incorrect. It had the total state_class instead of total_increasing. As a workaround, you can overwrite this via configuration.yaml:

homeassistant:
customize:
gas_today:
state_class: total_increasing

[Calimerorulez]

homeassistant:
customize:
gas_today:
state_class: total_increasing

@joerimul
Thanks, I will try that :)

[arjanhs]

Having the same and it started when I removed the older hacks based solution and using the HA integrated version now

[Calimerorulez]

@arjanhs
I can confirm @joerimul's solution works.

[arjanhs]

Good to hear, only have some problems with the format within the configuration.yaml file. Haven't done this in a while.

[Calimerorulez]

@arjanhs

Just like this:

homeassistant:
  customize:
    sensor.gasverbruik_vandaag:
      state_class: total_increasing

I'm using a two space indentation.

[arjanhs]

Thanks @Calimerorulez now wait and see if it works tomorrow.
Update: problem solved, thanks again @Calimerorulez and @joerimul

[koningdde]

Works for me also! Thanks.

[JeroenvIS]

I'm also having this issue. Good to see that there's a workaround.

I haven't done any development for Home Assistant yet, but: if a workaround is to override the state class of the sensor, wouldn't a proper solution be to change that class in the source of the integration?

Looks like this is the relevant line: https://github.com/home-assistant/core/blob/dev/homeassistant/components/huisbaasje/sensor.py#L200
...and I guess that
state_class=SensorStateClass.TOTAL
should be replaced with
state_class=SensorStateClass.TOTAL_INCREASING
then?

[dennisschroer]

Yes the fix is as simple as that. I will see if I can change that in one of the next days. Otherwise, feel free to do so yourselves :P

[Calimerorulez]

Thanks all!

Should I remove the work around from my config once a new version of HA Core is released?

homeassistant:
  customize:
    sensor.gasverbruik_vandaag:
      state_class: total_increasing

[JeroenvIS]

@Calimerorulez IMHO it would indeed be cleaner when you remove the workaround once running a release with the fix. I don't expect that leaving it in will break anything, but it's unneeded clutter when the underlying issue has been resolved.