Post Requests for LAN/WIFI Edge Drivers Here (community-created)

[netcsk]

I’d like to request the Flume Flow Meter, which is a LAN device that straps on the street flow meter to collect whole home flow data.

There are two versions as smart apps / DH:

[OBSOLETE] Flume Water Meter Smartthings Smartapp + Flume Water Meter Device Handler

https://www.amazon.com/Flume-Smart-Home-Water-Sensor/dp/B07GPXKN8Z/ref=sr_1_1?keywords=flume+water+meter&qid=1568400732&s=gateway&sr=8-1 It doesn’t have the home/away that stream labs water meter has so the interface looks slightly different. It will turn to ‘wet’ if a Low Flow Leak is detected by Flume Water Meter. Also you will need to adjust for your time zone line 337. Since it’s a frankenstein app it might have redundant methods…feel free to clean up methods or debug statements as you see fit. Acknowledgements: My first Smartthings app and groovy stab, want to thank @windsurfer99 for his implementation: [RELEASE] StreamLabs Smart Home Water Meter Interface also thank @joshs85 [OBSOLETE] Honeywell Lyric Water Leak Sensor Connect also thank michaeldavie Flume Water Meter - #42…

[OBSOLETE] SmarThings Smart App and Device Handler for Flume Smart Home Water Monitor

Code is available at: GitHub - tronikos/FlumeSmartThings: SmarThings Smart App and Device Handler for Flume Smart Home Water Monitor Direct links to code: SmartApp code Device Handler code Local proxy code Features Leak sensor Changes to wet on low flow leaks Changes to wet on any usage alert (configurable) Changes to dry when notification is deleted in the flume app or when it’s read (configurable) Wet/dry status can be permanently or temporarily paused (with configurable time lime) Water usage for the last full minute, today, this month, this year is shown in the device page as well as the dashboard water usage stats, connection status, battery level, away mode are exposed as attributes for webCoRE automations When SmartThings changes to away, Flume can be put in away mode th…

I use the second version as it avoids rate limiting shared by all users by calling to the API from local rather than ST servers.
A strong want would be to expose flow rate directly to automations versus just a display value / webcore value.

I also realize this would be difficult as it requires calling to a remote API and thus likely an intermediate step like what @TAustin has done for other LAN devices with his bridge server. Thanks for any consideration!