DY-SQ100B Not working?

Compatible devices
1

I got a bunch of DY-SQ100B from AliExpress and I tested with two units and saw something register as like Generic Remote and nothing matches what I read online. I bought these due them being recommended from the supported devices page.

I’m using a LilyGO v2.1 board running 433 of course and see other devices I have and even don’t have.

What do I need to do, test, or troubleshoot? Thanks!

2

They were supported before the integration of RTL_433, with RF gateway
image
This module uses an SRX882 or equivalent as a receiver, not an SX127X like you have

Not sure they can work with RTL_433, could you give more details like the messages you are getting from the detection?

3

Here is what I see when I run rtl_433 with the 433.92Mhz setup.

tag       : g002_433.92M_250k.cu8                  time      : 2023-08-19T21:28:30.423189-0400
model     : Generic-Remote                         House Code: 30847
Command   : 205          Tri-State : Z1X0Z111101Z

Here is the capture file from RTL-433 as well.

Any help is appreciated as I bought 12 of these things thinking they would work due to the site

4

And with the Lilygo what do you see?

5

I bumped up the logging via the webui to verbose and captured this when I touched the sensor leads:

T: isAdupl?
N: Send on /RTL_433toMQTT/Generic-Remote/26240 msg {"model":"Generic-Remote","id":26240,"cmd":205,"tristate":"ZXZXX000101Z","protocol":"Generic Remote SC226x EV1527","rssi":-94,"duration":2702002}
T: jsonPubl - ON
T: [ OMG->MQTT ] topic: home/OMG-RTL-433-laundry/RTL_433toMQTT/Generic-Remote/26240 msg: {"model":"Generic-Remote","id":26240,"cmd":205,"tristate":"ZXZXX000101Z","protocol":"Generic Remote SC226x EV1527","rssi":-94,"duration":2702002} 
T: Min ind: 11
T: store code : 26240 / 833186879
T: Col: val/timestamp
T: mem code : 26240 / 833082204
T: mem code : 15004 / 833091278
T: mem code : 15311 / 833106130
T: mem code : 9320 / 833107474
T: mem code : 15004 / 833107965
T: mem code : 15311 / 833122586
T: mem code : 15311 / 833139392
T: mem code : 9320 / 833141751
T: mem code : 15004 / 833141789
T: mem code : 15004 / 833158315
T: mem code : 6373 / 833158947
T: mem code : 26240 / 833186879
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?
T: no pub. dupl
T: isAdupl?

If there is something else I need to do let me know.

6

What is preventing you from using the msg sent?

7

I mean I guess I could use this but it wasn’t what I saw from others with their experience. It only triggers when water is detected so could do that.

8

So I was able to play more with the device and using OMG AutoDiscovery into HA it only comes through with the RSSI as a sensor. I know I can use templates in HA to give me the “last updated” time of the device and if that time is RECENT it is known the contacts connected. While this is a viable solution it is of course less than ideal.

Any recommendations?

9

Yes I would advise using the cmd value with a timeout, by creating an mqtt sensor into your configuration.yaml.