Flume Values are Too Large after 2022.11.3 Core Update #82336

zSprawl · 2022-11-18T17:51:52Z

The problem

In the update released yesterday, the following change was implemented for the Flume water monitoring integration:

#81968

It has caused the "current flume value" showing water to be 5 times larger. The change above increased the polling interval by 5 times, so it lines up perfectly with the issue.

The Flume website and API show 2 gallons, the value in Home Assistant is displayed as 10 gallons, which of course set off all kinds of alarms at my house as we searched for the leak.

What version of Home Assistant Core has the issue?

core-2022.11.3

What was the last working version of Home Assistant Core?

core-2022.11.2

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Flume

Link to integration documentation on our website

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

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 · 2022-11-18T17:51:57Z

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

Code owner commands

Code owners of flume can trigger bot actions by commenting:

@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Change the title of the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign flume Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

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

jeeftor · 2022-11-18T18:00:42Z

Most interesting....

I increased the time for polling to 5 mins because multiple devices were timing out due to api limits.

Did it as a temporary patch with the eventual goal to scale based on device count - but I'm not sure why that's causing this issue.

I'll have to take a look but I'm currently traveling for thanksgiving.....

zSprawl · 2022-11-19T04:43:13Z

No problem.

It only appears to affect the "real time" value, aka sensor.flume_sensor_home_current, so the new water charts and such aren't affected.

jordahlm · 2022-11-21T04:57:37Z

I'm seeing the same thing. I had set up an automation to turn on my bathroom fan if the flow rate I've found to indicate a shower was sustained for 4 minutes. After the 2022.11.3 update this was getting constantly triggered just by small water usage. I thought it was just the 5 minute polling period but looks like this issue is at play as well. Hopefully we can get the adaptable polling rate based on device count that was mentioned in place soon!

mermelmadness · 2022-11-22T23:17:33Z

Following as I've noticed the same, but only with the current usage reading. My daily total seems to be in line with my normal usage.

tcallaw · 2022-12-13T03:56:16Z

I am seeing the same thing. Current usage is reading much higher than actual. Daily and monthly totals line up with the totals in the Flume app.

rmcginty · 2022-12-18T19:54:13Z

Same as others report. Current high but all other values match app.

jeeftor · 2022-12-20T16:20:35Z

I'm hoping to take a look at this in the near future... been very busy with work.

matthewhadley · 2023-01-15T01:08:33Z

I am experiencing this issue (Flume current value was 5x what the Flume app showed) and found that overriding the change made in https://github.com/home-assistant/core/pull/81968/files resolves it.

To revert the change I created a custom component following these steps:

Copy the current Flume component code into custom_components/flume per https://skylar.tech/overriding-default-home-assistant-components/
add a version number (1.0.0 was fine) per https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes/#versions
change homeassistant/components/flume/const.py to DEVICE_SCAN_INTERVAL = timedelta(minutes=1)

zSprawl · 2023-01-15T18:17:46Z

It would be nice if the dev reverted the change from before Thanksgiving until they have time to work on this.

bdraco · 2023-01-15T18:24:00Z

If was that simple I would have already reverted it. Unfortunately reverting the change will trigger the rate limit so we would need to revert quite a few changes.

bdraco · 2023-01-15T18:30:50Z

I think the easiest fix would be to remove the binary sensor platform and change the interval back to 1 minute.

bdraco · 2023-01-15T18:32:37Z

This would probably work as well but it makes the leak notifications pretty useless

# Flume API limits individual endpoints to 120 queries per hour
NOTIFICATION_SCAN_INTERVAL = timedelta(minutes=60)
DEVICE_SCAN_INTERVAL = timedelta(minutes=1)
DEVICE_CONNECTION_SCAN_INTERVAL = timedelta(minutes=60)

bdraco · 2023-01-15T18:35:50Z

There aren't really any good solutions here since the flume rate limit is so low https://flumetech.readme.io/docs/rate-limiting

They really need a local api, a web socket api, or an increase in rate limit. Its not so great to have to poll for something time critical as a leak notifications.

With flume's current api design there are just a lot of bad options to fix this. Whatever change gets made is going to make one of the sensors worse.

kdill00 · 2023-01-16T16:55:07Z

I think the current one should take up 60 of those updates and reduce calls to the others? Because in the current way if im mistaken, I still have to use the flume app to clear a leak notification? Their is no need to have the other sensors update but once every so often. Maybe make it customizeable? Have all sensors disabled and allow people to choose in some manner? Prior to the update all my leak notifications were based off of the current use. If i am wrong that there is a way to reset the leak notification without opening the flume app let me know, but homeassistant to me is what i use to ditch a 1000 apps.

matthewhadley · 2023-01-17T16:52:16Z

If it's possible, it might be good to allow the user to set how to spend their "api budget". My preference is to have the usage levels updated frequently, with sensor.flume_current updating as frequently as possible. I do not use the native flume notifications as I replicate these directly in homeassistant automations using the current flow rate data.

bdraco · 2023-01-17T19:56:53Z

# Flume API limits individual endpoints to 120 queries per hour
NOTIFICATION_SCAN_INTERVAL = timedelta(minutes=5)
DEVICE_SCAN_INTERVAL = timedelta(minutes=1)
DEVICE_CONNECTION_SCAN_INTERVAL = timedelta(minutes=60)

I'd probably pick something like this. It seems to work well for me and avoid the rate limit

To stay under the API limit the device connection is now only checked hourly and notifications are only checked every 5 minutes fixes home-assistant#82336

To stay under the API limit the device connection is now only checked hourly and notifications are only checked every 5 minutes fixes #82336

zSprawl · 2023-01-23T05:38:02Z

@bdraco - Thank you!

home-assistant bot added the integration: flume label Nov 18, 2022

home-assistant bot assigned bdraco Nov 18, 2022

bdraco added a commit to bdraco/home-assistant that referenced this issue Jan 21, 2023

Restore flume scan interval to match app

acebfba

To stay under the API limit the device connection is now only checked hourly and notifications are only checked every 5 minutes fixes home-assistant#82336

bdraco mentioned this issue Jan 21, 2023

Restore flume scan interval to match app #86354

Merged

19 tasks

thecode closed this as completed in #86354 Jan 21, 2023

thecode pushed a commit that referenced this issue Jan 21, 2023

Restore flume scan interval to match app (#86354)

a49461a

To stay under the API limit the device connection is now only checked hourly and notifications are only checked every 5 minutes fixes #82336

matthewhadley mentioned this issue Feb 20, 2023

Latest fix to IAquakink (2023.2.4) has not resolved issue #88033

Closed

github-actions bot locked and limited conversation to collaborators Feb 22, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Flume Values are Too Large after 2022.11.3 Core Update #82336

Flume Values are Too Large after 2022.11.3 Core Update #82336

zSprawl commented Nov 18, 2022

home-assistant bot commented Nov 18, 2022

jeeftor commented Nov 18, 2022

zSprawl commented Nov 19, 2022 •

edited

Loading

jordahlm commented Nov 21, 2022

mermelmadness commented Nov 22, 2022

tcallaw commented Dec 13, 2022

rmcginty commented Dec 18, 2022

jeeftor commented Dec 20, 2022

matthewhadley commented Jan 15, 2023

zSprawl commented Jan 15, 2023

bdraco commented Jan 15, 2023

bdraco commented Jan 15, 2023

bdraco commented Jan 15, 2023

bdraco commented Jan 15, 2023 •

edited

Loading

kdill00 commented Jan 16, 2023

matthewhadley commented Jan 17, 2023

bdraco commented Jan 17, 2023

zSprawl commented Jan 23, 2023

Flume Values are Too Large after 2022.11.3 Core Update #82336

Flume Values are Too Large after 2022.11.3 Core Update #82336

Comments

zSprawl commented Nov 18, 2022

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

home-assistant bot commented Nov 18, 2022

jeeftor commented Nov 18, 2022

zSprawl commented Nov 19, 2022 • edited Loading

jordahlm commented Nov 21, 2022

mermelmadness commented Nov 22, 2022

tcallaw commented Dec 13, 2022

rmcginty commented Dec 18, 2022

jeeftor commented Dec 20, 2022

matthewhadley commented Jan 15, 2023

zSprawl commented Jan 15, 2023

bdraco commented Jan 15, 2023

bdraco commented Jan 15, 2023

bdraco commented Jan 15, 2023

bdraco commented Jan 15, 2023 • edited Loading

kdill00 commented Jan 16, 2023

matthewhadley commented Jan 17, 2023

bdraco commented Jan 17, 2023

zSprawl commented Jan 23, 2023

zSprawl commented Nov 19, 2022 •

edited

Loading

bdraco commented Jan 15, 2023 •

edited

Loading