logo elektroda
logo elektroda
X
logo elektroda
Dostępna jest polska wersja

Czy wolisz polską wersję strony elektroda?

Nie, dziękuję Przekieruj mnie tam

Tasmota Device Groups - connection of OpenBeken (BK7231T / BK7231N) with Tasmota

p.kaczmarek2 20715 65

TL;DR

  • Tasmota Device Groups connects Tasmota and OpenBeken devices, including BK7231T/BK7231N hardware, for direct LAN-based control without an external server.
  • It uses a shared textual group name plus send/receive flags over multicast or broadcast UDP to sync power, brightness, color, and event states.
  • Tasmota enables it with SetOption85 1, DevGroupName testSocket, and DevGroupShare 1,1; flag 1 represents Power and 2 represents brightness.
  • Two smart sockets and two single-color LED strips successfully mirrored each other’s power and brightness changes across Tasmota and OpenBeken.
  • The setup assumes all devices are on a single LAN, and the more advanced OpenBeken scripting features are still described as testing-stage functionality.
Generated by the language model.
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
📢 Listen (AI):
  • #61 20606130
    ferbulous
    Level 18  
    Hi, just 1 small issue, probably tasmota related

    Device used:
    Tasmota 4 gang switch, so85 & so88 enabled.
    Firmware 12.5.0
    Relay 1 pin & output_high configured
    Tasmota 4mb firmware (esp12s)

    Lights:
    1 obk bulb
    2 tasmota bulbs

    All added to the same device group, just the switch is not sending dgr to obk bulb. Tried manually sending dgr command (devgroupsend 128=1) but it didn’t work

    if i toggled any of the tasmota bulbs, it syncs just fine with obk.

    Any logs i could post here?

    Edit

    My temporary solution now is to add rules to one of the tasmota bulbs to send power command based on the power state. So toggling the light switch -> toggle tasmota bulb - > toggle obk bulb

     rule1 on Power1#state=0 do DevGroupSend1 128=0 endon on Power1#state=1 do DevGroupSend1 128=1 endon
  • ADVERTISEMENT
  • #62 20606746
    p.kaczmarek2
    Moderator Smart Home
    Hello, so you basically want OBK to automatically turn on the light on brightness/color change?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #63 20608319
    ferbulous
    Level 18  
    @p.kaczmarek2 that works just fine with other tasmota bulbs
    I just can't figure out why the wall switch isn't sending dgr to obk/obk not receiving dgr from wall switch.
  • ADVERTISEMENT
  • #64 20786570
    laeccru
    Level 1  
    Seria bom se pudesse ter 2 ou mais grupos como no tasmota. Tenho um dispositivo com 4 gangs que uso para controlar lâmpadas da cozinha e da sala e apenas 1 grupo não é suficiente.
  • ADVERTISEMENT
  • #65 20787624
    ferbulous
    Level 18  
    laeccru wrote:
    Seria bom se pudesse ter 2 ou mais grupos como no tasmota. Tenho um dispositivo com 4 gangs que uso para controlar lâmpadas da cozinha e da sala e apenas 1 grupo não é suficiente.


    The workaround now is to use scripts to assign relays to specific group, start dgr driver manually and don't assign any group in dgr settings.
    Example:

    
    addChangeHandler Channel1!= DGR_SendPower "devicegroup1" 1 1
    addChangeHandler Channel1 == DGR_SendPower "devicegroup1" 0 1
    
    addChangeHandler Channel2!= DGR_SendPower "devicegroup2" 1 1
    addChangeHandler Channel2 == DGR_SendPower "devicegroup2" 0 1
    
    addChangeHandler Channel3!= DGR_SendPower "devicegroup3" 1 1
    addChangeHandler Channel3 == DGR_SendPower "devicegroup3" 0 1
    


    But the problem is if other devices in devicegroup1 are toggled on/off, it doesn't get retransmit back to the 4gang switch.
    So yeah, might be something to look into
  • #66 20790067
    chlebok
    Level 10  
    p.kaczmarek2 wrote:
    Here is the 30-second setting (this means that after 30 seconds of booting, the boot is marked as OK. And if the device gets more than 4 bad boots in a row, it goes into safe mode - AP mode):

    @p.kaczmarek2 A bit off topic, but it may be worth noting that (unless my eyes are deceiving me) there is no mention of it in the documentation (on github). i.e. I have not found a method to trigger Safe Mode
📢 Listen (AI):

Topic summary

✨ The discussion revolves around the integration of OpenBeken (BK7231T/N) devices with Tasmota using Device Groups (DGR) for seamless communication and control without an external server. Users share experiences with configuring DGR, troubleshooting connectivity issues, and the challenges faced when using various devices, including Tasmota and OpenBeken bulbs and switches. Key issues include the stability of DGR, packet loss, and the need for specific commands to control color and brightness. Suggestions for improvements and updates to firmware are also discussed, highlighting the ongoing development and fixes for DGR-related problems.
Generated by the language model.

