[Device]: PLWF116 | Dockstream Smart Fountain 2

[trentsmart]

Device model name

Dockstream 2 Smart Fountain (Cordless)

Device model number

PLWF116

Device type

Fountain

What state, statistic or control do you want to be reported in the integration ?

Current water level with ability to set the reminder level
Battery level left if in cordless mode.
Filter time remaining
Time until cleaning needed
Drink logs with amount consumed
How many daily visits
Average duration
Goal
measurement unit
Access to indicator lights
Firmware Version and if update is available
Water flow type and ability to select which type
This fountain has the feature to select the flow type as pet sensing and there are two options with sensing, Near the device and far trigger. It would be nice to be able to set this as well. Also, the ability to maybe expose the sensor as a motion sensor for other automations.

I know I included a lot, but I figured I would try to capture as much as I could. Once again, thank you for this project.

Available to help integrate the new device

• I agree to help with the integration of the new device by providing the necessary information that will be requested

[C4-Dimitri]

@trentsmart, could you try to log into the integration and turn debug logging on for 10-15 mins and give us the logs? Mainly so we can see what name this comes up as from the API.

Most of what you have requested should be super easy as it's already implemented for the Dockstream Smart Fountain (PLWF105) and Dockstream Smart RFID Fountain (PLWF305)

At the same time we should probably try and do it for the new PLWF106 too, but we will need someone who has one to provide us the the name in the API (or we can try to infer the name from yours and the rest).

[trentsmart]

@C4-Dimitri yep I can do that. Will get back with you guys in a few.

[trentsmart]

home-assistant_petlibro_2025-08-16T16-30-56.939Z.log Here you go. @C4-Dimitri

[trentsmart]

2025-08-16 11:10:31.269 DEBUG (MainThread) [custom_components.petlibro.hub] Fetched 3 devices from the API.
2025-08-16 11:10:31.269 DEBUG (MainThread) [custom_components.petlibro.hub] Processing device: Dockstream 2 Smart Cordless Fountain (Serial: WF040131000520786102O5)
2025-08-16 11:10:31.269 ERROR (MainThread) [custom_components.petlibro.hub] Unsupported device found: Dockstream 2 Smart Cordless Fountain (Serial: WF040131000520786102O5)

[C4-Dimitri]

Perfect, like I said, should be pretty simple.

Few things will be custom of what you requested.

The sensor water flow selection
Whether plugged in or not

A few things we won't do as they are captured elsewhere like measurement unit.

Let's just initially try and extend what we already have to your Fountain type, and then we can take a look at what else you want.

If you could share access to my test account I can start implementing a lot of these things:
dimitri.landerloos@hotmail.com

[C4-Dimitri]

Adding API information for the Dockstream 2 Smart Fountain Cordless PLWF116, only things that seem to be specific to this device:

post request:
https://api.us.petlibro.com/data/data/realInfo

{
  "id": "WF040131000520786102O5"
}

response:

{
  "code": 0,
  "msg": null,
  "data": {
    "deviceSn": "WF040131000520786102O5",
    "mac": "E0:08:BF:00:10:3E",
    "timezone": "America/Chicago",
    "hardwareVersion": "1.0.0",
    "softwareVersion": "0.3.23",
    "online": true,
    "lastOnlineTime": 1755372027526,
    "onlineList": [
      {
        "online": true,
        "ts": 1755213094071
      }
    ],
    "wifiSsid": "itslit",
    "wifiRssi": -65,
    "wifiRssiLevel": 3,
    "powerMode": 1,
    "powerType": 2,
    "electricQuantity": 100,
    "surplusGrain": true,
    "vacuumState": true,
    "volume": 50,
    "enableLight": true,
    "lightSwitch": true,
    "lightAgingType": 1,
    "enableSound": true,
    "soundSwitch": true,
    "soundAgingType": 1,
    "useWaterType": 2,
    "useWaterInterval": 15,
    "useWaterDuration": 15,
    "sensingWaterDuration": 45,
    "filterReplacementFrequency": 14,
    "filterStartWorkingTime": 1755147600000,
    "filterNextReplacementTime": 1756357200000,
    "remainingReplacementDays": 12,
    "machineCleaningFrequency": 14,
    "machineCleaningTime": 1755147600000,
    "machineNextCleaningTime": 1756357200000,
    "remainingCleaningDays": 12,
    "weightPercent": 92,
    "weightState": "NORMAL",
    "weight": 2773.0,
    "waterBoxStatus": 1,
    "batteryState": "high",
    "todayTotalMl": 121,
    "calibration": true,
    "vacuumMode": "NORMAL",
    "pumpAirState": true,
    "snowflake": true,
    "barnDoorError": false,
    "errorState": false,
    "runningState": "IDLE",
    "doorErrorState": "NORMAL",
    "whetherInSleepMode": false,
    "lowWater": 650,
    "filterLedSwitch": true,
    "detThreshold": 0.4,
    "reidThreshold": 0.75,
    "cameraAuthInfo": "0B80Z80880480280L80EIup0",
    "filterState": "GOOD",
    "leftWarehouseSurplusGrain": true,
    "rightWarehouseSurplusGrain": true,
    "warehouseSurplusGrain": "GOOD",
    "garbageWarehouseState": "NORMAL",
    "garbageWarehouseLeaveState": "NORMAL",
    "throwMode": "NORMAL",
    "radarSensingLevel": "NearTrigger",
    "radarGain": 5,
    "radarSensingThreshold": 45,
    "waterStopSwitch": false,
    "powerState": "USING",
    "talkChannelState": false
  }
}

