FAQ
TL;DR: Tasmota Device Groups (DGR) are now enabled on OpenBeken LN882H; firmware grew by +7,216 bytes; "I will merge the PR now." If you're an LN882H/OpenBeken user seeking Tasmota group sync, flash a DGR-enabled build and match group settings. [Elektroda, p.kaczmarek2, post #21099675]
Why it matters: It lets DIYers mirror switch/relay states across LN882H and Tasmota devices without extra glue code.
Quick Facts
- DGR support is enabled for LN882H in OpenBeken; SSDP/DDP were disabled for now as the PR was merged. [Elektroda, p.kaczmarek2, post #21099675]
- Final DGR-only build size: 655,468 bytes, an increase of +7,216 bytes versus release. [Elektroda, p.kaczmarek2, post #21099675]
- Earlier PR artifacts were +15,144 bytes larger than the latest release (663,396 vs 648,252). [Elektroda, max4elektroda, post #21099393]
- You can download and flash PR build artifacts; no local compile needed. [Elektroda, divadiow, post #21098249]
- Some devices marked “CB2S” were reported to host LN882H modules—unusual, but observed. [Elektroda, Zain00, post #21098234]
Does Tasmota Device Groups now work on LN882H with OpenBeken?
Yes. Device Groups (DGR) is now enabled for LN882H in OpenBeken. SSDP and DDP were removed to keep size down. “I will merge the PR now,” confirmed the maintainer. Update to a build that includes this merge to use DGR. [Elektroda, p.kaczmarek2, post #21099675]
Which firmware should I flash to get Device Groups on LN882H?
Use a build that includes the DGR merge. If testing before a release, download the ZIP artifact from PR #1252 and flash the included binary. “Builds created off the back of a pull request can be downloaded and flashed.” [Elektroda, divadiow, post #21098249]
How do I set up Device Groups on OpenBeken LN882H with a Tasmota device?
Follow this quick setup:
- Flash an OpenBeken build where DGR is enabled.
- In both devices, configure matching Device Group name and index.
- Reboot and toggle a relay to verify synchronized state.
Screens show Tasmota and OpenBeken group settings aligned. [Elektroda, Zain00, post #21098277]
Why does “startDriver DGR” return OK but DGR doesn’t start?
An early test build missed a required define, so the driver acknowledged but did not load. Update to the fixed build from the PR or the merged release. As the maintainer noted: “Ah there is a define missing, wait.” [Elektroda, p.kaczmarek2, post #21098299]
How can I confirm the DGR driver is active?
Open the Drivers page and look for DGR in the active list. If you “see no DGR driver active,” you’re on a build without DGR or it failed to start. Update to the corrected build and re-check. [Elektroda, Zain00, post #21098292]
Are Device Group packets sending and receiving correctly on LN882H?
Yes. A tester reported normal behavior after the fix: “It seems to be working correctly.” Keep both devices on the same group name and index, then verify by toggling a relay and watching peer updates. [Elektroda, Zain00, post #21098324]
How much firmware size overhead does enabling Device Groups add on LN882H?
With DGR-only, the binary measured 655,468 bytes, a +7,216-byte increase versus the reference build. This keeps the feature lean while enabling group sync. Plan OTA budgets accordingly. [Elektroda, p.kaczmarek2, post #21099675]
Is SSDP/DDP available on LN882H builds right now?
Not by default. The maintainer removed SSDP and DDP for LN882H to limit size and left only DGR. They added, “Still, maybe we could actually use SSDP as well?” Future builds may revisit this. [Elektroda, p.kaczmarek2, post #21099675]
Should I enable SSDP too, or is DGR enough?
DGR alone is sufficient for group control. One contributor is “a +1 for SSDP,” but also noted it’s “not a deal-breaker.” If you need device discovery, watch for builds that re-enable SSDP. [Elektroda, divadiow, post #21099713]
I flashed a general release and DGR didn’t work—why?
You likely used a build from before the DGR merge. That general release lacked the feature. Flash the artifact from PR #1252 or a newer merged release that includes DGR. “That’s a general release build.” [Elektroda, divadiow, post #21098280]
Do I need multiple devices to test Device Groups effectively?
Yes, to see synchronization you need at least two devices in the same group. The maintainer requested testers “who has more than 1 relay device” to validate multi-device behavior. [Elektroda, p.kaczmarek2, post #21098237]
I see “CB2S” on my board but it’s LN882H—normal?
It was reported by a user and acknowledged as unusual. Check the module’s printed markings and SoC package to confirm. Functionality isn’t affected if the correct firmware targets LN882H. [Elektroda, Zain00, post #21098234]
How big were the initial PR test builds compared to the latest release?
The PR #1252 artifacts were +15,144 bytes larger than the latest release (663,396 vs 648,252 bytes). Size was then optimized by disabling SSDP/DDP for LN882H. [Elektroda, max4elektroda, post #21099393]
What should I do if Device Groups misbehave after updating?
Verify both devices share the same group name and index, then check the Drivers page for DGR. If issues persist, re-flash the fixed build and retest. A tester planned to report any misbehavior after confirming it worked. [Elektroda, Zain00, post #21098324]
