I've got a water leak sensor (T300) attached to hub (H100) working well in HA, but it doesn't update when the alarm volume is muted. Looking at the waterleak sensor PR #876 I'm guessing it's something to do with using sensor_alarm for detection so requires in_alarm to be true.
Diagnostics from the sensor hub when sensor is wet but alarm is muted. The water_leak_status changes as expected but the Moisture sensor shows Dry.
"in_alarm": false,
"water_leak_status": "water_leak",
Use case if I'm away from the house and there's a leak, I would like to have automations available but not leave the alarm blasting. HA core and device firmware all with latest updates.
There hasn't been any activity on this issue recently. This issue has been automatically marked as stale because of that. It will be closed if no further activity occurs.
Please make sure to update to the latest python-kasa version and check if that solves the issue.
Thank you for your contributions.
Hi, when I did that PR, my understanding was that the in_alarm would also happen even if the volume would be muted, and I thought I verified it, too.
Sorry to hear that it's not working as expected. You could try to query (using the cli tool) and/or capture a fixture–as described in the docs–when the device is alarming when it's muted, just to see if there is some other information we could use to make it work.
Alas, in the case where the device is not reporting the leak state while muted, there is nothing this library can reasonably do. Maybe just document the behaviour in the docs, or completely disallow setting it to the mute?
Activity
github-actions commented on Jun 26, 2025
There hasn't been any activity on this issue recently. This issue has been automatically marked as stale because of that. It will be closed if no further activity occurs.
Please make sure to update to the latest python-kasa version and check if that solves the issue.
Thank you for your contributions.
rytilahti commented on Jul 4, 2025
Hi, when I did that PR, my understanding was that the in_alarm would also happen even if the volume would be muted, and I thought I verified it, too.
Sorry to hear that it's not working as expected. You could try to query (using the cli tool) and/or capture a fixture–as described in the docs–when the device is alarming when it's muted, just to see if there is some other information we could use to make it work.
Alas, in the case where the device is not reporting the leak state while muted, there is nothing this library can reasonably do. Maybe just document the behaviour in the docs, or completely disallow setting it to the mute?