Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help Pairing Samsung Leak Sensor #946

Closed
sktaylortrash opened this issue Nov 14, 2018 · 23 comments
Closed

Help Pairing Samsung Leak Sensor #946

sktaylortrash opened this issue Nov 14, 2018 · 23 comments

Comments

@sktaylortrash
Copy link

Apologies if this is not the place to ask. Has anyone successfully paired the new SmartThings leak sensor. I can't get anything to show up in deconz. It pairs instantly with a SmartThings hub of course, but despite repeated tries no joy with deCONZ.

@ebaauw
Copy link
Collaborator

ebaauw commented Nov 14, 2018

I don’t think that is yet supported by deCONZ. Please see
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Request-Device-Support

@sktaylortrash
Copy link
Author

Thanks, but unless I'm misunderstanding to get the info requested deCONZ needs to have actually been able to see the device. I can't get that to happen even. Do I just keep trying until it finally sees it? Also is the old WebApp or Phoscon the more appropriate choice for trying to get it seen?

@ebaauw
Copy link
Collaborator

ebaauw commented Nov 14, 2018

Until support is added, the sensor won't show in the REST API, and therefore not in Phoscon nor in the Web app. You need to search for it in one of these apps, and then look for the node in the deCONZ GUI on the server.

@sktaylortrash
Copy link
Author

Okay well I guess I'll just keep trying because it doesn't show up in the deCONZ gui on the server. That's where I was looking for it

@ebaauw
Copy link
Collaborator

ebaauw commented Nov 14, 2018

Is it a ZIgBee device?

@sktaylortrash
Copy link
Author

It says it is in the manual and on the box

@ebaauw
Copy link
Collaborator

ebaauw commented Nov 14, 2018

Ok, then the trick is to figure out how to reset it, so it wants to join the network. Make sure you run a recent version of deCONZ. You might want to power down all your ZigBee routers (lights), and keep the sensor in range of the RaspBee or ConBee, to force a direct connection. Make sure there's still room for new end devices on the RaspBee or ConBee (recent firmware versions allow 32, older versions only 10).

@sktaylortrash
Copy link
Author

So I did update to the newest release versions I could find.
Version 2.05.47 / 11/13/2018
Firmware 262F0500

Powered down everything but the Pi with the RaspBee and I only have 2 endpoints according to deCONZ which makes sense as I only have 1 motion sensor and 1 remote.

The reset procedure is hold the button for 5 seconds until the red light flashes.
I tried 15-20 times to no avail, yet it works over and over again with an older smartthings hub.
I tried with the sensor next to the Pi and a few feet away in case that made a difference as well

Is it possibly because the device is ZigBee 3.0 the ConBee page lists itself as compatible but the RaspBee page makes no mention of it

@manup
Copy link
Member

manup commented Nov 14, 2018

Just to check, did you also put deCONZ in sensor search mode?

Phoscon App > Menu > Sensors > Add new sensor > Other

@manup
Copy link
Member

manup commented Nov 14, 2018

Is it possibly because the device is ZigBee 3.0 the ConBee page lists itself as compatible but the RaspBee page makes no mention of it

They both share the same software and firmware, so it doesn't make a difference, the sensor should at least join the network.

@sktaylortrash
Copy link
Author

sktaylortrash commented Nov 14, 2018

I tried both from Phoscon as described and also from the old WebApp and just opening the network neither was successful

@sktaylortrash
Copy link
Author

sktaylortrash commented Nov 14, 2018

Okay so I unboxed a different unit and it showed up immediately so here's the pics. No idea what I did different
image
image

image

Hope I did that right

@ebaauw
Copy link
Collaborator

ebaauw commented Nov 15, 2018

Cool. Can you also post screenshots of the IAS Zone and Temperature measurement clusters, after reading the attributes. You need to wake the sensor (by briefly pressing the button) before the attributes can be read.

@sktaylortrash
Copy link
Author

Ok here are those clusters as well thanks
image
image

@sktaylortrash
Copy link
Author

Couple quick questions.

  1. I see that has been tagged as device integration - so presumably that means you have the info you need from me?
  2. Is there anything I can manually change in the GUI to get the sensor to show up in the API in the meantime?

Thanks

mysteryan added a commit to mysteryan/deconz-rest-plugin that referenced this issue Dec 12, 2018
mysteryan added a commit to mysteryan/deconz-rest-plugin that referenced this issue Dec 12, 2018
Button triggers websocket notifications in rest api, but single, double and hold still aren’t distinguishable from each other.
dresden-elektronik#993
dresden-elektronik#946
manup pushed a commit that referenced this issue Dec 16, 2018
Add Samsung SmartThings manufaturer code
#993
#946
@stale
Copy link

stale bot commented Mar 21, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 21, 2019
@sktaylortrash
Copy link
Author

This issue should not be closed as the sensor still is not supported

@stale stale bot removed the stale label Mar 21, 2019
@stale
Copy link

stale bot commented Jul 19, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 19, 2019
@stale stale bot closed this as completed Jul 26, 2019
@srg74
Copy link

srg74 commented Aug 6, 2019

Sensor is paired and show proper values in the beginning and suddenly became unavailable. After pairing again working for some time and disappear again.

@sktaylortrash
Copy link
Author

Sensor is paired and show proper values in the beginning and suddenly became unavailable. After pairing again working for some time and disappear again.

I'm not seeing that issue

@srg74
Copy link

srg74 commented Aug 6, 2019

Sensor is paired and show proper values in the beginning and suddenly became unavailable. After pairing again working for some time and disappear again.

I'm not seeing that issue

Screen Shot 2019-08-06 at 4 23 22 PM

@MrHollowPS
Copy link

Sorry to dig this up. I'm trying to pair a first gen waterleak sensor, it shows up in the zigbee mesh but it doesn't get detected by the gateway in the phoscon app so i cannot use it in Home Assistant with deCONZ. Any ideeas?

@jdraxgit
Copy link

Sorry to dig this up. I'm trying to pair a first gen waterleak sensor, it shows up in the zigbee mesh but it doesn't get detected by the gateway in the phoscon app so i cannot use it in Home Assistant with deCONZ. Any ideeas?

I have the same issue, any fixes/updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants