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!
@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)?
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.
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.
Ah I have a theory. My refresh rate is the default @ 2 mins, but I have two Flume units at two homes under one account. That would explain it, no?
Yep, I'd bet you will run into that issue about halfway through each hour. Is that what you're seeing?
Try pinging Flume support to see if they would increase your limit given your use case (and that you're a repeat customer of theirs). Maybe they will throw you a bone. 
For anyone curious, these are the 4 requests and their purposes in each refresh by my integration:
/devices/{id}/query - for usage data (minute, hour, day, week, month)/users/{userid}/usage-alerts - for usage alerts, primarily smart leak/users/{userid}/notifications - for notifications, like high flow, long duration/users/{userid}/locations - for location information, primarily home/away status.
Yep sure am. I didn't notice that pattern until you mentioned it. Thanks.
Just sent a note to Flume customer support asking for double the API "allowance" since I'm double the customer. 
We'll see.
Interesting and disappointing interaction with Flume today. They basically said the their API volume limit is set per-customer. As a result, if I purchase two or three Flumes, I only get a half or a third of the API value. Which doesn't seem to make good business sense as it disproportionately punishes repeat customers.
I spoke to a support manager this afternoon and asked them to reconsider. They said they'd get back to me. Fingers crossed.
That's a bummer.
Their limit is really low. It's barely usable as it is.
If their cost structure is based on keeping that limit so low I could understand it on a per-unit basis. But per-customer is punitive like you said for anyone that wants to use it with multiple purchases.
I searched far and wide for this about a year ago and could not find anything that would work.
They will warranty that at 9 months.
Well, the saga continues. Here's the response from Flume's engineering lead. It's a workaround that should be fine for now, but a bit silly for a startup that is still supposed to be in an agile stage of growth. Oh well.
@tomw, I don't see any reason that your Hubitat integration would be rendered unusable by this workaround, do you?
Yes, currently if you set up an additional device with a different account you will have a separate API allocation. You could even set up an account using something like mluck+1@alum.mit.edu and the emails will still go to mluck@alum.mit.edu - but this of course would make a 3rd party integration like Hubitat potentially unusable.
Unfortunately, the system we use isn't designed to make account level exceptions for the API limits, but I understand your point and have recorded this as a feature request!
At some level, every software person is just hacking away at things I guess. 
I think it would work, as long as the account email and client ID/secret from Flume and the login details you use for my integration are a match, regardless of where the emails ultimately end up.
Quick update for anyone else with multiple Flumes.
The workaround is to setup two different accounts with Flume, with one device in each. I found it easiest to add “+1” to the left of the @ in my email address, that way I could still use a single email address while having Flume treat it as two different accounts. Of course each account has its own client ID and secret, each of which you can use to create separate devices using @tomw’s most awesome driver.
Then, even better, if you tell Flume you have two different accounts, they can configure it so that it still shows up as a single virtual account if accessing Flumes through their app. That was a nice bonus I wasn’t expecting.
That’s it. If anyone needs help with 2 or more Flumes, feel free to reach out. I have it working perfectly for the moment.
That's a nice bonus...kudos to them for having some level of flexibility on this!
And thanks for working this all out for the rest of us.
I knew I liked this guy...Not only did he bring us this very cool Flume integration, he's a Rush fan! Awesome! 
How do you get metrics into influxDB? is it via influx logger app? Thank you
yes, for all other devices the influx logger works great but no for Flume device.
Download the Hubitat app
