[ST Edge] •• Tasmota Edge •• for Sonoff, Tuya & many other ESP WiFi & HTTP devices - over 2000 Tasmota supported devices

[waphbs (小鸭 小)]

Thanks for your efforts. It should be able to display the working status of the air conditioner synchronously, but the synchronization time delay is a bit large, it takes about 30 seconds. There are a few more questions that I hope to modify: Can the title text in the number 1 in the figure be called indoor temperature? Can the number 2 in the figure be called set temperature or configuration temperature instead of always showing the cooling temperature? Can the signal strength and quality data in the history records be reduced or turned off? There are too many. I hope to only see necessary information such as indoor temperature, set temperature and mode. Thank you again

[waphbs (小鸭 小)]

Signal strength and quality can add a switch in the settings, which can be turned off in the settings. The mode option can also add custom selections in the settings, such as letting it only display cooling and heating, which would be better.

[waphbs (小鸭 小)]

Too much synchronization delay is also a problem

[hongtat (HONGTAT TAN)]

@waphbs

The title texts “Temperature” and “Cooling Temperature” are fixed and cannot be dynamically adjusted.

The synchronization delay happens because Tasmota cannot push certain values to SmartThings, requiring us to poll for them instead.

You can disable the signal strength and quality history in the settings.

[waphbs (小鸭 小)]

[grid]

[/grid]This is my infrared air conditioner remote control. Its interface is displayed like this. It is very beautiful and logical.

[waphbs (小鸭 小)]

[grid]

[/grid]I just found that the operating mode of the air conditioner and the operating status of the air conditioner fan are not synchronized. Please fix it. Thank you.

[waphbs (小鸭 小)]

When changing the device icon, an error message appears and the device cannot be saved.
Is there any plan to fix the above issue?

[Maciek1]

Witam

Jak dodać czujnik zbudowany na esp8266 i BMP180 do ST przy użyciu obecnego sterownika żeby widzieć kafelek z pomiarami temperatury i ciśnienia atmosferycznego a nie standardowy przycisk gdzie trzeba wejść żeby odczytać temperaturę

[barrie (Barrie Thesen)]

Any tips on using Tasmota Edge to connect to a human presence HWK2410C using an ESP8266. I would just be connectin OUT to GPI05 and not connecting RX and TX. Should I just configure the device as a SWITCH?

[SRolly]

Hallo,

meine Frage ist ob es noch funktioniert und ob man es gefahrenlos kaufen kann.

Mit freundlichen Grüßen

[flsoto (Felipe)]

For the past 3 days my Tasmota devices have stopped working.

Is anyone else experiencing the same issue?

[montyfert (martin)]

hi have you tried esp32 ? I have a couple of esp32 with temperature sensors attached connected to smartthings via matter, but don’t have a human presence HWK2410C to test .

martin

[barrie (Barrie Thesen)]

Hi Martin,
I did get this working with an ESP8266. I Tasmotized the ESP8266 and used Hongtat’s Tasmota Edge to connect to Smartthings. I did configure the 2410C sensor as a switch in Tasmota. I like the Human Presence sensor better than a motion sensor because you know someone is in a space and for how long. I got a detection range of 7 metres. I am interested that you got the temperature sensor hooked up to SmartThings using Matter. This seems more straightforward than using Tasmota and Tasmota Edge.

Barrie

[montyfert (martin)]

hi another thing I’ve noticed about the esp32 matter thingy in matter settings in the tasmota web browser view there is an option to Add Remote Tasmota .

where you can add other tasmota devices e.g. esp8266 etc and they should show up in smartthings .

[Maciek1]

tak opcja zdalnych czujników działa miałem tak podłączone czujniki temperatury z esp 8266 budzące się co 10 min a samo esp32 z Matter działało jako hub Matter. smartthings wtedy widział je cały czas jako online a same esp 8266 dobrze skonfigurowane i gołe bez bajerów na baterii 2000mAh działały około 30dni

