This looks great! I had the previous version of Flume (they have a new version out now) and got rid of it because I wasn’t able to integrate it with ST. I just happened to bump into this thread and I’m glad I did. Just so I understand this, would there be a way for WebCoRE to shut off a water valve (already have that installed and connected to ST) in case it detects a heavy flow leak (or maybe even a slow leak?) Will your implementation work with their newest Flume version? Thanks
I’ll know for sure if the newer device works with this current implementation once I get my hands on one, it’s on its way courtesy of Flume :), if not ill work on an updated DH/implementation.
@smartie Currently the implementation is setup to auto retrieve data every 6 minutes. This can be adjusted down to 1 minute
Line 124 of updated oneApp DH
schedule(“0 0/6 * * * ?”, poll) //refresh every 10 minutes change to 6
The refresh interval is limited due to Flume API’s rate limit. If you exceed rate limit you’ll be locked out and get request data/refresh denied response. im not sure what is the locked out time (guessing a couple of minutes) so six minutes is the safe/stable path.
Thanks for updating this. I tried to install just the Smartapp and the new DH but that did not create a device. I had to also create the old DH in order for it to create a device and then update it to the new DH. Was that intended or did I miss a step somewhere?
Thanks for catching that and providing a workaround. There’s a line on the Flume smartapp that calls the device dth but currently calls old dth name.
For current device already installed updating to newer device type as mentioned earlier post is the way to go.
For new/fresh installs Ill need to update the smartapp to match the name of the new/updated device dth. Im working on a newer smartapp version with other features plus will include call to newer device dth, will release a week or two.
@JosephNY
Try new version, if you still get this issue please let me know, I’ll take a look.
@frazered
I updated the SM and the Device handler here:
This new SM version handles multiple flume devices and with the newer DH should find your Flume devices once you enter your Login in the Options section of the SM.
I have been crazy busy with work but planned is add the option to view device Bridge Wifi Connection and Sensor Battery Level (Flume uses low, medium, high) but I’m partially there with the OneApp frontend presentations. This version is easier to setup Flume device(s) as mentioned earlier.
@smarties
The best thing about Flume v2 battery replacement it’s super easy now, there’s a YT video that talks about other differences, not mine, maybe I need a YT channel LOL.
Using the new DH and SApp, I tried creating an Alert but the “Water Sensor” still shows “Dry”. I received the alerts in Flume app but the ST Device “-Flume Meter” kept showing “Dry”.
Logs for the smartapp show that it received the alert
request_id:SYSTEM_TRIGGERED_USAGE_ALERT, since_datetime:2021-01-04 12:17:00
can you take a screenshot of your Flume ios/Android App Notification (within Flume click the Bell icon on top right and it should have all Notifications) of the triggered alert you received.
This SM handles Low Leak Alerts.
With the screenshot I can confirm if this is a Low Leak or a custom Usage alert (which I think it is)
If it’s a custom usage alert then I will need to add additional code logic to handle custom usage alerts.
if screenshot shows Low Leak then I can take a look what’s going on with current implementation since this definitely should have turned to Wet.
Oh ok, yes it is a custom usage alert I created to test the Flume 2 (just got it yesterday).
Will await the custom alert addition if and when you add it to the DH.
Sorry, maybe I’m doing something wrong, but I can’t figure it out. After changing the code for the DH andSmartApp in IDE, Once I enter my email/pw and click done, I see “processing” and get taken back to the list of all my smartapps. When I click on the “Flume Home” again, I am taken back to the same screen with credentials.
