Configuring Tuya/SmartLife Alarm PIR Motion Sensor (CT61W) with CB3S (BK7231N) Module

Name: Configuring Tuya/SmartLife Alarm PIR Motion Sensor (CT61W) with CB3S (BK7231N) Module
Uploaded: 2023-05-13T21:50:41+02:00
Description: Hi! I recently purchased this product and I have successfully installed the openbeken software after seeing that they changed the module from TYWE3S to CB3S (BK7231N). But now I'm stuck on how to configure it because there is no template for it... Can anyone give me a hand? :)

Question

Hi! I recently purchased this product and I have successfully installed the openbeken software after seeing that they changed the module from TYWE3S to CB3S (BK7231N). But now I'm stuck on how to configure it because there is no template for it... Can anyone give me a hand? :)

p.kaczmarek2 · Accepted Answer

Hello, it looks like a PIR sensor without TuyaMCU, altough you could confirm that by showing the other side of the PCB.

In case of version without TuyaMCU, you'll have to use deep sleep feature of OpenBeken to preserve battery life, but we already got it working for door sensors and more:
Door/window sensor without TuyaMCU - deep sleep and energy saving, OpenBeken
[OpenBeken] SHT Sensor configuration, commands, and deep sleep usage with wake up on pin change
but before invoking deep sleep, we need to know which GPIOs are used.

Are you able to determine which GPIO is used for PIR sensor, which is used for button, for battery level, etc?

@dheenhasty do you think your battery driver can run on that?

Btw... huh, manufacturer says batteries will last for 6 hours only? I think with OBK they could last longer than that, of course.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

p.kaczmarek2 · Accepted Answer

TuyaMCU is protocol used to communication between WiFi module and external MCU. Some Tuya devices are designed that way. It seems that your is without TuyaMCU.

Hmm if you are going to power is constantly, then indeed Deep sleep is not required. I that case configuration would be very, very simple.

You just need to find out which GPIO is used dinput sensor.

So, the device was using TYWE3S in the past? Here is GPIO13:

And here are CB3S GPIOs:

Pin number	Symbol	I/O type	Function
1	RST	I	Low-level reset, high level active (the pin has been pulled high internally), correspond to CEN of the IC
2	ADC3	AI	ADC pin, which corresponds to P23 of the IC
3	CEN	I	Enabling pin, which is pulled high internally to be compatible with other modules
4	P14	I/O	A common GPIO interface, which corresponds to P14 of the IC
5	P26	I/O	GPIOP_26, which corresponds to P26 of the IC, PWM 5
6	P24	I/O	GPIOP_24, which corresponds to P24 of the IC, PWM 4
7	P6	I/O	GPIOP_6, which corresponds to P6 of the IC, PWM 0
8	VCC	P	Power supply pin (3.3V)
9	GND	P	Power supply reference ground
10	P9	I/O	GPIOP_9, which corresponds to P9 of the IC, PWM 3
11	TXD2	I/O	UART2_TXD (used to display the module internal information), which corresponds to P0 of the IC
12	CSN	I/O	Production test control pin. If it is used as a common I/O pin, it must be connected to the VCC externally. Do not connect it to the ground before the module is powered on.
13	P8	I/O	GPIOP_8, which corresponds to P8 of the IC, PWM 2
14	P7	I/O	GPIOP_7, which corresponds to P7 of the IC, PWM 1
15	RXD1	I/O	UART1_RXD (user serial interface), which corresponds to P10 of the IC. Do not connect it to the VCC. By default, the MCU serial port should be in low-level or high-impedance state.
16	TXD1	I/O	UART1_TXD (user serial interface), which corresponds to P11 of the IC. Do not connect it to the VCC. By default, the MCU serial port should be in low-level or high-impedance state.
17	ADC3	AI	(Not recommended. If needed, please use Pin 2) ADC port, which corresponds to P23 of the IC. Programmed SPI
18	P22	I/O	(Not recommended ) GPIOP_22, which corresponds to P22 of the IC. Programmed SPI
19	CSN	I/O	The pull-up resistor is needed during usage of customers. Do not connect it to the ground before the module is powered on. Correspond to P21 of the IC.
20	P20	I/O	(Not recommended. ) GPIOP_20, which corresponds to P20 of the IC. Programmed SPI

