I haven’t fully tested this but I think this should work for you.
You can create a helper using the “Utility Meter” integration. It creates a helper, and you can set it to:
Name: Liters Since Reset (or Gals Since Reset)
Input Sensor: Volume Today
Meter reset cycle: No cycle
Meter reset offset: 0
Net consumption: false
Delta values: false
Periodically resetting: true
Sensor always available: whatever you want (true or false)
Then when you want to reset the helper count, use an automation with an action of:
Add action → Helpers → Utility Meter → Reset
And then choose entity: sensor.liters_since_reset
You can name the automation “Reset Filter Count” and manually run the action.
You can also add an automation “Replace Filter Notification” that triggers on a certain number of Liters (or Gals) accumulated on sensor.liters_since_reset, and set an action to send you a notification to “Replace the Filter”. And then manually reset filter count when you replaced the filter.
Or, you can combine both: set a trigger based on the number of liters (or gallons) you want. When it triggers, it will can do action1 and reset the value to 0 and then do action2 and send you a notification. This assumes you can replace the filter right away.
Edit: Just occurred to me that you may not be able to use an exact value as the increments to liters_since_reset is not guaranteed to be increments of 1, it may jump over your selected value without triggering. You will likely have to use an Above value selection - which may cause multiple notifications. You’ll have to play with this a bit so you don’t create a nuisance set of notifications.
This is the reason why I added this to the energy monitoring section. Homeassistant does all the hard work, once tag the “Volume Today” entity with the class: water attribute, and configure the Water Consumption section of the Energy Configuration
Hi forum,
I know this is a bit off topic however I am after some advice about the Frizzlife water monitor and valve which I purchased for repeated scheme water leaks often for several days at our acreage in Australia from irrigation failures as we are only there on weekends.
I need to connect this to Australian standard 240v DC power rather than the US 110v. I see it comes with a USB connection to a wall plug/transformer. Most USB plugs run at 5v so I am hoping it simply means attaching this to an Australian standard USB plug transformer such as from an old phone or tablet? Hopefully it is that simple or am I missing something?
Many thanks. I will try to hook it up over the Christmas break. This should be more widely publicized as the Flo seems to have the local market as it comes with a local plug
Just noticed that the latest version (2025.12.3) of Tuya_Local provided a file named: frizzlife_lp365p_watermonitorandshutdoff.yaml.
A couple of notes:
It provides a device id of 89tojzdfimssmkuk which appears to some sort of generic 15 char device ID rather than a 22 char virtual ID.
I tried using it but it wouldn’t find my lp365p - I’ll try some variations on configuration to see if I can get it to work.
It does not provide a dps id of 15 - which is for the pressure sensor.
It does have some interesting configurations which looks like a potential fix to get rid of my ugly select lists of time and volume flows for Mode 4,5 and 6.
Unfortunately, I don’t have any answers on how to use it yet. Hopefully I’ll have some time in the next little while to see if I can integrate it - or integrate to it. I’d love to have a working version of this included in Tuya Local.
In case anybody lost their fixed frizzlife_lp365p_watermonitorandshutoff.yaml file with a Tuya Local update, here’s mine. Sensors work, but I haven’t done any tweaks to the various modes.
I haven’t been able to spend any time on this lately as I’ve been busy with other commitments.
I hope to have some time in the next month.
It’s a bit of a pain to keep having to copy my personal copy back to the devices folder after an update, but at least it’s only a copy and no edits are required.
I got Tuya Local to pick up my Frizzlife LP365-P with the built-in definition. First, I updated the firmware on the device. Then in integration creation I set the API version to 3.5, otherwise it gives you bad matches. All looks good.
i haven’t installed my unit yet, but I made a merged file to support both LP365 and LP365-P with detection for metric vs imperial units. Can I get some people to test this? If it looks good, I’ll submit it to tuya-local.
I’ll see if I can find time to integrate into my version and test. Thanks everyone, glad to see folks with more knowledge than me getting involved.
NOTE:
Frizzlife has removed the temperature sensor in the latest shipments of the LP365-P. I have a neighbour that purchased the LP365-P and we were trying to figure out why his app doesn’t show the temp - I confirmed with Frizzlife support that they intentionally removed the sensor.
I can certainly test out your YAML. I just updated my tuya_local and forgot to save a copy of my earlier yaml. Do I need to add the device all over again ? Or is there anyway to update existing device with correct YAML ?
Nevermind, I was able to find the custom yaml name in the logs and had a backup somewhere else. Once I added the file it works again.
Now when I used your file, Temperature was showing unavailable and my values were showing abnormally high, first 3 highlighted rows are with your yaml and rest of them are with @ wundrellama yaml
Here is a fixed Yaml that makes the temperature optional as well (my LP365-P has one) and fixes the scale for the US units which I had an extra zero on.
Hi Roy, finally got around to testing your YAML. Everything looks good for me except water temperature. its showing up as -7.5C when it should be about 18.5C. I’m guessing the cause is using DPS 102 as the selector for temperature. Since my device is configured for us-units for volume, but metric units for water temperature, it might be using a different DPS for water temp units?
Other than that, everything seems to be working very well. thanks for the update - looking forward to this being merged.