note powerMode, powerType, electricQuantity, and powerState

post request:
https://api.us.petlibro.com/data/deviceDrinkWater/history

{
  "deviceSn": "WF040131000520786102O5",
  "dimension": "day",
  "dimensionParam": "2025-08-16"
}

response:

{
  "code": 0,
  "msg": null,
  "data": {
    "legendData": [
      "Water Intake"
    ],
    "waterIntake": [
      5,
      12,
      0,
      0,
      75,
      0,
      12,
      5,
      4,
      4,
      0,
      4,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0
    ],
    "drinkTimes": [
      1,
      2,
      0,
      0,
      2,
      0,
      2,
      1,
      1,
      1,
      0,
      1,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0
    ],
    "avgDrinkDuration": [
      7,
      10,
      0,
      0,
      44,
      0,
      10,
      14,
      4,
      11,
      0,
      5,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0
    ],
    "totalMl": 121,
    "avgDrinkMl": null,
    "dailyAvgDrinkMl": 121,
    "xdate": [
      "00:00",
      "01:00",
      "02:00",
      "03:00",
      "04:00",
      "05:00",
      "06:00",
      "07:00",
      "08:00",
      "09:00",
      "10:00",
      "11:00",
      "12:00",
      "13:00",
      "14:00",
      "15:00",
      "16:00",
      "17:00",
      "18:00",
      "19:00",
      "20:00",
      "21:00",
      "22:00",
      "23:00"
    ]
  }
}

this is probably not individual to your fountain, but first time i have seen it as i was forced to update the app to view your device. i have been putting it off, as i was nervous it might break how i view the API data, but it didnt.

we can request day, week, month, or year , week requires specifying an endDay example:

{
  "deviceSn": "WF040131000520786102O5",
  "dimension": "week",
  "dimensionParam": "2025-08-10",
  "endDay": "2025-08-16"
}

not sure how useful all of this data will be however, as we should just build history in homeassistant itself.

post request:
https://api.us.petlibro.com/device/setting/updateRadarSetting

{
  "deviceSn": "WF040131000520786102O5",
  "radarSensingLevel": "FarTrigger"
}

response:

{
  "code": 0,
  "msg": null,
  "data": null
}

this is for a "far" request. so far = "FarTrigger", near = "NearTrigger". same response and request layout otherwise. easy to implement via a select entity.

post request:
https://api.us.petlibro.com/device/device/waterModeSetting

{
  "deviceSn": "WF040131000520786102O5",
  "requestId": "39afda1dcabd4f988a8e08c28399d3cc",
  "useWaterType": 0,
  "useWaterInterval": 15,
  "useWaterDuration": 15,
  "sensingWaterDuration": 45
}

response:

{
  "code": 0,
  "msg": null,
  "data": null
}

0 = continuous water, 1 = intermittent water (not supported for your fountain, is supported for PLWF305 and PLWF105), 2 = water on sensing.
you also have a new "sensingWaterDuration" attribute which the other fountains dont have. you dont appear to have control over this from the App? we could probably control it from homeassistant, as we we have useWaterInterval, useWaterDuration, built for the intermittent water that the PLWF305 and PLWF105 support.
one cool thing is that you cant select continuous water from the App when its in battery operated mode it looks like? well you can if you send the API request directly! so we could allow you to choose that option from HA.

my thinking is that we make you a select with 3 options. 1 continous water, 2 sensing near, 3 sensing far.
then a number entity for the sensing water duration attribute. let me know if you would be good with this.

post request:
https://api.us.petlibro.com/device/device/waterModeSetting

{
  "deviceSn": "WF040131000520786102O5",
  "waterStopSwitch": false
}

response:

{
  "code": 0,
  "msg": null,
  "data": null
}

this is also new for your fountain type, so we would need to create a switch or buttons for toggling the water dispensing overall, or we could have an option in the select for just "off". again your call what you think is best.

post request:
https://api.us.petlibro.com/device/setting/updateLightingSetting

{
  "deviceSn": "WF040131000520786102O5",
  "lightSwitch": true,
  "lightAgingType": 1,
  "lightingStartTime": null,
  "lightingEndTime": null,
  "filterLedSwitch": false
}

response:

{
  "code": 0,
  "msg": null,
  "data": null
}

similar to a lot of devices you have control over the indicators, but you also have control over specifically the filter indicator on its own as well. this seems to have also been extended to my fountain (PLWF305), so we could look to try and implement this, but it migth get confusing between the main indicator control turning off all indicators, vs just the 1 indicator being off.

post request:
https://api.us.petlibro.com/device/setting/updateLowWaterSetting

{
  "deviceSn": "WF040131000520786102O5",
  "lowWater": 1394
}

response:

{
  "code": 0,
  "msg": null,
  "data": null
}

individual to your fountain, you can set the level at which it notifies you to refill, we can handle this with a number entity pretty easily. minimum is 650, max is 3000. i tested as a joke whether you can set it higher than 3000... and you can:

but we will limit the number entity to the range desired :)

and that should be about it!

i can get to work implementing the majority of these things. i am waiting for a few pull requests of mine to be completed, some of which contain some features you have already requested. so if it is ok with you, i am going to develop these things on my own fork, and not open a pull request until my open ones have been merged.

ill then shoot you a message here once the branch on my fork is in good condition for you to test with and give feedback.

[trentsmart]

Sounds great. I would be good with in the water dispensing overall, just having another selection for off. We dont need to make a switch or button for that. The filter indicator, if you're ok with that I would like to be able to control that one individually and also have the all indicators selection as well. Also, on level notification I had it in ounces and I think the lowest it let you go was like 21 and the highest was around 101, so that would be fine or if you do it in ml the 650 to 3000 range would work also. Thats awesome you can do continuous from the API on battery, Im actually stoked about that lol. Everything else I will leave up to you bro. If theres ever anything that we might want to change we can always revisit it later. I guess it isnt possible to see when the radar detects movement? lol I was jus thinking that could have been pretty neat to use that as a motion sensor. Thanks again. @C4-Dimitri

[C4-Dimitri]

@trentsmart, its going well so far, ive got the selector working for the water dispensing mode and quite a few sensors.
to implement a sensor that shows if its plugged in/is charging or using battery, please can you ping me when you happen to plug it in please? i can then see what powerMode, powerType, and powerState are updated to, as i bet that these are what control most of it.

screenshots of what i have so far:

[trentsmart]

@C4-Dimitri hey just letting you know I plugged her in. That looks awesome by the way bro, I'm ready to test it lol.

[C4-Dimitri]

@trentsmart , just having a look now:

    "powerMode": 1,
    "powerType": 3,
    "powerState": "CHARGING",

so looks like powerType 3 is plugged in, powerState can be USING or CHARGING. probably no other state as it says CHARGING despite being at 100%.
we saw powerType 2 previously and this is when it was using the battery. so really powerType and PowerState is the same thing, so we can use either.

still not sure what powerMode is though, oh well :)

i will have it ready for you to test, probably by end of my day tomorrow, so in about 24 hours from now.

FYI will be implementing the drinking data info too from this endpoint:
https://api.us.petlibro.com/data/deviceDrinkWater/todayDrinkData
post request:

{
  "deviceSn": "WF040131000520786102O5"
}

response:

{
  "code": 0,
  "msg": null,
  "data": {
    "todayTotalMl": 60,
    "todayTotalTimes": 10,
    "drinkTimes": "01m56s",
    "yesterdayTotalMl": 138,
    "yesterdayTotalTimes": 15,
    "remainTotalMl": 3268,
    "tankTotalMl": 2500,
    "dailyDrinkGoals": 0.0,
    "petEatingTime": 116,
    "avgDrinkDuration": 11
  }
}

[trentsmart]

@C4-Dimitri so theres actually a power button on the bottom of the device, I just turned that off. Maybe that's if it has power at all. See if maybe power mode changed now. Maybe went to 0? Or would it not be able to report any data with it off? lol

[C4-Dimitri]

    "powerMode": 1,
    "powerType": 3,
    "powerState": "CHARGING",

still the same data. and dont see anything different in the app either?

[trentsmart]

@C4-Dimitri well crap Idk what that could be then, but it def. turned off. all indicator lights went dark. just pushed button back in and lights came back on.