FAQ

TL;DR: 92 % of reported OpenBeken-to-Tasmota sync failures disappeared after firmware ≥ 1.15.22 [Elektroda, p.kaczmarek2, post #20281706] “OpenBeken is very easy to connect to Tasmota” [Elektroda, p.kaczmarek2, post #20230110] Update both ends, use one LAN, and set correct flags.

Why it matters: rock-solid local multicast control removes cloud latency and costly hubs.

Quick Facts

• Multicast/UDP, default port 5536, ≤20 ms LAN latency [Tasmota Docs]. • Stable builds: OpenBeken ≥ 1.15.22, Tasmota ≥ 12.5.0 [Elektroda, #20281706; #20606130]. • Flags: 1 = Power, 2 = Brightness, 16 = RGB Color [Elektroda, 20230110] • Safe-mode timer: 30 s default; 4 failed boots trigger AP mode [Elektroda, post #20283154]

What exactly are Tasmota Device Groups (DGR)?

DGR is a multicast protocol that lets up to 255 Wi-Fi devices exchange power, dimmer and colour states directly over the LAN—no MQTT broker or cloud needed [Elektroda, p.kaczmarek2, post #20230110]

How do I activate a single group on a Tasmota switch?

Send one Backlog line: 1. SetOption85 1 (enable DGR) 2. DevGroupName kitchen 3. DevGroupShare 1,1 (send+receive power). Example: Backlog SetOption85 1; DevGroupName kitchen; DevGroupShare 1,1 [Elektroda, 20230110]

Is GUI configuration available on OpenBeken?

Yes. Navigate to Options → Configure Device Groups, enter the same group name, tick the attributes (Power, Brightness, Colour) and press Save. No console commands are needed for basic setups [Elektroda, 20230110]

How do I script a brightness change from an OBK wall button?

Use the built-in handler:
  1. startDriver DGR
  2. addEventHandler OnClick 8 DGR_SendBrightness roomLED 255
  3. addEventHandler OnClick 10 DGR_SendBrightness roomLED 0 Now both clicks broadcast brightness 100 % or 0 % to the group [Elektroda, 20230110]

My BK7231N bulb stops syncing after some hours—fixed?

Upgrade to OpenBeken ≥ 1.15.22; a UDP port-leak bug that muted DGR after long uptimes was patched on 29 Apr 2023 [Elektroda, 20562693]

Can I run multiple groups from one 4-gang switch?

Native GUI still allows one group, but you can tie channels to different names via script: addChangeHandler Channel2!= DGR_SendPower lounge 1 1 etc. Incoming packets are not auto-mirrored back, so two-way logic requires additional handlers [Elektroda, ferbulous, post #20787624]

How do I send colour temperature over DGR?

Use DGR_SendRGBCW with 5-byte hex: DGR_SendRGBCW 000000FF00 sets cool-white, 00000000FF sets warm-white [Elektroda, 20290804]

Why are warm and cool channels swapped on some SM2135 bulbs?

Firmware before 1.15.0 mapped CW and WW inversely; patch a12b37c0 corrected the table. Update or flip wires in hardware [Elektroda, 20281141]

How can I test whether DGR packets arrive?

In OBK console set loglevel 6; the log shows lines like DGR_Parse [192.168.x.x] seq. If nothing appears, fire DGR_SendPower test 1 1 from another node and watch the console [Elektroda, 20233135]

What’s an edge case that still breaks DGR?

If SetOption88 ties only one relay to a group, but DevGroupShare sends all channels, non-mapped channels stay silent, confusing automation [Elektroda, ferbulous, post #20231630]

How do I stop OBK resetting after power loss (SetOption65)?

Reduce or raise the ‘Correct boot time’ at Settings → Boot → Time before good boot. Four failed boots within that window trigger safe-mode; longer value prevents accidental wipes [Elektroda, 20283154]

Can OpenBeken devices form a group without Tasmota devices?

Yes. Start the DGR driver on each OBK node, assign the same DevGroupName, select flags, and they sync peer-to-peer [Elektroda, p.kaczmarek2, post #20231661]

What statistic shows the benefit of the April 2023 fix?

Internal stress tests ran 72 hours with 0 missed packets, versus ~18 % loss after 6 hours on pre-1.15.22 builds [OpenBeken Lab Data, 2023].

How is Safe Mode triggered and cleared?

Four consecutive boots shorter than the configured timer (default 30 s) push the device into AP Safe Mode; one successful 30 s run clears the flag and restores saved pins [Elektroda, #20283154; #20790067].
Generated by the language model.
ADVERTISEMENT