Important bug identified and solved on Sonoff-Tasmota forked by stefanbode

3 minutes of reading

With the recent Update Searchnameof the firmware Tasmota 6.5 some changes related to functionality have been introduced INTERLOCK; these changes have had impacts - inevitable - even on the note Stefanbode fork dedicated to the management of tappelectric arrays.

To this proposito, these days our user Loris has identified a fairly annoying bug.

Using the integration of an actuator connected to a tappelectric arelle (type Sonoff dual) with Home Assistant and checking that entity (of type "Cover") using the keys "Up down" (of Home Assistant) and finally activating the second relay while the first is active, the second relay is also deactivated instantly. Translated: if the tapparella is going up and you decide to let it go down, the tapparella si farm.

This behavior it is obviously wrong.

As can be seen from the messages sent to the broker by the actuator, it appears an incorrect shutdown of the second relay (the last one)POWER2: OFF"):

------------
14:27:41 Start shutter in right direction -1
14:27:41 MQT: stat/sonoff-cletto/RESULT = {"POWER1":"OFF"}
14:27:41 MQT: stat/sonoff-cletto/POWER1 = OFF (salvato)
14:27:41 MQT: stat/sonoff-cletto/RESULT = {"POWER2":"ON"}
14:27:41 MQT: stat/sonoff-cletto/POWER2 = ON (salvato)
14:27:41 MQT: stat/sonoff-cletto/RESULT = {"shutterposition1":10}
14:27:41 MQT: stat/sonoff-cletto/SHUTTER1 = 28 (salvato)
14:27:41 MQT: stat/sonoff-cletto/RESULT = {"POWER2":"OFF"}
14:27:41 MQT: stat/sonoff-cletto/POWER2 = OFF (salvato)
14:27:41 MQT: tele/sonoff-cletto/RESULT = {"SHUTTER-1":{"position":28, "direction":0}}
14:27:43 MQT: stat/sonoff-cletto/RESULT = {"shutterposition1":28}
------------

We also have a video demonstrating the phenomenon:

This does not occur instead using the physical keys or the ON / OFF keys on the webgui Tasmota:

------------
14:35:14 MQT: stat/sonoff-cletto/RESULT = {"POWER1":"ON"}
14:35:14 MQT: stat/sonoff-cletto/POWER1 = ON (salvato)
14:35:14 Shutter 0: Real Pos: 200, Target 40000, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 0.1  [s]
14:35:15 Shutter 0: Real Pos: 2200, Target 40000, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 1.1  [s]
14:35:16 Shutter 0: Real Pos: 4200, Target 40000, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 2.1  [s]
14:35:17 Shutter 0: Real Pos: 6200, Target 40000, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 3.1  [s]
14:35:18 Shutter 0: Real Pos: 8200, Target 40000, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 4.1  [s]
14:35:19 Shutter 0: Real Pos: 10200, Target 40000, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 5.1  [s]
14:35:20 MQT: stat/sonoff-cletto/RESULT = {"POWER1":"OFF"}
14:35:20 MQT: stat/sonoff-cletto/POWER1 = OFF (salvato)
14:35:21 MQT: stat/sonoff-cletto/RESULT = {"POWER2":"ON"}
14:35:21 MQT: stat/sonoff-cletto/POWER2 = ON (salvato)
14:35:21 Shutter 0: Real Pos: 11600, Target 0, source: Shutter, start-pos: 0 %, direction: -1, rtcshutter: 0.2  [s]
14:35:22 Shutter 0: Real Pos: 9600, Target 0, source: Shutter, start-pos: 0 %, direction: -1, rtcshutter: 1.1  [s]

-----------

Another demonstration video:

Loris, flanked by Snakuzzo, he immediately suggested a bug on the stefanbode fork (since su Tasmota original the slider for the management of the tapparelle is absent).

Snakuzzo therefore has prosaw to open an issue at GitHub in order to report the possibility that there was a bug in the firmware, bug that was actually recognized by the developer which he has quickly proexpected to make a corrective change, issued as "Sonoff-Tasmota 6.5.0.3 stb-1.4"

We provveduto to perform the test again using the new firmware version and actually the proproblem seems to have been solved (POWER2 OFF is released correctly only once it reaches the end of its travel):

-----------
18:28:18 MQT: stat/sonoff-cletto/RESULT = {"POWER1":"ON"}
18:28:18 MQT: stat/sonoff-cletto/POWER1 = ON (salvato)
18:28:18 MQT: stat/sonoff-cletto/RESULT = {"shutterposition1":56}
18:28:18 Shutter 0: Real Pos: 1100, Target 22400, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 0.6 [s]
18:28:19 Shutter 0: Real Pos: 3100, Target 22400, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 1.6 [s]
18:28:20 Shutter 0: Real Pos: 5100, Target 22400, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 2.5 [s]
18:28:21 Shutter 0: Real Pos: 7100, Target 22400, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 3.5 [s]
18:28:22 Shutter 0: Real Pos: 9100, Target 22400, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 4.5 [s]
18:28:23 Shutter 0: Real Pos: 11100, Target 22400, source: Shutter, start-pos: 0 %, direction: 1, rtcshutter: 5.5 [s]
18:28:24 Start shutter in direction -1
18:28:24 MQT: stat/sonoff-cletto/RESULT = {"POWER1":"OFF"}
18:28:24 MQT: stat/sonoff-cletto/POWER1 = OFF (salvato)
18:28:24 MQT: stat/sonoff-cletto/RESULT = {"POWER2":"ON"}
18:28:24 MQT: stat/sonoff-cletto/POWER2 = ON (salvato)
18:28:24 MQT: stat/sonoff-cletto/RESULT = {"shutterposition1":9}
18:28:25 Shutter 0: Real Pos: 10500, Target 3600, source: Shutter, start-pos: 0 %, direction: -1, rtcshutter: 1.0 [s]
18:28:26 Shutter 0: Real Pos: 8500, Target 3600, source: Shutter, start-pos: 0 %, direction: -1, rtcshutter: 2.0 [s]
18:28:27 Shutter 0: Real Pos: 6500, Target 3600, source: Shutter, start-pos: 0 %, direction: -1, rtcshutter: 3.0 [s]
18:28:28 Shutter 0: Real Pos: 4500, Target 3600, source: Shutter, start-pos: 0 %, direction: -1, rtcshutter: 4.0 [s]
18:28:28 MQT: stat/sonoff-cletto/SHUTTER1 = 9 (salvato)
18:28:28 MQT: stat/sonoff-cletto/RESULT = {"POWER2":"OFF"}
18:28:28 MQT: stat/sonoff-cletto/POWER2 = OFF (salvato)
18:28:28 MQT: tele/sonoff-cletto/RESULT = {"SHUTTER-1":{"position":9, "direction":0}}
18:28:28 MQT: stat/sonoff-cletto/RESULT = {"shutterposition1":9}
-----------

Videos:

Currently the bug has therefore been effectively resolved.
We therefore recommend to anyone using this important fork of the well-known firmware Tasmota to update i proprior actuators.


telegram

Stay up to date through ours Telegram channel!