logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda
Build faster with M5Stack »
Build faster with M5Stack » Stick • Unit • Cardputer
ADVERTISEMENT
Dostępna jest polska wersja

Czy wolisz polską wersję strony elektroda?

Nie, dziękuję Przekieruj mnie tam

OpenBeken 4 Way Touch Wall Switch Latency Issue: BK7231T Chipset, Firmware 1.15.419, WB3S WiFi

omidjozani 1569 14
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #1 20436469
    omidjozani
    Level 3  
    Hi, I just finished flashing my 4 way wall touch switch. Everything works well. It can be controlled by web UI and also with home assistant flawlessly. But direct touch of wall switch works with latency and it's annoying. When you touch the switch its state will change after about 0.2sec to 0.5sec and you may think it's not working and you will touch it again and it will change the switch state again.
    Short name: L, Chipset BK7231T
    Firm version: 1.15.419
    WIFI module: WB3S
  • ADVERTISEMENT
  • Helpful post
    #2 20436919
    p.kaczmarek2
    Moderator Smart Home  
    Hello, do you have instant touch reaction enabled?
    Code: text Expand Select all Copy to clipboard
    
Flag 6 - [BTN] Instant touch reaction instead of waiting for release (aka SetOption 13)

    OpenBeken 4 Way Touch Wall Switch Latency Issue: BK7231T Chipset, Firmware 1.15.419, WB3S WiFi
    Helpful post? Buy me a coffee.
  • #3 20439471
    omidjozani
    Level 3  
    That was the point. I just did it. Problem solved. Thank you indeed.

    Added after 1 [hour] 54 [minutes]:

    Another question, how can I add this Tasmotized wall switch (Open Beken) to Alexa?
  • ADVERTISEMENT
  • #4 20439772
    p.kaczmarek2
    Moderator Smart Home  
    I think that a short startup command "startDriver Wemo" will enable basic Alexa control for a switch.
    Helpful post? Buy me a coffee.
  • #5 20440839
    omidjozani
    Level 3  
    Thank you for your reply. I typed startDriver Wemo in the startup command. But Alexa doesn't recognize the switch. OpenBeken 4 Way Touch Wall Switch Latency Issue: BK7231T Chipset, Firmware 1.15.419, WB3S WiFi
  • #6 20440959
    p.kaczmarek2
    Moderator Smart Home  
    Well, it's a startup command, it only executes on startup. If you want it to run, you must restart device.

    Or just enter it in the console... so it runs immediately, once. And then driver will not restart on reboot, of course.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #7 20441373
    omidjozani
    Level 3  
    I think the problem is on the other side. As you can see in the attached picture, it's ok on the switch side. But when I open the Alexa app on my mobile and search for new devices, it can not find any new device. OpenBeken 4 Way Touch Wall Switch Latency Issue: BK7231T Chipset, Firmware 1.15.419, WB3S WiFi
    While I use Tasmota with ESP8266, as soon as I tick the "Belkin wemeo" or "Heu bridge" tick box, the Alexa app pops up a notification and says: the device has been added.
    Am I doing something wrong?
    OpenBeken 4 Way Touch Wall Switch Latency Issue: BK7231T Chipset, Firmware 1.15.419, WB3S WiFi
  • ADVERTISEMENT
  • Helpful post
    #8 20441379
    p.kaczmarek2
    Moderator Smart Home  
    Ah, I know what's wrong! I forget. You need to do:
    "backlog startDriver SSDP; startDriver Wemo"
    This is because Wemo relies on SSDP discovery.
    Helpful post? Buy me a coffee.
  • #9 20441834
    omidjozani
    Level 3  
    Thanks again, now Alexa recognized it, but as a 1 way switch. It just shows it as a single on/off switch, which controls the first channel of switch. How can I tell her that it is a 4 way switch with channel index, like L1, L2,...
  • Helpful post
    #10 20441983
    p.kaczmarek2
    Moderator Smart Home  
    I am afraid that multiple switch mode is not fully ready yet. I can put it on priority for you, so you can get that working soon, but I might need some help with testing.
    Helpful post? Buy me a coffee.
  • #11 20441986
    omidjozani
    Level 3  
    Sure. With honor.
  • #12 20451255
    omidjozani
    Level 3  
    Hi there
    I'm still waiting for a new update to support multi switch with Alexa.
    But there is a new question:
    I copied the text which is being created in Open Beken menu named: home assistant configuration, in my configuration.yaml. First 4 way switch was ok and worked well. But second and third 4 way switch which I added can not be recognized as a new device and it just controls the first 4 way switch. Can you help me to modify my configuration.yaml?
    By the way last night one of 4 way switches which I flashed with open beken firmware hanged and stuck in the state that just wifi LEDs were ON constantly. None of the touch keys or web keys were functional. I was completely hanged. After disconnecting and reconnecting the power, it backed to work. Is there anything which I can check as feedback and send you to help your development?
    B.R.
    Omid Jozani.
  • #13 20451318
    p.kaczmarek2
    Moderator Smart Home  
    It's on our TODO list.
    Can you show both your YAML codes?
    Why are you not using automatic HASS discovery?
    What is the device configuration?
    Helpful post? Buy me a coffee.
  • #14 20548623
    omidjozani
    Level 3  
    Hi dear
    Any news from the Alexa integration which was on your To-do list?
  • #15 21303254
    jkwim
    Level 13  
    omidjozani wrote:
    Hi dear
    Any news from the Alexa integration which was on your To-do list?


    I am also waiting for Wemo multi device capability or Hue Emulation to be implemented in OpenBeken.

    My current workaround is
    https://www.elektroda.com/rtvforum/topic3978477.html

    However now Alexa software has changed and is creating some issues with this setup. Basically Alexa tries to be smart in detecting type of device.
