I've missed that part, my apologies.
Thanks for your help and to allow my tuya devices a new life with home assistant.
I managed to write OpenBeken firmware and it works.
But I think that I've broken the magnetic field sensor because although I put the magnet closer the device don't stops.
By the way, I've seen that CB3S supports bluetooth.
That could be interesting for a door sensor, to detect which devices are near when the door is opened.
Unfortunately I don't have much time at the moment.
I don't know if your problem is solved, but I also had problems with flashing the device initially. When flashing I had a write error again and again.
I fixed it by changing the USB serial device. It was the same guy. I don't know why, but the other one works fine.
I used the flashing tool (Buffalo in version 1.4.8 as described in the discussion).
Hello I have this door open sensor. I uploaded OpenBK version 1.15.468 to it, so far it works without any problems. I analyzed the board and drew a schematic. Maybe someone will like it.
Hello, thanks for the diagram. This door sensor, i.e. the one from TuyaMCU?
Remember that if your door/window sensor does not have TuyaMCU and is implemented on the WiFi chip only, then you should consider its configuration to work with Deep Sleep and wake up by changing the state on the pin.
Also (in any case) it is worth considering adding the PowerSave command to the short startup command, which in turn starts the hybrid sleep mode (the device supposedly works all the time, but it saves energy). PowerSave will soon be set to 1 by default in every release (you won't need to enable it), but we're still testing it.
I have a request, could you tell me how to implement a pin-triggered Deep sleep into Open BK. (I searched the web, but unfortunately I couldn't find the information I needed). I have already implemented power save.
@miroww1 for simple situations, it is enough to set the roles of, for example, a button for a pin and use the PinDeepSleep command, then the device will "sleep" and this button will wake it up, but more complex logic is needed for the door controller.
I guess for the door sensor I will just write you a ready-made driver that will cover everything, can you look at this topic? https://www.elektroda.com/rtvforum/topic3959677.html#20455596 There is a similar question and I would like to continue the discussion in one place.
The sensor from this topic (from the first post), DS06, uses TuyaMCU, and there the external MCU gets sleep and turns off the WiFI module. Your door open sensor is different, yours doesn't have TuyaMCU, there is only Beken itself.
Today, 2023-04-30, Tuya battery devices driver has been updated to cover both formats with and without date.
Here's a summary of a setup for such devices (like in the first post).
1. Do UART capture to figure out dpId meanings:
https://www.elektroda.com/rtvforum/topic3970199.html#20528459 2. Flash OBK, you may need to cut traces because TuyaMCU will interfere with UART communication. You also will need to connect power to 3.3V of WiFi module because otherwise TuyaMCU can cut off its power (see first post)
https://github.com/openshwprojects/BK7231GUIFlashTool 3. Configure obk wifi and pass, also add autoexec with tuyaMCU dpIDs mapping , here is my sample:
startDriver TuyaMCU
startDriver tmSensor
// may be needed, depends on device
//tuyaMcu_setBaudRate 115200
// map dpID 1 to channel 1
linkTuyaMCUOutputToChannel 1 val 1
setChannelType 1 OpenClosed
// map dpID 3 to channel 3
linkTuyaMCUOutputToChannel 3 val 3
setChannelType 3 Custom
4. configure HA to receive that, here is a small sample:
Code: YAML
Log in, to see the code
5. Now remember, the wifi module will be on for a very short time when door state changes, TuyaMCU will later power it off and go into deep sleep, but you can also keep it powered longer by pressing for a long time (several seconds) the pair button multiple times
6. now, door state changes will result in such or similar log (if you keep Web App Log Open, you may see it):
Info:MAIN:Main_Init_Before_Delay
Info:CFG:####### Boot Count 26 #######
Warn:CFG:CFG_InitAndLoad: Correct config has been loaded with 7 changes count.
Error:CMD:no file early.bat err -2
Info:GEN:PIN_SetupPins pins have been set up.
Info:MAIN:Main_Init_Before_Delay done
Info:MAIN:Main_Init_Delay
Info:MAIN:Main_Init_Delay done
Info:MAIN:Main_Init_After_Delay
Info:MAIN:ssid:MY_WIFI_SSID key:MY_WIFI_PASS
Info:MAIN:Using SSID [MY_WIFI_SSID]
Info:MAIN:Using Pass [MY_WIFI_PASS]
Info:MQTT:MQTT_RegisterCallback called for bT t_mcu_door/ subT t_mcu_door/+/set
Info:MQTT:MQTT_RegisterCallback called for bT bekens/ subT bekens/+/set
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/t_mcu_door/ subT cmnd/t_mcu_door/+
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/bekens/ subT cmnd/bekens/+
Info:MQTT:MQTT_RegisterCallback called for bT t_mcu_door/ subT t_mcu_door/+/get
Info:CMD:CMD_StartScript: started autoexec.bat at the beginning
Info:MAIN:Main_Init_After_Delay done
Info:MAIN:Started TuyaMCU.
Info:MAIN:Started tmSensor.
Info:GEN:Channel 1 type changed to OpenClosed
Info:GEN:Channel 3 type changed to Custom
Info:MAIN:Time 1, idle 247169/s, free 83744, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 2, idle 245680/s, free 83744, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:TuyaMCU:TUYAMCU received: 55 AA 00 01 00 24 7B 22 70 22 3A 22 33 73 6C 70 69 72 6C 6E 6C 71 70 30 62 71 6F 31 22 2C 22 76 22 3A 22 31 2E 30 2E 30 22 7D C6
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 1 (QueryProductInformation) with 43 bytes
Info:TuyaMCU:TuyaMCU_ParseQueryProductInformation: received {"p":"3slpirlnlqp0bqo1","v":"1.0.0"}
Info:TuyaMCU:TUYAMCU received: 55 AA 00 05 00 05 01 01 00 01 01 0D
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 5 (WiFiSelect) with 12 bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: processing dpId 1, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: raw data 1 byte:
Info:GEN:CHANNEL_Set channel 1 has changed to 1 (flags 0)
Info:MQTT:Channel has changed! Publishing 1 to channel 1
Info:MAIN:Time 3, idle 94355/s, free 83808, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 4, idle 0/s, free 83808, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTING - 1
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:MQTT:mqtt_userName homeassistant
mqtt_pass ma1oovoo0pooTie7koa8Eiwae9vohth1vool8ekaej8Voohi7beif5uMuph9Diex
mqtt_clientID t_mcu_door
mqtt_host 192.168.0.113:1883
Info:MAIN:Time 5, idle 121902/s, free 83704, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:mqtt_connection_cb: Successfully connected
Info:MQTT:mqtt_subscribed to t_mcu_door/+/set
Info:MQTT:mqtt_subscribed to bekens/+/set
Info:MQTT:mqtt_subscribed to cmnd/t_mcu_door/+
Info:MQTT:mqtt_subscribed to cmnd/bekens/+
Info:MQTT:mqtt_subscribed to t_mcu_door/+/get
Info:MQTT:Publishing val obk61B58371 to t_mcu_door/host retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 00 02 00 00 01
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 2 (MCUconf) with 7 bytes
Info:TuyaMCU:TuyaMCU_ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:MAIN:Time 6, idle 245750/s, free 83936, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MAIN:Boot complete time reached (5 seconds)
Info:CFG:####### Set Boot Complete #######
Info:MQTT:Publishing val Build on Apr 30 2023 13:32:58 version 1.0.0 to t_mcu_door/build retain=0
Info:MAIN:Time 7, idle 233534/s, free 83664, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:Publishing val 10:d5:61:b5:83:71 to t_mcu_door/mac retain=0
Info:MAIN:Time 8, idle 247547/s, free 83936, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:Publishing val 3 to t_mcu_door/sockets retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 00 02 00 00 01
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 2 (MCUconf) with 7 bytes
Info:TuyaMCU:TuyaMCU_ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:TuyaMCU:TUYAMCU received: 55 AA 00 05 00 05 03 04 00 01 02 13
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 5 (WiFiSelect) with 12 bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: processing dpId 3, dataType 4-DP_TYPE_ENUM and 1 data bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: raw data 1 byte:
Info:GEN:CHANNEL_Set channel 3 has changed to 2 (flags 0)
Info:MQTT:Channel has changed! Publishing 2 to channel 3
Info:MQTT:Publishing val 2 to t_mcu_door/3/get retain=0
Info:MAIN:Time 9, idle 265333/s, free 72208, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic t_mcu_door/3/get
Info:MQTT:Publishing val -52 to t_mcu_door/rssi retain=0
Info:MAIN:Time 10, idle 226762/s, free 83704, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:GEN:dhcp=0 ip=192.168.0.235 gate=192.168.0.1 mask=255.255.255.0 mac=10:d5:61:b5:83:71
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-52,ssid=MY_WIFI_SSID,bssid=28:87:ba:a0:f5:6d ,channel=3,cipher_type:CCMP
Info:MQTT:Publishing val 10 to t_mcu_door/uptime retain=0
Info:MAIN:Time 11, idle 245307/s, free 83704, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:Publishing val 72208 to t_mcu_door/freeheap retain=0
Info:MAIN:Time 12, idle 251851/s, free 72208, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38
Info:MQTT:Publishing val 192.168.0.235 to t_mcu_door/ip retain=0
Info:MAIN:Time 13, idle 245380/s, free 83936, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:Channel has changed! Publishing 1 to channel 1
Info:MQTT:Publishing val 1 to t_mcu_door/1/get retain=0
Info:MAIN:Time 14, idle 247389/s, free 83936, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic t_mcu_door/1/get
Info:MQTT:Channel has changed! Publishing 2 to channel 3
Info:MQTT:Publishing val 2 to t_mcu_door/3/get retain=0
Info:MAIN:Time 15, idle 244718/s, free 83936, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic t_mcu_door/3/get
Info:MAIN:Time 16, idle 493519/s, free 83936, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
After 4 seconds, I get WiFI with DHCP (quick wifi connect flag in flags). After 6 seconds, I get MQTT. After whole 16 seconds, the device goes to sleep. The communication speed can be improved soon.
Hi, my Tuya door contact device is moreless looking identical to the water-leakage-detector (https://obrazki.elektroda.pl/1674347900_1671892731.jpg) refer to #13 from 24th december 2022. I was able to install openBeken onto my device and I'm struggling with the correct configuration...
In order to avoid the problem, that TuyaMcu is powering the CBS3 I just soldered wires to GND and VCC of the CBS3; so the CBS3 is permanetely powered (if wanted).
I tried the following configuration (not knowing which DP are really used by my device):
It is strange, because the output does not correlate with the door state. Even worse, the DP states are sent sporadically; means they are send rarely and not when contact state is changing. I have currently no MQTT broker running - would this make a difference? I did not try yet.
Added after 1 [minutes]:
At this moment I'm using this autoexec.bat:
backlog startDriver tuyaMCU
startDriver tmSensor
linkTuyaMCUOutputToChannel 1 val 1
setChannelType 1 ReadOnly
linkTuyaMCUOutputToChannel 3 val 3
setChannelType 3 ReadOnly
I think that powering CB3S constantly is the source of your problems.
I may be wrong, but as far as I remember, and I did quite a research on this topic, the TuyaMCU on battery powered devices works in such a way that the MCU powers on the WiFi module and WiFi module then sends the first UART packet to the MCU. WiFi module initiates the transaction, and MCU only responds, so timings are crucial.
If you power on the WiFi module permanently ,you break the communication standard and get undefined behaviour.
I have tested two door sensors and in both cases it worked reliable when I was following the protocol as designed by Tuya.
Hi, I repeated the test by NOT powering the CB3S. Please find the SniffUART recording attached (this file can be imported into SniffUART). I opend the magnet contact and got a change in DP1 from false to true. So half way is done. Still missing the magnet close event from DP1= true to false. I guess, there is something wrong in my autoexec.bat above?
Best Regards MK_Munich
Hi @p.kaczmarek2, I'm digging into it From the Serial Port Protocol of Wi-Fi for Low Power Devices in the flowchart below section "Report the real-time status" it is seen, that values are reported by MCU to CB3S after CB3S tells the MCU, that connected to network. In my attached SniffUART recording above this behavior is seen. For this I would guess, that in case of closing the contact, the "Report Network Status" message is missing?
In an other sniff after I closed and opened the contact I got (after "Report Network Status") DP1=false , then =true and back to =false.
thanks for all the information in this thread, it helped me setting up this sensor. I have a slightly different version with CBU module, else it looks similar and seems to have the same other components:
Now, after reading through and trying some things I understand a little more about how it works with MCU (but still just a little!). And I found that I have the same problem as mentioned in your post >>20351761 that I am referring to here.
The MCU is activated through button press or bridging of the water probes and then transmits data to CBU module. But same problem for me here: when WET after few seconds from last connect, it sends only battery value to MQTT, and claims that the water status hasn't changed and therefore ignores the send. Please have a look at the log:
Spoiler:
Info:MAIN:Main_Init_Before_Delay
Info:CFG:####### Boot Count 300 #######
Warn:CFG:CFG_InitAndLoad: Correct config has been loaded with 100 changes count.
Error:CMD:no file early.bat err -2
Info:GEN:PIN_SetupPins pins have been set up.
Info:MAIN:Main_Init_Before_Delay done
Info:MAIN:Main_Init_Delay
Info:MAIN:Main_Init_Delay done
Info:MAIN:Main_Init_After_Delay
Info:MAIN:Using SSID [***]
Info:MAIN:Using Pass [***]
Info:MQTT:MQTT_RegisterCallback called for bT bksensor_WL00/ subT bksensor_WL00/+/set
Info:MQTT:MQTT_RegisterCallback called for bT bekensensors/ subT bekensensors/+/set
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/bksensor_WL00/ subT cmnd/bksensor_WL00/+
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/bekensensors/ subT cmnd/bekensensors/+
Info:MQTT:MQTT_RegisterCallback called for bT bksensor_WL00/ subT bksensor_WL00/+/get
Info:MAIN:Started tuyaMCU.
Info:MAIN:Started tmSensor.
Info:GEN:Channel 1 type changed to ReadOnly
Info:GEN:Channel 3 type changed to ReadOnly
Info:CMD:LFS_ReadFile: failed to file autoexec.bat
Info:CMD:CMD_StartScript: failed to get file autoexec.bat
Info:MAIN:Main_Init_After_Delay done
Info:MAIN:Time 1, idle 282468/s, free 77552, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:TuyaMCU:TUYAMCU received: 55 AA 00 01 00 24 7B 22 70 22 3A 22 78 62 62 6A 35 35 74 32 63 71 62 6B 31 69 74 70 22 2C 22 76 22 3A 22 31 2E 30 2E 30 22 7D 74
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 1 (QueryProductInformation) with 43 bytes
Info:TuyaMCU:TuyaMCU_ParseQueryProductInformation: received {"p":"xbbj55t2cqbk1itp","v":"1.0.0"}
Info:MAIN:Time 2, idle 190780/s, free 77552, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 3, idle 184680/s, free 77552, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 4, idle 192370/s, free 77552, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 5, idle 191162/s, free 77552, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:ssid:FunkLoch key:1607198654321
Info:MAIN:Time 6, idle 182891/s, free 72816, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Boot complete time reached (5 seconds)
Info:CFG:####### Set Boot Complete #######
Info:MAIN:Time 7, idle 182298/s, free 72112, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 8, idle 85434/s, free 72088, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 9, idle 0/s, free 72088, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 10, idle 0/s, free 72088, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:GEN:dhcp=0 ip=0.0.0.0 gate=0.0.0.0 mask=0.0.0.0 mac=50:8b:b9:3b:ce:ce
Info:GEN:sta: 0, softap: 0, b/g/n
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTING - 1
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:MAIN:Time 11, idle 91465/s, free 72496, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:TuyaMCU:TUYAMCU received: 55 AA 00 02 00 00 01
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 2 (MCUconf) with 7 bytes
Info:TuyaMCU:TuyaMCU_ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:MAIN:Time 12, idle 193748/s, free 60840, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 3/38
Info:MQTT:mqtt_userName ***
mqtt_pass ***
mqtt_clientID bksensor_WL00
mqtt_host 192.168.86.6:1883
Info:MAIN:Time 13, idle 189733/s, free 72448, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:mqtt_connection_cb: Successfully connected
Info:MQTT:mqtt_subscribed to bksensor_WL00/+/set
Info:MQTT:mqtt_subscribed to bekensensors/+/set
Info:MQTT:mqtt_subscribed to cmnd/bksensor_WL00/+
Info:MQTT:mqtt_subscribed to cmnd/bekensensors/+
Info:MQTT:mqtt_subscribed to bksensor_WL00/+/get
Info:MQTT:Publishing val WL00 to bksensor_WL00/host retain=0
Info:MAIN:Time 14, idle 181666/s, free 72448, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:Publishing val Build on Aug 29 2023 23:56:28 version 1.17.231 to bksensor_WL00/build retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 00 02 00 00 01
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 2 (MCUconf) with 7 bytes
Info:TuyaMCU:TuyaMCU_ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:TuyaMCU:TUYAMCU received: 55 AA 00 08 00 0C 00 02 02 02 02 02 02 01 04 00 01 00 25
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 8 (QueryState) with 19 bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: processing dpId 1, dataType 4-DP_TYPE_ENUM and 1 data bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: raw data 1 byte:
Info:GEN:No change in channel 1 (still set to 0) - ignoring
Info:MAIN:Time 15, idle 188993/s, free 72448, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:Publishing val 50:8b:b9:3b:ce:ce to bksensor_WL00/mac retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 00 08 00 0C 00 01 01 01 01 01 01 03 04 00 01 01 22
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 8 (QueryState) with 19 bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: processing dpId 3, dataType 4-DP_TYPE_ENUM and 1 data bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: raw data 1 byte:
Info:GEN:CHANNEL_Set channel 3 has changed to 1 (flags 0)
Info:MQTT:Channel has changed! Publishing 1 to channel 3
Info:MQTT:Publishing val 1 to bksensor_WL00/3/get retain=0
Info:MAIN:Time 16, idle 179609/s, free 72448, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic bksensor_WL00/3/get
Info:MQTT:Publishing val FunkLoch to bksensor_WL00/ssid retain=0
Info:MAIN:Time 17, idle 176748/s, free 72448, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MAIN:Main_Init_Before_Delay
Info:CFG:####### Boot Count 301 #######
Warn:CFG:CFG_InitAndLoad: Correct config has been loaded with 100 changes count.
Error:CMD:no file early.bat err -2
Info:GEN:PIN_SetupPins pins have been set up.
Info:MAIN:Main_Init_Before_Delay done
Info:MAIN:Main_Init_Delay
Info:MAIN:Main_Init_Delay done
Info:MAIN:Main_Init_After_Delay
Info:MAIN:Using SSID [***]
Info:MAIN:Using Pass [***]
Info:MQTT:MQTT_RegisterCallback called for bT bksensor_WL00/ subT bksensor_WL00/+/set
Info:MQTT:MQTT_RegisterCallback called for bT bekensensors/ subT bekensensors/+/set
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/bksensor_WL00/ subT cmnd/bksensor_WL00/+
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/bekensensors/ subT cmnd/bekensensors/+
Info:MQTT:MQTT_RegisterCallback called for bT bksensor_WL00/ subT bksensor_WL00/+/get
Info:MAIN:Started tuyaMCU.
Info:MAIN:Started tmSensor.
Info:GEN:Channel 1 type changed to ReadOnly
Info:GEN:Channel 3 type changed to ReadOnly
Info:CMD:LFS_ReadFile: failed to file autoexec.bat
Info:CMD:CMD_StartScript: failed to get file autoexec.bat
Info:MAIN:Main_Init_After_Delay done
Info:MAIN:Time 1, idle 283851/s, free 77552, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:TuyaMCU:TUYAMCU received: 55 AA 00 01 00 24 7B 22 70 22 3A 22 78 62 62 6A 35 35 74 32 63 71 62 6B 31 69 74 70 22 2C 22 76 22 3A 22 31 2E 30 2E 30 22 7D 74
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 1 (QueryProductInformation) with 43 bytes
Info:TuyaMCU:TuyaMCU_ParseQueryProductInformation: received {"p":"xbbj55t2cqbk1itp","v":"1.0.0"}
Info:MAIN:Time 2, idle 188681/s, free 77552, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 3, idle 182450/s, free 77552, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 4, idle 191409/s, free 77552, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 5, idle 188950/s, free 77552, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:ssid:FunkLoch key:1607198654321
Info:MAIN:Time 6, idle 180034/s, free 72816, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Boot complete time reached (5 seconds)
Info:CFG:####### Set Boot Complete #######
Info:MAIN:Time 7, idle 179142/s, free 72112, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 8, idle 82993/s, free 72088, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 9, idle 0/s, free 72088, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:MAIN:Time 10, idle 0/s, free 72088, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38
Info:GEN:dhcp=0 ip=0.0.0.0 gate=0.0.0.0 mask=0.0.0.0 mac=50:8b:b9:3b:ce:ce
Info:GEN:sta: 0, softap: 0, b/g/n
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTING - 1
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:MAIN:Time 11, idle 89750/s, free 72456, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:TuyaMCU:TUYAMCU received: 55 AA 00 02 00 00 01
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 2 (MCUconf) with 7 bytes
Info:TuyaMCU:TuyaMCU_ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:MAIN:Time 12, idle 187911/s, free 72504, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:mqtt_userName ***
mqtt_pass ***
mqtt_clientID bksensor_WL00
mqtt_host 192.168.86.6:1883
Info:MAIN:Time 13, idle 184228/s, free 72416, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:mqtt_connection_cb: Successfully connected
Info:MQTT:mqtt_subscribed to bksensor_WL00/+/set
Info:MQTT:mqtt_subscribed to bekensensors/+/set
Info:MQTT:mqtt_subscribed to cmnd/bksensor_WL00/+
Info:MQTT:mqtt_subscribed to cmnd/bekensensors/+
Info:MQTT:mqtt_subscribed to bksensor_WL00/+/get
Info:MQTT:Publishing val WL00 to bksensor_WL00/host retain=0
Info:MAIN:Time 14, idle 362822/s, free 60712, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38
Info:MQTT:Publishing val Build on Aug 29 2023 23:56:28 version 1.17.231 to bksensor_WL00/build retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 00 02 00 00 01
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 2 (MCUconf) with 7 bytes
Info:TuyaMCU:TuyaMCU_ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:TuyaMCU:TUYAMCU received: 55 AA 00 08 00 0C 00 02 02 02 02 02 02 01 04 00 01 01 26
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 8 (QueryState) with 19 bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: processing dpId 1, dataType 4-DP_TYPE_ENUM and 1 data bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: raw data 1 byte:
Info:GEN:CHANNEL_Set channel 1 has changed to 1 (flags 0)
Info:MQTT:Channel has changed! Publishing 1 to channel 1
Info:MQTT:Publishing val 1 to bksensor_WL00/1/get retain=0
Info:MAIN:Time 15, idle 545831/s, free 60712, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic bksensor_WL00/1/get
Info:MQTT:Publishing val 50:8b:b9:3b:ce:ce to bksensor_WL00/mac retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 00 08 00 0C 00 01 01 01 01 01 01 03 04 00 01 01 22
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 8 (QueryState) with 19 bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: processing dpId 3, dataType 4-DP_TYPE_ENUM and 1 data bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: raw data 1 byte:
Info:GEN:CHANNEL_Set channel 3 has changed to 1 (flags 0)
Info:MQTT:Channel has changed! Publishing 1 to channel 3
Info:MQTT:Publishing val 1 to bksensor_WL00/3/get retain=0
Info:MAIN:Time 16, idle 169547/s, free 72416, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic bksensor_WL00/3/get
Info:MQTT:Publishing val FunkLoch to bksensor_WL00/ssid retain=0
Info:MAIN:Time 17, idle 175427/s, free 72416, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38
I don't understand why it is "ignoring" the state, claiming that there was no change, when it actually has changed a few seconds ago.
0 means wet, and 1 means dry.
I have tried different settings, including enabling/disabling Flags 10 and 19. Adding "tuyaMcu_setBaudRate 115200" to startup command line has not helped but lead to sensor's inactivity.
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: processing dpId 1, dataType 4-DP_TYPE_ENUM and 1 data bytes
Info:TuyaMCU:TuyaMCU_V0_ParseRealTimeWithRecordStorage: raw data 1 byte:
Info:GEN:No change in channel 1 (still set to 0) - ignoring
means that the channel 1 already had value 0 inside, most likely because it's a default channel value, hm...
We could try to fix it in code (make it always report MCU values), but you can also do one of the following workarounds:
- in Config->Startup, set startup value of channel 1 to 99 or something else unique
- in Config->Startup, make channel 1 remember its value between reboots (but it will slowly wear out flash)
I may look into it more, but you have a good point. Firmware is trying to optimize the number of publishes with the logic "don't send if there is no change", but the value 0 is default and there actually was a change...
I may look into it from the firmware side as well. Add some 64 bit integer to track whether the channels were ever set before and if not, then force-publish the change...
Both settings:
- channel 1 startup value other than 0 or 1, or
- channel 1 startup value -1
result in sucessful mqtt publish of value "0" after water probes have been bridged.
- My observation: after wakeup from sleep it takes 15 seconds for MCU to report new state, and if probes are repeatedly bridged/unbridged at the time of report, wifi connection is kept and status changes are reported instantly.
This is amazing, I really love how there is a workaround for almost everything!! Thanks a lot! I will tear down and flash other sensors too and post results or make YT videos about it!
I am curious, do you have the same problem with your W06 device but with CB3S module?
As for your idea to look into firmware change, do you need any of my device data? I have backed up read result of original firmware, and can send it to you if it helps!?
Anyone who happens to have the same device (W06 with CBU module), please try these settings to get this device to work:
1. Desolder CBU module from motherboard
2. Flash OpenBK and setup wifi, names and mqtt
3. Set startup command:
backlog startDriver tuyaMCU; startDriver tmSensor; linkTuyaMCUOutputToChannel 1 val 1; setChannelType 1 ReadOnly; linkTuyaMCUOutputToChannel 3 val 3; setChannelType 3 ReadOnly;
4. Set flags 10 and 19 (it is optional, for me it worked even without setting the flags)
5. Go to device's web interface (not webapp!) --> Config --> Configure Startup --> here set a value other than 0 or 1 to Channel 1, e.g. 99
6. Do Home Assistant discovery
7. Solder CBU back to motherboard
8. Enjoy!
Hi.
I bought another revision of the water leakage sensor.
It contains cb3s and um8005(tuya?) chips.
I flashed cb3s with the latest firmware OpenBK.
It works, but tuyaMCU needs baud rate 115200. I used startup command "tuyaMcu_setBaudRate 115200"
But there is a problem. Often the first time we get wet, the mqtt doesn't send a message. If you immediately dry it and wet it again, the messages come normally. After a deep sleep, the first message can again be missed.
in the stock firmware all messages arrive correctly
Hi have 3 exact devices (have opened them up and PCB and chip layout are identical). I have been trying for days now to get these to work without success and looking for some assistance. I have managed to cloud cut and load OpenBK on them (well one has kickstarter-esphome...but that another story). I have tried using the template found in the OpenBK device list data base for Tuya W06 Water Sensor which seems to load just fine but I do not see any change in the pin configuration afterwards...should I? I have tried adding the startup command as you indicated and that does seem to change anything. Can you give a walk down of the process you did to config or anything that I should check or do? Thanks for help you can give. fyi, I am a long time Tasmota user so some things in OpenBK are famaliar some things not so much.
I think you need to manually go to the template source topic and find autoexec.bat there and copy it.
Autoexec.bat tutorial:
https://www.youtube.com/watch?v=kXi8S12tmC8 Autoexec.bat is not copied automatically right now to LittleFS, so you may be missing it.
yes that was the missing step that I need to have it work! Thank you. The only issue I am experiencing now is I have OpenHab configured to interact with this device via MQTT (much like many other Tasmota Tuya devices I have) as a contact device (read only) which works fine but it seems to not be very reliable. If I short the contacts when the device is not in sleep Openhab will receive the topic just fine and update the devices state but if the device is in sleep mode nothing happens...it like the device publishes the topic before it connects to the network again thus does not get sent anywhere. Not sure if there is any settings regarding this in Openbeken or not....
So what kind of autoexec.bat do you have currently? The reporting mechanism is designed in such a way that it waits for MQTT connection first and then proceeds to report the data.
Hi everyone,
since some days i am testing some similary devices, sold by medion with label ambiano, SWDA04 (door window) and SWW04U (water).
PCB's are identical, some simple components are different, door/window has hallsensor and water transistor.
Flashing is as usual, configuring can be done by pressing button and insert batteries (then led is blinking fast).
Before flashing i catched communication between tuyamcu and cbu-modul with tuyaexplorer:
//S 09.01.2025 15:38:23 WiFi sent:
55AA0001000000
//R 09.01.2025 15:38:23 WiFi received:
55AA000100247B2270223A2267696271717A33356872776D6F6D6E66222C2276223A22312E302E32227D05
//R 09.01.2025 15:38:24 WiFi received:
55AA0002000001
//S 09.01.2025 15:38:25 WiFi sent:
55AA000200010204 <--------------------------- missing in openbeken
//R 09.01.2025 15:38:28 WiFi received:
55AA0002000001
//S 09.01.2025 15:38:28 WiFi sent:
55AA000200010305
//S 09.01.2025 15:38:32 WiFi sent:
55AA000200010406
//R 09.01.2025 15:38:32 WiFi received:
55AA0002000001
//R 09.01.2025 15:38:32 WiFi received:
55AA001000010010
//R 09.01.2025 15:38:32 WiFi received:
55AA0005000501010001010D
//R 09.01.2025 15:38:32 WiFi received:
55AA00050008020200040000006478
//S 09.01.2025 15:38:34 WiFi sent:
55AA00100002010012
//S 09.01.2025 15:38:34 WiFi sent:
55AA000500010005
//S 09.01.2025 15:38:34 WiFi sent:
55AA000500010005
//R 09.01.2025 15:38:39 WiFi received:
55AA001000010010
//S 09.01.2025 15:38:39 WiFi sent:
55AA00100002010012
Is it ok that in openbeken the line with <---------- is missing ?
With openbeken exists the problem, that often the modules are not responsable to magnetic/water, cbu is not powered from tuyamcu.
The reason is that if modules when powered up or wakeup sometimes there is a delay of exactly 17/18sec between product-query and mcuconf.
cbu is powered down by tuyamcu too fast to get dpcache and publish this and after this uncomplete communication it's impossible to wakeup tuyamcu for 50 min.
Here is the log:
//S 11.01.2025 21:50:26 WiFi sent:
55AA0001000000
//R 11.01.2025 21:50:27 WiFi received:
55AA000100247B2270223A2267696271717A33356872776D6F6D6E66222C2276223A22312E302E32227D05
//S 11.01.2025 21:50:44 WiFi sent:
55AA000200010305
//R 11.01.2025 21:50:45 WiFi received:
55AA0002000001
//R 11.01.2025 21:50:47 WiFi received:
55AA0002000001
//S 11.01.2025 21:50:48 WiFi sent:
55AA000200010406
//R 11.01.2025 21:50:51 WiFi received:
55AA001000010010
//S 11.01.2025 21:50:52 WiFi sent:
55AA00100002010012
Hi again,
i found the solution for things described in last post. Only the first result of obtainDpCache (everytime correctly by tuyamcu delivered) is not published, ALL other are published correctly and CBU is switched on EVERYTIME if door/water input changed. The howto and result can be seen in attachment: Productquery is moved to autoexec.bat, mcuconf (...0204) is inserted to TuyaMCU_RunStateMachine_BatteryPowered and g_tuyaNextRequestDelay are minimized. It's only and perfect working this way. The remaining problem cannot solved with startup value or anything posted here. Hints and ideas very welcome...
The discussion revolves around the Tuya WiFi door/window sensor DS06, focusing on its power consumption, communication protocols, and firmware issues. Users share experiences with various battery-operated sensors, including those using CR2032 and CR1632 batteries, and discuss the impact of temperature on battery performance. The conversation highlights the TuyaMCU protocol, firmware flashing challenges, and the importance of proper configuration for reliable operation. Users also explore alternative communication methods like Zigbee and Bluetooth, and share insights on deep sleep modes to enhance battery life. Several users report successful firmware updates and configurations, while others seek assistance with specific issues related to their devices. Summary generated by the language model.
![[ZIGBEE] 20A Zigbee socket with energy metering (Tuya TS011F_plug_3)](https://obrazki.elektroda.pl/1000454900_1749493372_thumb.jpg)
I've missed that part, my apologies.
From the Serial Port Protocol of Wi-Fi for Low Power Devices in the flowchart below section "Report the real-time status" it is seen, that values are reported by MCU to CB3S after CB3S tells the MCU, that connected to network. In my attached SniffUART recording above this behavior is seen. For this I would guess, that in case of closing the contact, the "Report Network Status" message is missing?
