-
Notifications
You must be signed in to change notification settings - Fork 502
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
Comments
I don’t think that is yet supported by deCONZ. Please see |
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? |
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. |
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 |
Is it a ZIgBee device? |
It says it is in the manual and on the box |
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). |
So I did update to the newest release versions I could find. 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. 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 |
Just to check, did you also put deCONZ in sensor search mode? Phoscon App > Menu > Sensors > Add new sensor > Other |
They both share the same software and firmware, so it doesn't make a difference, the sensor should at least join the network. |
I tried both from Phoscon as described and also from the old WebApp and just opening the network neither was successful |
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. |
Couple quick questions.
Thanks |
Add Samsung SmartThings manufaturer code dresden-elektronik#993 dresden-elektronik#946
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
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. |
This issue should not be closed as the sensor still is not supported |
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. |
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 |
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? |
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.
The text was updated successfully, but these errors were encountered: