Hopefully @tomw will have some sage input on this. My input is generally parsley. 
2 Likes
There's a limit of 120 API accesses per hour from Flume, which is a relatively low limit.
When you first set up the integration, it will make approximately 6 API accesses. Each refresh makes another 4 API accesses.
So, if you manually your Refresh a few times or have a 1 minute refresh interval, you'll get ahead of your 120 per hour pace pretty quickly and run out before your hour is up.
What do you have your refresh rate set to on the Hubitat virtual device page? I'd encourage you to dial that down to every 2 minutes (or longer) and then wait about an hour to see if it begins working again.
2 Likes
ok, this make sense. I had the refresh interval set for 1 minute - changed it now to 2 minutes and the connection now show as good. Thanks for that!
Now I set the data to be stored in InfluxDB to present it in Grapana but no values of any of the virtual device activities are coming up there 
Do you mean no attributes are showing up for this device or no attributes are showing up for any devices?
Most of the attributes for the Flume device are custom attributes. Do you have to do anything to make those show up in your InfluxDB setup? I have never used that before.
that may explain the issue - none of the attributes are showing in Grafana so far, I'll check what is being recorded in the DB itself.
after checking the InfluxDB logs, it does seems like no values are being send to the database other than the Presence (?) and Dry/wet variable - All are info messages:
handleEvent(): House Water Monitor(water:null) dry
handleEvent(): House Water Monitor(presence:null) present
softPoll(): Softpolling device House Water Monitor for attribute: water
Any way to make the attributes binary so they will be exported and stored in the DB?
It was great if it would have been possible to export the flowStatus and usageLastMinute & hour to build my own water charts in the Grafana dashboard.
An example of another device which is reporting its data to influxDB (Thermostat in this case):
handleEvent(): Hallway Thermostat(heatingSetpoint:null) 68
softPoll(): Softpolling device Hallway Thermostat for attribute: heatingSetpoint
handleEvent(): Hallway Thermostat(temperature:°F) 70.4
softPoll(): Softpolling device Hallway Thermostat for attribute: temperature
There really aren't built in attributes to support everything I did as custom ones. Is there a way to log custom attributes in InfluxDB? I'd be surprised if that wasn't an option somehow.
He already replied but I can’t help myself.
Just give it thyme.
3 Likes
Any way to optimize the API calls per refresh to one?
There's not really a way to optimize it further without losing info from attributes supported by the integration.
The best I could see was maybe to remove 1 API access (out of 4) from each refresh, which would require removing the home/away status info. Some people might use this for automation or even presence indication, though, so I'm reluctant to do that.
What are you trying to do that requires further optimization? Keep in mind that the Flume sensor data itself isn't particularly responsive even though it is very accurate once updated, so spinning on Refresh at a high rate doesn't really give any more responsive data.
2 Likes
I was thinking that each poll to the API gives a number, and the quicker I can poll that number the more accuracy I'll gain in my hubitat logging over time. But if the resolution is only so-much as provided by the flume API, maybe it doesn't matter then?
The measurement is very accurate, but it doesn't update very often no matter how fast you poll using the API. So, I don't personally see much benefit from refreshing more than a few times per minute.
3 Likes
Got it, thanks for that!
Another question on tiles. I used attribute tiles to show me the last min, hour, and day of water usage. However, it's a bit of a waste of space honestly. On the Neurio driver they were able to use an "html" attribute to let us make a custom tile (although I haven't figured it out yet, but others have). Is there something like that possible in a future update of this?
I would recommend looking at one of my other drivers like the children from the Unifi Network or Blink (I think) to copy over the Tile Template method. It is a replacement/update I made to the original mircolino method (who is not on Hubitat anymore).
@tomw and I seem to have way too many cross over points. 
2 Likes
I haven't personally used it, but I think this is the purpose of @bptworld's popular Tile Master integration: [RELEASE] Tile Master - Display multiple devices that can be Controlled from the tile!
I'd give that a try to see if it meets your needs. If it doesn't work out let me know and we'll come up with something else!
1 Like
@tomw
Hey Tom.....noticed the last couple days your awesome flume driver is generated some errors in the log. I'm not noticing any particular problems manifesting, but maybe I'm just not noticing yet.
error: status code: 429 reason phrase: too many requests @ line: 950 (and also @ line: 133)
That's the rate limiting error from Flume's cloud. They limit the number of requests per hour to 120, and each refresh from my driver executes 4 requests. What do you have as your scheduled refresh rate? Do those errors go away after an hour (and then possibly return later in the 'next' hour)?
1 Like
The flume mobile app just notified me it’s time to replace the battery pack in my Flume 2. That means mine lasted about nine months, and now I get to pay them for the privilege of using another one of their proprietary packs.
What have others’ experiences been like with the Flume 2 battery?
The battery life is bad. I had an experience similar to yours, if not shorter.
Open it up and see if you have a shrink-wrapped pack or a fully encased one. You can replenish the shrink-wrapped one with normal AAs.
1 Like
If you have the shrink-wrap version and a outlet close enough, a mains-powered battery conversion kit works really well -- mine's still going since original install over a year ago.
I gotta think there's a version of that shrink-wrap model's basic 4-battery "cage" on AliExpress or something like that -- it just seems to be a super vanilla / standard looking battery component thingamajig.
2 Likes