I think we can already see which one is GPIO13 equivalent in CB3S. OpenBeken is using P* indexes.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

p.kaczmarek2 · Accepted Answer

Hello, if you look into our auto-generated docs:
https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/README.md
the IO Pin Roles, to be exact:
https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/ioRoles.md
You can find out that:

DigitalInput	this is a simple digital input pin, it sets the linked channel to current logical value on it, just like digitalRead( ) from Arduino. This input has a internal pull up resistor.
DigitalInput_n	As DigitalInput as above, but inverted
ToggleChannelOnToggle	this pin will toggle target channel when a value on this pin changes (with debouncing). you can connect simple two position switch here and swapping the switch will toggle target channel relay on or off
DigitalInput_NoPup	As DigitalInput, but without internal programmable pullup resistor. This is used for, for example, XR809 water sensor and door sensor.
DigitalInput_NoPup_n	As DigitalInput_n, but without internal programmable pullup resistor

The device will do a MQTT publish when a channel value changes, for example:


OBK_DEV_NAME/2/get

with payload equal to channel value.

You can also use autoexec.bat to create event handlers and custom publishes, for example:


addEventHandler OnChannelChange 1 publishInt mySensorState $CH1

or


addChangeHandler Channel1 == 1 publish myDoor nowClosed
addChangeHandler Channel1 == 0 publish myDoor nowOpen

You can do much more with scripts, for example, you could send a HTTP GET request to a target HTTP server when a channel value is changed.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

pincopallino1010 · Answer

What is TuyaMCU?

