question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue with 2018 SmartThings Water Leak Sensor (IM6001-WLP01) treated like 2015 version (F-WTR-UK-V2)

See original GitHub issue

I have found a weird circumstance when pairing my IM6001-WLP01 SmartThings water leak sensor. I have verified that the device’s firmware is fully up-to-date (version 0x11 / 17).

During pairing, it identifies itself as follows:

  • Manufacturer: Samjin
  • ModelID: water

When pairing is complete, Zigbee2MQTT treats it as a SmartThings F-WTR-UK-V2, which is a completely different device. When I short the sensors (to simulate a water leak event), zigbee2mqtt cannot interpret the resulting zigbee message, so the leak is not reported.

Interestingly, the F-WTR-UK-V2 is referred to as the “2018 model” by z2m, but it is actually a 2014 or 2015 model according to this SmartThings support article. I believe the device I have (the IM6001-WLP01) is the 2018 model. The zigbee2mqtt documentation website has the correct pictures for both the IM6001-WLP01 and the F-WTR-UK-V2.

I believe that one of two things has happened:

  1. There are multiple different devices with the modelId water. This would be bad!
  2. zigbee-herdsman-converter’s devices.js has an error in it.

I do not know what to do if 1 has happened, and I’m hoping that Samsung wouldn’t allow that kind of oversight. Thus, going forward, I will assume 2.

Here’s what I’ve been able to gather:

In order to make my device work, I would have to change the modelId of water for the existing devices.js entry for the F-WTR-UK-V2 (and replace the modelId of IM6001-WLP01 for the existing IM6001-WLP01 entry). I don’t know what the correct modelId for the F-WTR-UK-V2 is, and I certainly don’t want to break any existing device configurations.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:3
  • Comments:8 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
airdrummingfoolcommented, Dec 18, 2019

@achurak thanks for the information. I had the same issue with contact events on my sensor, and have fixed it in my local branch. I’ll be submitting a PR in the next couple days that includes the fix for both the contact sensor and the identification of the device.

0reactions
Koenkkcommented, Dec 23, 2019

Closing this as #833 has been merged, thank you very much @airdrummingfool for figuring this out.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Samsung SmartThings Water Leak sensor won't connect
On Samsung SmartThings home screen, tap Water Leak Sensor > tap More (3 ... Release the button when the LED light starts blinking...
Read more >
CentraLite Water Leak Sensor 3315-G Issues V2 Hub
In January, we began receiving reports that some Centralite devices on 2015 and 2018 SmartThings hubs were becoming unresponsive. This update ...
Read more >
How to reset Samsung SmartThings Water Leak Sensor
If the Samsung SmartThings Water Leak Sensor won't connect to your Hub or detect moisture, you'll want to reset the device.
Read more >
Samsung GP-U999SJVLCAA SmartThings Water Leak Sensor
The sensor monitors moisture and water leaks to prevent flooding, as well as sudden rises or drops in temperature. Easily install the sensor...
Read more >
The Best Smart Water-Leak Detector - The New York Times
Some devices may rely on a hub. Smart-home integration. You can link leak sensors with other devices for extra features such as voice ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found