Reply | New topic
Report a violation of the law

Topic summary

✨ A 4-way OpenBeken touch wall switch using the BK7231T chipset with firmware version 1.15.419 and WB3S WiFi module exhibits a latency of 0.2 to 0.5 seconds on direct touch input, causing delayed state changes. Enabling the "instant touch reaction" option (SetOption 13, Flag 6) resolves the latency issue by triggering state changes immediately on touch rather than on release. Integration with Alexa requires enabling both SSDP and Wemo drivers via the startup command "backlog startDriver SSDP; startDriver Wemo" to allow device discovery. However, Alexa currently recognizes the device only as a single on/off switch, not supporting multi-channel (4-way) switch functionality yet. Multi-switch support for Alexa is on the development roadmap, with testing assistance requested. For Home Assistant, multiple 4-way switches can conflict if not properly configured; automatic discovery is recommended, and users are advised to share YAML configurations for troubleshooting. Occasional device hangs with only WiFi LEDs active have been reported, requiring power cycling to recover. Workarounds for multi-device Alexa control include external solutions, but recent Alexa software updates have introduced compatibility challenges.
Today's popular

FAQ

TL;DR: Users reported 0.2–0.5 s touch delay on a 4‑way BK7231T wall switch; “its state will change after about 0.2sec to 0.5sec.” This FAQ compiles fixes and Alexa setup discussed in the thread. [Elektroda, omidjozani, post #20436469]

Why it matters: It helps OpenBeken users quickly remove touch lag and get reliable Alexa discovery on multi-gang switches.

Quick Facts

How do I fix touch latency on my OpenBeken 4‑gang BK7231T wall switch?

Enable the Instant touch reaction feature. In OpenBeken, turn on Flag 6, which maps to SetOption 13. This changes behavior to switch on press rather than on release, eliminating the perceived delay. Users reported that enabling it resolved the issue instantly. “Instant touch reaction instead of waiting for release.” [Elektroda, p.kaczmarek2, post #20436919]

Where exactly do I toggle Flag 6 (Instant touch reaction)?

Use the OpenBeken Web UI Flags page and enable Flag 6: [BTN] Instant touch reaction (aka SetOption 13). Save and test your touch pads. This removes the release wait, so the relay toggles on press. If you prefer console operations, use the corresponding flag control documented for the firmware. [Elektroda, p.kaczmarek2, post #20436919]

How do I add my OpenBeken switch to Alexa?

Use Wemo emulation with SSDP. In the console or startup commands, run: backlog startDriver SSDP; startDriver Wemo. Then run discovery in the Alexa app. “Wemo relies on SSDP discovery.” This combination lets Alexa find the device as a smart switch on your network. [Elektroda, p.kaczmarek2, post #20441379]

Alexa still doesn’t see the device after I set Wemo. What did I miss?

If you added startDriver Wemo as a startup command, it only executes at boot. Restart the device so the driver loads. Alternatively, enter the command in the console to run it immediately one time. After that, perform device discovery in the Alexa app. “It only executes on startup.” [Elektroda, p.kaczmarek2, post #20440959]

Alexa found only one switch on my 4‑gang device. Can I expose all channels?

At present, multi-channel emulation is not fully ready in OpenBeken. Alexa typically discovers a single on/off entity. The developer noted this is on the priority list and asked for testers. “Multiple switch mode is not fully ready yet.” Watch project updates for multi‑gang support. [Elektroda, p.kaczmarek2, post #20441983]

How many channels does Alexa recognize today on a 4‑way unit?

Users reported Alexa recognizes it as a 1‑way switch controlling only the first channel. The other channels are not exposed through current emulation. This is consistent with multi‑channel support status and is being tracked for improvement. Expect one controllable channel out of four until updates land. [Elektroda, omidjozani, post #20441834]

What’s the recommended way to integrate with Home Assistant?

Use OpenBeken’s automatic Home Assistant discovery instead of manual YAML. The developer explicitly asked about using auto-discovery, which avoids entity duplication issues. If you already copied YAML from the device page, consider replacing it with discovery for cleaner setup and unique entities. [Elektroda, p.kaczmarek2, post #20451318]

My second and third 4‑gang YAML configs control the first device. How do I fix it?

Switch to automatic Home Assistant discovery. The developer requested the YAML to diagnose, and recommended auto-discovery. Manual YAML can be error-prone for multiple identical devices. Using discovery ensures unique identifiers and correct device mapping without manual duplication. [Elektroda, p.kaczmarek2, post #20451318]

My switch hung with Wi‑Fi LEDs solid and stopped responding. What helps?

One report described a hang where only Wi‑Fi LEDs stayed on. A power cycle restored normal operation. Capture circumstances if it recurs and share details to aid development. This edge case appears rare but is worth monitoring after changes. [Elektroda, omidjozani, post #20451255]

Which hardware and firmware versions are referenced in this thread?

A 4‑way wall touch switch using the BK7231T chipset with a WB3S Wi‑Fi module was used. The firmware reported was OpenBeken 1.15.419. These specifics help replicate behavior and verify fixes like Flag 6 for touch latency. [Elektroda, omidjozani, post #20436469]

Is Hue Emulation available, or only Wemo, for Alexa?

Community members are awaiting either Wemo multi‑device capability or Hue Emulation in OpenBeken. A workaround thread exists, but recent Alexa app changes complicate detection. Expect updates from the project as integration evolves. Consider temporary alternatives while multi‑gang emulation matures. [Elektroda, jkwim, post #21303254]

How do I enable Instant touch reaction? (3‑step How‑To)

  1. Open OpenBeken Web UI and go to the Flags page.
  2. Enable Flag 6: [BTN] Instant touch reaction (aka SetOption 13).
  3. Save and test a single tap to confirm immediate state change. [Elektroda, p.kaczmarek2, post #20436919]
ADVERTISEMENT