[LazyPawn]

I have some ESP8266 boards connected to motion sensors, running Tasmota and connected to SmartThings. They worked perfectly until a few days ago, now the motion sensors are no longer updating. It is probably related to the latest hub firmware update (0.62.7). Tasmota Edge 2025.11.1 (Pro).
Logcat constantly shows an error in red - ERROR Tasmota Edge Tasmota Sensor thread encountered error: [string “commands.lua”]:328: attempt to perform arithmetic on a nil value.
@hongtat - any help with this?

[Hugo_Ng]

I have the same issue, I even uninstall tasomota edge and reinstall it, but not fixing the problem, and i gpt it, no solution so far

Motion sensor ↓ 433 MHz ↓ RF Bridge 192.168.68.xx ↓ Tasmota receives F7DACE ↓ WebQuery 192.168.68.56:48415 ↓ Tasmota Edge ↓ SmartThings Motion Sensor @hongtat

[AlecBL (Alec)]

The same is here! Any help from the developer?

[barrie (Barrie Thesen)]

Hello Hongtat,

I’m trying to set up a SmartThings Virtual Button using Tasmota Edge and an RF Bridge, and I’ve run into a problem that I’m hoping you can help me understand.

I have a Sonoff RF Bridge running Tasmota 12.1.1. I am using the Tasmota Edge driver, which reports:

Tasmota Edge version: 2025-11-06T15:44:35.39620742

My goal is to have a physical RF remote button received by the RF Bridge cause a SmartThings Virtual Button to be pressed, so that I can use that Virtual Button as a trigger for a SmartThings Routine.

The RF portion appears to be working correctly.

For example, when I press the physical RF button, the RF Bridge receives:

B706B8

and its Rule successfully sends this to the Gateway at:

192.168.4.30:57161/j

with:

{"Mac":"C44F33A281E0","RfReceived":{"Data":"B706B8"}}

I can also use the SmartThings Virtual Button to cause the RF Bridge to transmit B706B8, and the RF Bridge’s receiver detects the transmitted code as B706B8. So both receiving and transmitting RF appear to work.

The problem is that the physical RF button does not cause the SmartThings Virtual Button to change state or create a History entry, and therefore it does not trigger the SmartThings Routine.

I noticed something else that may be significant.

In your documentation for Virtual Buttons, I see examples showing that multiple RF buttons can be configured in the Gateway. I remember having this working in the past with a 4-button Virtual Button.

However, when I configure a 4-button Virtual Button today, the Gateway interface only provides the two fields for a single button:

1. RFReceived/state code

2. Tasmota command to send

There are no additional fields where I can enter the codes for buttons 2, 3, and 4.

For example, I currently have:

State/RF code:
B706B8

Command:
Backlog RfSync 11080; RfLow 380; RfHigh 1110; RfCode #B706B8

The SmartThings Virtual Button can be operated from within the SmartThings app, but pressing the physical RF button does not cause the Virtual Button to register the incoming RF code.

Could you tell me:

1. Should a 4-button Virtual Button currently display four RF-code/command entries in the Gateway?

2. If so, why would my Gateway display only one?

3. Is there a particular version of the Tasmota Edge driver or Gateway that is required for multiple Virtual Button entries?

4. Has the Virtual Button/RF receiving functionality changed in recent versions?

I have only one RF Bridge, and the Gateway address is definitely 192.168.4.30:57161.

I would prefer not to change the working RF Bridge configuration until I understand whether the problem is with the Gateway or Tasmota Edge.

Thank you for any help you can provide. I’ve used Tasmota Edge for quite a while and would really like to get this working again.

Best regards,

Barrie
Calgary, Canada

[barrie (Barrie Thesen)]

I also tried hooking up a 12v power supply to the dongle just in case the battery was low, but no change. I still can’t get a virtual button working with my RF Bridge.