Wifi Smoke Alarm Nedis/LSC TYWE3S

[RSV-Tuono]

Hello all,
I have opened this new thread because I have not found a suitable solution on the web. All solutions came to nothing.
This is about a LSC Smoke Alarm (similar to Nedis WIFIDS20WT) with TYWE3S.

It was successfully flashed with Tasmota and Tasmotizer using a jig.

• Program Version 13.1.0.3(sensors)
• Build Date & Time 2023-09-23T11:26:37
• Core/SDK Version 2_7_4_9/2.2.2-dev(38a443e)

The following template was applied:
Nedis Smoke Alarm Template

Unfortunately, the status remains "unknown" in Homeassistant because no usable MQTT messages are received. I can filter the following messages via the MQTT Explorer:
cmnd/RM-01/STATUS => changes from 11 to 1

Can someone perhaps help me to implement the smoke detectors in Homeassistant via Tasmota?

Thanks in advance

[barbudor]

Your LSC (or it's similar cousin Nedis) are not known in the Tasmota Templates repository, so if someone have ever succeeded to get Tasmota running, he didn't bother to share.

As you may have noticed, configuring a Tuya based device is more than just applying a template.
There are a few TuyaMCU command to use
And for all 3 models of Tuya smoke detector listed on the template repository there are a set of rules which are all different between the different devices

So that's not going to happen by magic

You need to provide more details, including more logs showing the received tuya messages.

[RSV-Tuono]

Thank you @barbudor for your comment.
I use TASMOTA-TUYA HELPER to get some more information:

18:22:39.422 SRC: Rule
18:22:39.424 CMD: Grp 0, Cmd 'PUBLISH', Idx 2, Len 217, Pld -99, Data 'homeassistant/binary_sensor/{mac_address}_test/config {"name":"Fire Alarm Test","state_topic":"stat/RM-01/TEST","icon":"mdi:bell-alert","unique_id":"{mac_address}_test","device":{"connections":[["mac","{mac_address}"]]}}'
18:22:39.431 MQT: homeassistant/binary_sensor/{mac_address}_test/config = {"name":"Fire Alarm Test","state_topic":"stat/RM-01/TEST","icon":"mdi:bell-alert","unique_id":"{mac_address}_test","device":{"connections":[["mac","{mac_address}"]]}} (retained)
18:22:39.456 RUL: SYSTEM#BOOT performs "publish2 homeassistant/binary_sensor/{mac_address}_mute/config {"name":"Fire Alarm Mute","state_topic":"stat/RM-01/MUTE","icon":"mdi:bell-sleep","unique_id":"{mac_address}_mute","device":{"connections":[["mac","{mac_address}"]]}}"
18:22:39.458 SRC: Rule
18:22:39.460 CMD: Grp 0, Cmd 'PUBLISH', Idx 2, Len 217, Pld -99, Data 'homeassistant/binary_sensor/{mac_address}_mute/config {"name":"Fire Alarm Mute","state_topic":"stat/RM-01/MUTE","icon":"mdi:bell-sleep","unique_id":"{mac_address}_mute","device":{"connections":[["mac","{mac_address}"]]}}'
18:22:39.467 MQT: homeassistant/binary_sensor/{mac_address}_mute/config = {"name":"Fire Alarm Mute","state_topic":"stat/RM-01/MUTE","icon":"mdi:bell-sleep","unique_id":"{mac_address}_mute","device":{"connections":[["mac","{mac_address}"]]}} (retained)
18:22:39.495 RUL: SYSTEM#BOOT performs "publish2 homeassistant/binary_sensor/{mac_address}_battery/config {"name":"Fire Alarm Battery","state_topic":"stat/RM-01/BATTERY","device_class":"battery","unique_id":"{mac_address}_battery","device":{"connections":[["mac","{mac_address}"]]}}"
18:22:39.498 SRC: Rule
18:22:39.501 CMD: Grp 0, Cmd 'PUBLISH', Idx 2, Len 230, Pld -99, Data 'homeassistant/binary_sensor/{mac_address}_battery/config {"name":"Fire Alarm Battery","state_topic":"stat/RM-01/BATTERY","device_class":"battery","unique_id":"{mac_address}_battery","device":{"connections":[["mac","{mac_address}"]]}}'
18:22:39.508 MQT: homeassistant/binary_sensor/{mac_address}_battery/config = {"name":"Fire Alarm Battery","state_topic":"stat/RM-01/BATTERY","device_class":"battery","unique_id":"{mac_address}_battery","device":{"connections":[["mac","{mac_address}"]]}} (retained)
18:22:40.124 TYA: Set WiFi LED 4 (0)
18:22:40.127 TYA: Send "55aa000200010406"
18:22:40.224 SRC: MQTT
18:22:40.227 CMD: Grp 0, Cmd 'STATUS', Idx 1, Len 1, Pld 1, Data '1'
18:22:40.234 MQT: stat/RM-01/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/tasmota-DE.bin","RestartReason":"External System","Uptime":"0T00:00:06","StartupUTC":"2023-10-04T17:22:34","Sleep":50,"CfgHolder":4617,"BootCount":50,"BCResetTime":"2023-09-23T17:47:09","SaveCount":78,"SaveAddress":"FB000"}}
18:22:40.293 SRC: MQTT
18:22:40.296 CMD: Grp 0, Cmd 'STATUS', Idx 1, Len 2, Pld 11, Data '11'
18:22:40.304 MQT: stat/RM-01/STATUS11 = {"StatusSTS":{"Time":"2023-10-04T18:22:40","Uptime":"0T00:00:06","UptimeSec":6,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":50,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"FRITZ!FM","BSSId":"3C:A6:2F:A6:66:17","Channel":1,"Mode":"11n","RSSI":86,"Signal":-57,"LinkCount":1,"Downtime":"0T00:00:03"}}}
18:22:40.362 SRC: MQTT
18:22:40.365 CMD: Grp 0, Cmd 'STATE', Idx 1, Len 0, Pld -99, Data ''
18:22:40.371 MQT: stat/RM-01/RESULT = {"Time":"2023-10-04T18:22:40","Uptime":"0T00:00:06","UptimeSec":6,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":54,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"FRITZ!FM","BSSId":"3C:A6:2F:A6:66:17","Channel":1,"Mode":"11n","RSSI":86,"Signal":-57,"LinkCount":1,"Downtime":"0T00:00:03"}}
18:22:41.391 HTP: Console
18:22:43.133 MQT: tele/RM-01/STATE = {"Time":"2023-10-04T18:22:43","Uptime":"0T00:00:09","UptimeSec":9,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"FRITZ!FM","BSSId":"3C:A6:2F:A6:66:17","Channel":1,"Mode":"11n","RSSI":84,"Signal":-58,"LinkCount":1,"Downtime":"0T00:00:03"}}
18:22:44.154 APP: Boot Count 51
18:22:44.804 CFG: Saved to flash at FA, Count 79, Bytes 4096
18:22:45.475 CMD: Backlog Weblog 4; TuyaSend8;
18:22:45.477 SRC: WebConsole from {ip_adress}
18:22:45.479 CMD: Grp 0, Cmd 'BACKLOG', Idx 1, Len 20, Pld -99, Data 'Weblog 4; TuyaSend8;'
18:22:45.554 SRC: Backlog
18:22:45.557 CMD: Grp 0, Cmd 'WEBLOG', Idx 1, Len 1, Pld 4, Data '4'
18:22:45.562 MQT: stat/RM-01/RESULT = {"WebLog":4}
18:22:45.764 SRC: Backlog
18:22:45.766 CMD: Grp 0, Cmd 'TUYASEND', Idx 8, Len 0, Pld -99, Data ''
18:22:45.769 TYA: Read MCU state
18:22:45.772 TYA: Send "55aa0001000000"
18:22:45.777 MQT: stat/RM-01/RESULT = {"TuyaSend":"Done"}
18:22:45.839 CMD: TuyaMCU;
18:22:45.841 SRC: WebConsole from {ip_adress}
18:22:45.843 CMD: Grp 0, Cmd 'TUYAMCU', Idx 1, Len 1, Pld -99, Data ';'
18:22:45.847 TYA: TuyaMcu Invalid function id=0
18:22:45.852 MQT: stat/RM-01/RESULT = {"TuyaMCU":[{"fnId":11,"dpId":1},{"fnId":51,"dpId":51}]}
18:22:48.155 MQT: tasmota/discovery/{mac_address}/config = {"ip":"{ip_adress}","dn":"RM-01","fn":["RM-01",null,null,null,null,null,null,null],"hn":"RM-01","mac":"{mac_address}","md":"Nedis WIFIDS10WT","ty":1,"if":0,"ofln":"Offline","onln":"Online","state":["OFF","ON","TOGGLE","HOLD"],"sw":"13.1.0.3","t":"RM-01","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"bat":0,"dslp":0,"sho":[],"sht":[],"ver":1} (retained)
18:22:48.164 MQT: tasmota/discovery/{mac_address}/sensors = {"sn":{"Time":"2023-10-04T18:22:48"},"ver":1} (retained)
18:22:58.011 WIF: Checking connection...```

.. so far I found out that there are some TUYA commands:
18:22:40.124 TYA: Set WiFi LED 4 (0)
18:22:40.127 TYA: Send "55aa000200010406"
18:22:45.769 TYA: Read MCU state
18:22:45.772 TYA: Send "55aa0001000000
18:22:45.847 TYA: TuyaMcu Invalid function id=0

Are these information helpful?
regards

[sfromis]

For readable logs, better wrap the block in triple backtick before/after, instead of single.

[barbudor]

I don't see what I was asking for : the TuyaReceived messages and the MCU Product ID
Also may be worth enabling WebLog 3 for a few additional messages

Also all 3 existing templates uses that configuration or a part of it:

Backlog TuyaMCU 11,4; TuyaMCU 51,51

so probably worth trying it

[RSV-Tuono]

Backlog TuyaMCU 11,4; TuyaMCU 51,51
also
WebLog 4
but no further information from TUYA

[RSV-Tuono]

Maybe these pics are also needed?


Thanks in advance

[barbudor]

What you could check is if the ESP TX and RX are going to the MCU (that rectangular chip on the left
Just to be sure they did decided to use different GPIO just to bother us

[RSV-Tuono]

... think I need a little bit time for it ;):
Selecting the Tuya MCU (54) module type will select the default and most common GPIO ports for Tuya Tx and Tuya Rx (GPIO 1 and 3 respectively), however it has been reported this can change for some devices. The best way is to follow the tracks on the PCB between the MCU and main chip, mapping this back to GPIO's, and some trial and error.

[RSV-Tuono]

Ok, for me it´s impossible to follow the tracks on pcb because of an isolation layer on the surface.
Is there another solution to find out the correct GPIO for RX TX?
I also tried to change the GPIO in TASMOTA configuration template to get some data in console, but with no success

[sfromis]

Devices infested with a TuyaMCU typically have Tuya TX/RX on either gpio 1/3 (standard tx/rx) or gpio 15/13, with a few exceptions. Setting baud rate may also be important, SetOption97.

[RSV-Tuono]

What I figured out (with a resistance meter) is following:

but it doesn´t have any effect when I change it in configuration ...
Will flash the device to clean install again, also I will test the 15/13 and report. The baud rate is set to 115200 with SetOption97 1

[RSV-Tuono]

... here we go:

00:00:00.002 HDW: ESP8266EX
00:00:00.050 CFG: Loaded from flash at FA, Count 18
00:00:00.056 QPC: Count 2
00:00:00.074 SNS: Hardware Serial
00:00:00.111 Project tasmota - Tasmota Version 13.1.0(tasmota)-2_7_4_9(2023-08-15T07:58:36)
00:00:00.550 WIF: Connecting to AP1 FRITZ!FM Channel 11 BSSId {mac_address} in mode 11n as tasmota-330706-1798...
00:00:01.803 WIF: Connected
00:00:02.007 HTP: Web server active on tasmota-330706-1798 with IP address {ip_address}
08:39:36.017 RSL: INFO1 = {"Info1":{"Module":"Tuya MCU","Version":"13.1.0(tasmota)","FallbackTopic":"cmnd/DVES_330706_fb/","GroupTopic":"cmnd/tasmotas/"}}
08:39:36.020 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-330706-1798","IPAddress":"{ip_address}"}}
08:39:36.021 RSL: INFO3 = {"Info3":{"RestartReason":"External System","BootCount":11}}
08:39:36.023 RSL: RESULT = {"POWER":"OFF"}
08:39:36.025 RSL: POWER = OFF
08:39:36.111 TYA: MCU Product ID: {"p":"cjlutkuuvxnie17o","v":"1.0.0"}
08:39:39.428 QPC: Reset
08:39:40.420 RSL: STATE = {"Time":"2023-10-08T08:39:40","Uptime":"0T00:00:08","UptimeSec":8,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"POWER":"OFF","Wifi":{"AP":1,"SSId":"FRITZ!FM","BSSId":"{mac_address}","Channel":11,"Mode":"11n","RSSI":54,"Signal":-73,"LinkCount":1,"Downtime":"0T00:00:03"}}
08:40:04.151 CMD: Backlog Weblog 4; TuyaSend8;
08:40:04.225 RSL: RESULT = {"WebLog":4}
08:40:04.430 SRC: Backlog
08:40:04.432 CMD: Grp 0, Cmd 'TUYASEND', Idx 8, Len 0, Pld -99, Data ''
08:40:04.435 TYA: Read MCU state
08:40:04.443 TYA: Send "55aa0001000000"
08:40:04.445 RSL: RESULT = {"TuyaSend":"Done"}
08:40:04.548 CFG: Saved to flash at F8, Count 20, Bytes 4096
08:40:04.558 CMD: TuyaMCU;
08:40:04.560 SRC: WebConsole from 192.168.178.21
08:40:04.562 CMD: Grp 0, Cmd 'TUYAMCU', Idx 1, Len 1, Pld -99, Data ';'
08:40:04.565 TYA: TuyaMcu Invalid function id=0
08:40:04.567 RSL: RESULT = {"TuyaMCU":[{"fnId":11,"dpId":1}]}
08:40:04.643 {"TuyaReceived":{"Data":"55AA000100247B2270223A22636A6C75746B757576786E696531376F222C2276223A22312E302E30227D17","Cmnd":1,"CmndData":"7B2270223A22636A6C75746B757576786E696531376F222C2276223A22312E302E30227D"}}
08:40:04.645 TYA: MCU Product ID: {"p":"cjlutkuuvxnie17o","v":"1.0.0"}
08:40:04.653 TYA: Send "55aa0002000001"
08:40:04.689 {"TuyaReceived":{"Data":"55AA0002000001","Cmnd":2}}
08:40:04.690 TYA: RX MCU configuration Mode=0
08:40:04.692 TYA: Read MCU state
08:40:04.700 TYA: Send "55aa0008000007"
08:40:04.883 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:05.898 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:06.407 TYA: Send "55aa00000000ff"
08:40:06.451 {"TuyaReceived":{"Data":"55AA000000010101","Cmnd":0,"CmndData":"01"}}
08:40:06.453 TYA: Heartbeat
08:40:06.913 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:07.928 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:08.943 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:09.956 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:10.973 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:11.990 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:13.006 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:14.020 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:14.794 WIF: Checking connection...
08:40:15.035 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:16.051 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:17.112 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:17.425 TYA: Send "55aa00000000ff"
08:40:17.463 {"TuyaReceived":{"Data":"55AA000000010101","Cmnd":0,"CmndData":"01"}}
08:40:17.466 TYA: Heartbeat
08:40:18.082 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:19.097 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:20.113 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:21.128 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:22.144 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:23.159 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:24.175 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:25.190 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:26.206 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:27.220 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:28.234 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:28.392 TYA: Send "55aa00000000ff"
08:40:28.434 {"TuyaReceived":{"Data":"55AA000000010101","Cmnd":0,"CmndData":"01"}}
08:40:28.437 TYA: Heartbeat
08:40:29.250 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:30.265 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:31.279 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:31.449 TYA: Send "55aa001c000801170a0808281f07a3"
08:40:32.294 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:33.310 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:33.411 WIF: Sending Gratuitous ARP
08:40:34.325 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:34.804 WIF: Checking connection...
08:40:35.339 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:36.353 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:37.369 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:38.383 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:39.395 TYA: Send "55aa00000000ff"
08:40:39.399 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:39.435 {"TuyaReceived":{"Data":"55AA000000010101","Cmnd":0,"CmndData":"01"}}
08:40:39.437 TYA: Heartbeat
08:40:40.414 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:41.430 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:42.444 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:43.459 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}
08:40:44.474 {"TuyaReceived":{"Data":"55AA0007000006","Cmnd":7}}

Don´t know what happens, but still got the information that @barbudor was searching for (I hope)
Made a clean install, only changed to TUYAMCA without putting some rules or options into console :)

[barbudor]

So now it looks like you aer able to receive from the TuyaMCU
I was expecting to see simalar values to those used with the others smoke detector in the template repository but I don't see that

May be you need to do Backlog TuyaMCU 11,4; TuyaMCU 51,51 to see those values

Or may be try to trigger the alarm to see if the data in {"Data":"55AA0007000006","Cmnd":7}} change
Cmnd 7 is a status report so it may be possible that some of the bytes after the 7 changes to some other values when the alarm triggers.

[RSV-Tuono]

Thank you for your support, @barbudor and sorry for my late response. But I can only check the discussions after work.
What I found out was that 9600 bps is the correct setting SetOption97 0 to get data from TUYA.

I made a clean install with "tasmota-battery.bin" because I read in another disussion supported by you that it is a better solution for energy saving. Thought it is a good idea in advance if I will get this TUYA stuff work.
... result was, that the Data ID changes from
{"Data":"55AA0007000006","Cmnd":7}} to {"Data":"55AA0002000001","Cmnd":2}}````

Also I activated MQTT to get the information in "MQTT Exxplorer"
I followed you suggestion to trigger the alarm (aftet two cigarettes in my homeoffice in a "non-Smoking" area where smoking is prohibited by wife´s law!!!) and got following messages:

09.10.2023 19:03:37(-0 seconds){"TuyaReceived":{"Data":"55AA000500050B050001001A","Cmnd":5,"CmndData":"0B05000100"}}
09.10.2023 19:03:37(-0 seconds){"TuyaReceived":{"Data":"55AA000500050E040001021E","Cmnd":5,"CmndData":"0E04000102"}}
09.10.2023 19:03:37(-0.04 seconds){"TuyaReceived":{"Data":"55AA00050005010400010110","Cmnd":5,"CmndData":"0104000101"}}
09.10.2023 19:03:37(-0.21 seconds){"TuyaReceived":{"Data":"55AA0002000001","Cmnd":2}}
09.10.2023 19:03:37(-0.05 seconds){"TuyaReceived":{"Data":"55AA000100247B2270223A22636A6C75746B757576786E696531376F222C2276223A22312E302E30227D17","Cmnd":1,"CmndData":"7B2270223A22636A6C75746B757576786E696531376F222C2276223A22312E302E30227D"}}
09.10.2023 19:03:18(-18.95 seconds){"TuyaReceived":{"Data":"55AA000500050B050001001A","Cmnd":5,"CmndData":"0B05000100"}}
09.10.2023 19:03:18(-0 seconds){"TuyaReceived":{"Data":"55AA000500050E040001021E","Cmnd":5,"CmndData":"0E04000102"}}
09.10.2023 19:03:18(-0.08 seconds){"TuyaReceived":{"Data":"55AA0005000501040001000F","Cmnd":5,"CmndData":"0104000100"}}
09.10.2023 19:03:17(-0.81 seconds){"TuyaReceived":{"Data":"55AA0002000001","Cmnd":2}}
09.10.2023 19:03:17(-0.12 seconds){"TuyaReceived":{"Data":"55AA000100247B2270223A22636A6C75746B757576786E696531376F222C2276223A22312E302E30227D17","Cmnd":1,"CmndData":"7B2270223A22636A6C75746B757576786E696531376F222C2276223A22312E302E30227D"}}

I think that
09.10.2023 19:03:18(-0.08 seconds){"TuyaReceived":{"Data":"55AA0005000501040001000F","Cmnd":5,"CmndData":"0104000100"}} is command "FIRE-ALARM-ON"

and this is command
09.10.2023 19:03:37(-0.04 seconds){"TuyaReceived":{"Data":"55AA00050005010400010110","Cmnd":5,"CmndData":"0104000101"}}
is "FIRE_ALARM_OFF"

What do you think?

[barbudor]

I wasn't in the room with you, so if you got the horn/siren while receiving those messages, it's probably the good ones
Although Tuya doc say that command 5 is about AP pairing mode
https://developer.tuya.com/en/docs/iot/tuya-cloud-universal-serial-port-access-protocol?id=K9hhi0xxtn9cb#title-11-Reset%20Wi-Fi%20and%20select%20pairing%20mode

There is also something totally non standard with your devices: Messages received from the MCU are supposed to start with 55AA03, not 55AA00

So now it's up to you to add some rule to manage that and send specific messages such as

Rule1
  on TuyaReceived#Data=55AA0005000501040001000Fdo Publish stat/%topic%/FIRE ON endon
  on TuyaReceived#Data=55AA00050005010400010110do Publish stat/%topic%/FIRE OFF endon
Rule1 1

And setup your home automation as needed

[RSV-Tuono]

OK, got it working: Thank you @barbudor !

Manual:
Flash TYWE3s with tasmota-lite.bin !important

SetOption97 0
TuyaMCU 51,51
Backlog SetOption1 1; SetOption65 1

Rule1
ON TuyaReceived#Data=55AA0005000501040001000F DO publish stat/%topic%/FIRE ON ENDON
ON TuyaReceived#Data=55AA00050005010400010110 DO publish stat/%topic%/FIRE OFF ENDON
ON TuyaReceived#CmndData=0E04000102 DO publish stat/%topic%/BATT OFF ENDON
ON TuyaReceived#CmndData=0E04000100 DO publish stat/%topic%/BATT ON ENDON

Rule1 1

Rule2
ON system#boot do publish homeassistant/binary_sensor/%macaddr%_fire/config {"name":"Fire Alarm","state_topic":"stat/%topic%/FIRE","device_class":"smoke","unique_id":"%macaddr%_fire","device":{"connections":[["mac","%macaddr%"]]}} ENDON
ON system#boot do publish homeassistant/binary_sensor/%macaddr%_battery/config {"name":"Fire Alarm Battery","state_topic":"stat/%topic%/BATT","device_class":"battery","unique_id":"%macaddr%_battery","device":{"connections":[["mac","%macaddr%"]]}} ENDON
ON system#boot do publish homeassistant/sensor/%macaddr%_battery_voltage/config {"name":"Fire Alarm Batt Volt","state_topic":"stat/%topic%/STATUS11","value_template": "{{ value_json.StatusSTS.Vcc | round (2)}}","unit_of_measurement": "V","device_class":"battery","unique_id":"%macaddr%_battery_voltage","device":{"connections":[["mac","%macaddr%"]]}} ENDON

Rule2 1

SetOption66 1

edit 27-10-23 : included Battery Voltage (thanks to @Wolfgang-Gi )
(del: Now it would be nice to have the "Battery State", then it´s perfect)

[Wolfgang-Gi]

Hello RSV-Tuono,
I have bought the same device and I managed to see the alarm in HA with your code.
Thanks.
I am also interested in seeing the bat status - please go ahead
BR

[RSV-Tuono]

@Wolfgang-Gi

Here we go: Try this to get the state, but unfortunately not in percent:

Rule1
ON TuyaReceived#Data=55AA0005000501040001000F DO publish stat/%topic%/FIRE ON ENDON
ON TuyaReceived#Data=55AA00050005010400010110 DO publish stat/%topic%/FIRE OFF ENDON
ON TuyaReceived#CmndData=0E04000102 DO publish stat/%topic%/BATT OFF ENDON
ON TuyaReceived#CmndData=0E04000100 DO publish stat/%topic%/BATT ON ENDON
Rule1 1

For Homeassistant :

Rule2
ON system#boot do publish homeassistant/binary_sensor/%macaddr%_fire/config {"name":"Fire Alarm","state_topic":"stat/%topic%/FIRE","device_class":"smoke","unique_id":"%macaddr%_fire","device":{"connections":[["mac","%macaddr%"]]}} ENDON
ON system#boot do publish homeassistant/binary_sensor/%macaddr%_battery/config {"name":"Fire Alarm Battery","state_topic":"stat/%topic%/BATT","device_class":"battery","unique_id":"%macaddr%_battery","device":{"connections":[["mac","%macaddr%"]]}} ENDON
Rule2 1

As I found out: these Smoke Alarms do not send any HIGH MED LOW information or any percentage.
Hope that if battery is low that it will be shown as LOW
Maybe there is someone outsite who has a better idea ?!?

regards
Tuono

[Wolfgang-Gi]

Good Morning.
How does that look?

Rule2
ON system#boot do publish homeassistant/binary_sensor/%macaddr%_fire/config {"name":"Fire Alarm","state_topic":"stat/%topic%/FIRE","device_class":"smoke","unique_id":"%macaddr%_fire","device":{"connections":[["mac","%macaddr%"]]}} ENDON
ON system#boot do publish homeassistant/binary_sensor/%macaddr%_battery/config {"name":"Fire Alarm Battery","state_topic":"stat/%topic%/BATT","device_class":"battery","unique_id":"%macaddr%_battery","device":{"connections":[["mac","%macaddr%"]]}} ENDON
ON system#boot do publish homeassistant/sensor/%macaddr%_battery_voltage/config {"name":"Fire Alarm Batt Volt","state_topic":"stat/%topic%/STATUS11","value_template": "{{ value_json.StatusSTS.Vcc | round (2)}}","unit_of_measurement": "V","device_class":"battery","unique_id":"%macaddr%_battery_voltage","device":{"connections":[["mac","%macaddr%"]]}} ENDON
Rule2 1

BR
Wolfgang

[RSV-Tuono]

You made my day 👍
It´s working only with tasmota-lite.bin 13.2
I´ve been on tasmota-DE.bin 13.1

Thank you very much @Wolfgang-Gi for sharing your knowledge!!!

A - Do you know how to handle the template, so that the battery symbol shows white when above 3,0V and red when under 2,7V?
B - Do you know if it´s possible to send data to TuyaMCU? Then it would be possible to send an alarm to other SmokeSensors

[Wolfgang-Gi]

Hi,
A - I have no clue
B - I think ESP is in deep sleep, it can't receive any Data

Do you know how offen the device send its status, wakes it self from sleep?

[ChrisCphDk]

Followed the steps the two of you detailed, for my Nedis Smoke Alarm (wifids29wt):

1. flashed with tasmota-lite
2. Went to web configuration, and pasted the template from https://templates.blakadder.com/nedis_WIFIDS10WT.html
3. entered the commands and set up the 2 rules through the web-console. NOTE: I did not fill in all the rule lines from step 2's template link, only the lines you posted here.

I'm getting "Unknown" for the fire alarm, and the battery (although the voltage shows up fine) in HA (where I set up MQTT and entered the user and password in the Tasmoto web configuration):

This is my first Tasmoto flashing, so I might have overlooked something the rest of you take for granted in the flashing, but as I see the voltage show up fine, I'm wondering if there is something in the rules that may be different for my version?
Any help would be much appreciated.

[RSV-Tuono]

Hi Chris,
did you restart Homeassistant? Then you need to activate the alarm manually by pushing the button.
Normally, if you follow all the steps from the manual above, it should work ...

To check my MQTT connections and messages I use https://www.mqtt-explorer.com.
If you do a test on the fire alarm, you will get a message like:
192.168.HA.IPadress ►tele►sensor name►
{ "TuyaReceived": { OLD: "Data": "55AA000500050E040001021E", NEW: "Data": "55AA000500050B050001001A", "Cmnd": 5, OLD: "CmndData": "0E04000102" NEW "CmndData": "0B05000100" } }
if you see that message, everythin is transmitted OK, then the mistake is in on HOMEASSISTANT site and you need to check the entities

reg

[ChrisCphDk]

@RSV-Tuono Thank you for replying.
I had it connected using the 3D printed jig with pogo-pins.
When I disconnected it from the jig, and instead inserted the battery (still left the speaker disconnected), then I now see:

I have to wake up the device every now and then to get updates in the console, by triple pressing the button.
If I then single press the button, and constantly refresh HA's UI it shows: "Detected" for a split second, and the "Logbook" under the device shows that it first detected smoke, and that it then clears. I assume this is the behavior we want.
I will try to do a test with real smoke when it will not irritate my better half.

Thank you so much for taking the time to answer, it was the push I needed even if it was something as simple as removing the jig, and using the battery.
Much appreciated

UPDATE: Did a test in our fireplace, and some pine branches for the smoke, and it works very well!
Now I just need to update the other two alarms

[dany547]

I have a question. I managed to install Tasmota Lite on the device but after its connected to Home Assistant, the device enters DeepSleep and disconnects from the network, thus making the entity in HASS Unavailable (after HASS is restarted) and to refresh the status basically i have to press the button on the smoke detector. Is there a way to wake the ESP chip once every 3 days or so? So it can connect to WIFI and report new data including its battery life?

[barbudor]

This may answer your question: #16031 (reply in thread)

[dany547]

thanks for the replay. Will this affect battery life? Because from what ive read device will report its status proactively?

[barbudor]

This affets how HA interprets the status of the device that enters DeepSleep, thus not marking it as Unavailable
It's only HA side, no impact on Tasmota

[Mo3he]

You can use these rules as they will publish with retain so the fire and battery sensors in HA dont ever go offline.

Rule1
ON TuyaReceived#Data=55AA0005000501040001000F DO publish2 stat/%topic%/FIRE ON ENDON
ON TuyaReceived#Data=55AA00050005010400010110 DO publish2 stat/%topic%/FIRE OFF ENDON
ON TuyaReceived#CmndData=0E04000102 DO publish2 stat/%topic%/BATT OFF ENDON
ON TuyaReceived#CmndData=0E04000100 DO publish2 stat/%topic%/BATT ON ENDON

Rule1 1

Rule2
ON system#boot do publish2 homeassistant/binary_sensor/%macaddr%_fire/config {"name":"Fire Alarm","state_topic":"stat/%topic%/FIRE","device_class":"smoke","unique_id":"%macaddr%_fire","device":{"connections":[["mac","%macaddr%"]]}} ENDON
ON system#boot do publish2 homeassistant/binary_sensor/%macaddr%_battery/config {"name":"Fire Alarm Battery","state_topic":"stat/%topic%/BATT","device_class":"battery","unique_id":"%macaddr%_battery","device":{"connections":[["mac","%macaddr%"]]}} ENDON
ON system#boot do publish2 homeassistant/sensor/%macaddr%_battery_voltage/config {"name":"Fire Alarm Batt Volt","state_topic":"stat/%topic%/STATUS11","value_template": "{{ value_json.StatusSTS.Vcc | round (2)}}","unit_of_measurement": "V","device_class":"battery","unique_id":"%macaddr%_battery_voltage","device":{"connections":[["mac","%macaddr%"]]}} ENDON

Rule2 1

[froniusMW]

Hey! I have an Cleverio fire alarm, but looks identical to this nedis. With tywe3s. Flashed went fine with the code in this thread. But the firealam sensor shows as unkown, any ideas on where to troubleshoot? Battery sensor seems to work. Thanks for the code btw guys!

[Atiroocky]

Hello,
I’ve got the same device from LSC.
I managed to flash it with ESPhome, and can add it tho HA, but no data is uploaded, apart from the connection status.
I put these lines at the end of the config file to get some datapoints :

binary_sensor:
  - platform: status
    name: detecteur-fumee-salon_status

uart:
  - id: com_1
    rx_pin: GPIO3
    tx_pin: GPIO1
    baud_rate: 9600
    
tuya:

In the log window of ESPhome, it connects well to the device, but nothing seems to come from the MCU, no datapoint, as if TX and RX GPIO were wrong.

[22:45:51][C][uart.arduino_esp8266:118]: UART Bus:
[22:45:51][C][uart.arduino_esp8266:119]:   TX Pin: GPIO1
[22:45:51][C][uart.arduino_esp8266:120]:   RX Pin: GPIO3
[22:45:51][C][uart.arduino_esp8266:122]:   RX Buffer Size: 256
[22:45:51][C][uart.arduino_esp8266:124]:   Baud Rate: 9600 baud
[22:45:51][C][uart.arduino_esp8266:125]:   Data Bits: 8
[22:45:51][C][uart.arduino_esp8266:126]:   Parity: NONE
[22:45:51][C][uart.arduino_esp8266:127]:   Stop bits: 1
[22:45:51][C][uart.arduino_esp8266:129]:   Using hardware serial interface.
[22:45:51][C][version.text_sensor:021]: Version Text Sensor 'detecteur-fumee-salon_firmware_version'
[22:45:51][C][version.text_sensor:021]:   Icon: 'mdi:new-box'
[22:45:51][C][status:034]: Status Binary Sensor 'detecteur-fumee-salon_status'
[22:45:51][C][status:034]:   Device Class: 'connectivity'
[22:45:51][C][captive_portal:088]: Captive Portal:
[22:45:51][C][mdns:115]: mDNS:
[22:45:51][C][mdns:116]:   Hostname: detecteur-fumee-salon
[22:45:51][C][ota:096]: Over-The-Air Updates:
[22:45:51][C][ota:097]:   Address: detecteur-fumee-salon.local:8266
[22:45:51][C][ota:100]:   Using Password.
[22:45:51][C][ota:103]:   OTA version: 2.
[22:45:51][C][api:139]: API Server:
[22:45:51][C][api:140]:   Address: detecteur-fumee-salon.local:6053
[22:45:51][C][api:142]:   Using noise encryption: YES
[22:45:51][C][tuya:041]: Tuya:
[22:45:51][C][tuya:046]:   Configuration will be reported when setup is complete. Current init_state: 3
[22:45:51][C][tuya:049]:   If no further output is received, confirm that this is a supported Tuya device.

@RSV-Tuono , which rx and tx GPIO did you configure to make the connection success to the MCU ?

Thanks for your help.

[barbudor]

This a Tasmota discussion forum
You'll ger better chance to get answers about ESP home on their own forum

[Atiroocky]

This a Tasmota discussion forum You'll ger better chance to get answers about ESP home on their own forum

Yes you’re right, but it was the only thread were this device was concerned.
I found another thread with a similar smoke detector (not exactly the same), with ESPhome flash, but gives no good result too. Seems that the MCU does not communicate in a Tuya standard.
I ended up flashing this device with Tasmota and applied the configuration of this thread. It works like a charm ;-)
Thanks for all the job done.