I am a little bit scared to reopen it cause the battery pack is soldered underneath the PCB.. but it seems that there is nothing underneath (i've tried to take a picture tho).

Do I really need to use the deep sleep feature? Cause I was thinking of connecting it directly to my UPS via USB-C without any battery.
Talking about the GPIO, I'm completely blind cause when I purchased it I was hoping to receive the ESP8266 model which have this GPIO..

So I have no idea how to retrieve them for this model and I was hoping that someone can give me a hand 😐

EDIT: These could be the pin definitions? https://developer.tuya.com/en/docs/iot/cb3s?id=Kai94mec0s076#title-5-Pin%20definition
Here also says that

Quote:
CB3S is built in with a 32-bit MCU

pincopallino1010 · Answer

Ok so if I understand correctly the GPIO13 on the TYWE3S is responsible for taking input from the PIR sensor.
On the CB3S it corresponds to the pin number 10, so I have to set the P9 pin like this?

EDIT: I notice that it remains always on 1 even if I wave my hand on it

I have also noticed that if I set this pin

The speaker turns on and I see this

p.kaczmarek2 · Answer

It seems that TYWE3S has shown a bottom view while the CB3S has a top view. Your GPIO13 would have CB3S index 7 then, which is P6.

pincopallino1010 · Answer

Yay! It worked

So now how can I access that value (I mean the 1 / 0 when the PIR is triggered).
Cause I wanted to turn on / off a switch based on this value via python script.

EDIT: And also, what is the difference between these values?

pincopallino1010 · Answer

Exactly! My idea is to send an HTTP GET request to a Tasmota switch in order to turn it on. How can I achieve this on OpenBeken? EDIT: Or in a more controlled way (since if the Sonoff will turn on it will turn on the siren) how can I send it to a Debian system in order to manage it via script?

p.kaczmarek2 · Answer

If you look into our console commands examples section here: you can find:

pincopallino1010 · Answer

OMG thanks a lot! You helped me make a little dream come true

p.kaczmarek2 · Answer

Btw, please post full final device config from Web App and your scripts as well if you can, so I can add this topic to the supported devices list.

Also, if you still have it, post some screenshots where device was bought and how the packaging looks like (model number? app name? etc)

Thanks!

pincopallino1010 · Answer

This is my template (I have only changed the pin) Code: text Expand Select all Copy to clipboard {   vendor: Tuya,   bDetailed: 0,   name: Full Device Name Here,   model: enter short model name here,   chip: BK7231N,   board: TODO,   keywords: [     TODO,     TODO,     TODO   ],   pins: {     6: dInput;1   },   image:    wiki:  } I have bought it from here (Aliexpress) And this is the package

p.kaczmarek2 · Answer

What about those two pin roles from old Tasmota template?

Let's try to support them somehow.

For example, if you set LED channel to the same channel that dInput has, then LED will reflect dInput state.

pincopallino1010 · Answer

I've tried to set the LED channel to the same channel that dinput has, but it seems not doing what we expect

p.kaczmarek2 · Answer

What does it do?

pincopallino1010 · Answer

Literally nothing 🤔

p.kaczmarek2 · Answer

Are you sure? It seems.... impossible.
If you have a dInput set for a given channel, then this dInput will sample logical value on its pin every frame and force-set the channel to 1 (if high) or to 0 (if low).
Then, if you have a LED on the same channel, the LED will follow the value from the channel. You can also use LED_n for inverted following.

Maybe... maybe do a little test - set that LED pin channel to something like Channel 5, and then try toggling channel 5 value and see if it blinks on the device. Via web GUI or commands - "toggleChannel 5". The LED should blink. If it's not blinking, then you've selected wrong GPIO.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

p.kaczmarek2 · Answer

I've just got one PIR sensor. Here's dInput + LED result on the same channel, of course on correct GPIO:

It reacts to movement. Channel switch to 1 for the time movement is there and later, with some delays, returns to 0.

mkmunichmk · Answer

@p.kaczmarek2, I have the same Tuya PIR device. Is there a template available for it? BR, MK

p.kaczmarek2 · Answer

I haven't finished the teardown article about it yet, but here is the JSON:

Log in, to see the code

Here is text description:


Device configuration, as extracted from Tuya: 
- Button (channel 0) on P20
- Status LED on P26
- PIR sensor on P16
- Battery Relay on P17
- Battery Max Voltage: 3000
- Battery Min Voltage: 2200
- Battery ADC on P23
Device seems to use Battery Driver. See more details here: https://www.elektroda.com/rtvforum/topic3959103.html
Device seems to be using CBU module, which is using BK7231N.
And the Tuya section starts, as usual, at 2023424

This is not a final config, it will require some little work to finish it.

pincopallino1010 · Answer

Hi, sorry I haven't replied to you more, but I've been busy these months :/

I saw that you carried on the work, great! I wonder, is there any way to control the sensitivity of the sensor in such a way to have a wider/narrower range of the sensor range?

Also, I tried out this configuration, but importing it resets my whole device without setting any pins. Am I doing something wrong?

p.kaczmarek2 · Answer

This sensor only provides us a binary signal, telling whether there was something detected or now, therefore it's not possibly to tune it at the WiFi module side.

PIR sensor configuration automatic import may not be ready yet, you need to enter it manually. Use it to extend what you've already got.

You will also need to get Deep Sleep running on this device. This is required to preserve battery life. Have you looked into the Deep Sleep mechanism of OpenBeken? We have some threads covering this topic, for example, here:
https://www.elektroda.com/rtvforum/topic3960149.html

pincopallino1010 · Answer

Um, I see. In which of the two spaces should I enter the configuration? Regarding deep sleep, since I connected the sensor directly by cable to an UPS I shouldn't need it, right?

p.kaczmarek2 · Answer

Hmm ok, you don't need deep sleep if you power device from cables. Configuration should be pasted in the first field, but as I said, the PIR data may need to be entered manually, not via importer.

pincopallino1010 · Answer

So I copied and pasted it here and it says this, does that mean it's okay? About the PIR data that may need to be entered manually, do you mean these?

p.kaczmarek2 · Answer

The following screenshot shows that no config was imported from that JSON. It seems that we have to update our importer to cover PIR data. As I said, PIR most likely will have to be done manually, for now... . I will try to look into that in the following days.

pincopallino1010 · Answer

Thank you very much for all the support, I apologize for not being able to respond in time

Unfortunately, the device stopped working suddenly (probably due to some soldering gone wrong) and I bought some sensors that are more suitable for my case... in fact, I asked here if, after flashing them with the new firmware, I need to tweak some other things.

Configuring Tuya/SmartLife Alarm PIR Motion Sensor (CT61W) with CB3S (BK7231N) Module

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Topic summary