Mirabella Genio Wi-Fi LED USB Desk Lamp With Wireless Charger - Teardown

wolfieeewolf 1836 2

TL;DR

Teardown of the Mirabella Genio Wi-Fi LED USB Desk Lamp With Wireless Charger I003867, a Bunnings $29.95AUD desk lamp using a WB3S BK7231T module with TuyaMCU.
CloudCutter via LightLeak flashed the main chip, then OBK logging exposed dpID 1 for power, dpID 3 and 4 for value-based light control, and dpID 2 remained unclear.
The lamp reports 255 and 127 in the logs for mode states, while brightness changes appear around 25 and 246 when holding the power button to dim or brighten.
Configuration only works partially: the light can turn on and adjust temperature or brightness, but the slider snaps back to 0 and full OFF control still fails.

Report a violation of the law

Reply Cool? Ranking DIY | New topic

Notify about new articles

📢 Listen (AI):

Helpful post

Post #1

20804782 08 Nov 2023 03:00

Device Name: Mirabella Genio Wi-Fi LED USB Desk Lamp With Wireless Charger - I003867
Device Type: Desk Lamp with Qi Charger
Device Chip: WB3S - BK7231T with TuyaMCU
Device Purchased Bunnings Warehouse - $29.95AUD - Appears they not stocking this anymore and selling last of stock

Flashing of Main Chip

CloudCutter Profile - Profile.json

I created a CloudCutter profile using LightLeak.

WB3S Module Datasheet

Configuration of Module

I still haven't worked this out yet. I have nothing configured and the device works if you press the buttons on the physical device. As far as I can tell this is using a TuyaMCU to change the light settings.

After looking at the profile.json I think these are the dpID values and what they do

dpID 1 - enum - Light Mode - cool, white, warm.
As per json it states 4 settings. Breathe, nature, read, night but when pressing the physical button it only cycles 3 settings

dpID 2 - value - Dimmer - Query dim light down to min of 25

dpID 3 - value - Dimmer - Query brighten light up to 255

dpID 4 - bool - Light ON/OFF

Setup with this code but nothing works

startDriver TuyaMCU
setChannelType 1 Toggle
setChannelType 2 LowMidHigh
setChannelType 3 Dimmer
setChannelType 4 Dimmer
tuyaMcu_setDimmerRange 0 1000
linkTuyaMCUOutputToChannel 4 bool 1
linkTuyaMCUOutputToChannel 1 enum 2
linkTuyaMCUOutputToChannel 2 val 3
linkTuyaMCUOutputToChannel 3 val 4

However, looking at the OBK logs it's a different story

Pressing - Light ON/OFF

ON

Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 01 01 00 01 00 11 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 1, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 0

OFF

Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 01 01 00 01 01 12 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 1, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 1

Pressing - Mode button - Light has to be on or it does nothing

I did notice I get different codes depending on the mode

Warm/White Light

Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 FF 19 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 3, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 255
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 04 02 00 04 00 00 00 7F 9A 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 4, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 127

Cool Light

Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 FF 19 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 3, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 255
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 04 02 00 04 00 00 00 FF 1A 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 4, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 255

Warm/Orange Light


Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 FF 19 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 3, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 255
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 04 02 00 04 00 00 00 00 1B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 4, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04

Pressing the Dimmer button - holding down the power button makes the light dim and holding it down again will brighten the light.

I get this while holding the power button

Info:TuyaMCU:Consumed 256 unwanted non-header byte in Tuya MCU buffer
Info:TuyaMCU:Skipped data (part) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Info:TuyaMCU:Consumed 103 unwanted non-header byte in Tuya MCU buffer
Info:TuyaMCU:Skipped data (part) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Info:TuyaMCU:Consumed 52 unwanted non-header byte in Tuya MCU buffer
Info:TuyaMCU:Skipped data (part) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Info:TuyaMCU:Consumed 52 unwanted non-header byte in Tuya MCU buffer
Info:TuyaMCU:Skipped data (part) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Info:TuyaMCU:Consumed 15 unwanted non-header byte in Tuya MCU buffer
Info:TuyaMCU:Skipped data (part) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes

On release, I get this when dimming down from cool white


Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 19 33 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 3, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 25
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 04 02 00 04 00 00 00 FF 1A 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 4, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 255

and this on brightening from cool white


Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 F6 10 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 3, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 246
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 04 02 00 04 00 00 00 FF 1A 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 4, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 255
Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04

There is a timer button that when held down sets the light to turn off in 40 minutes. This doesn't log anything

So after looking at all this. I think these are the dpID values and what they do

dpID 1 - bool - Light ON/OFF

dpID 2 - No idea

dpID 3 - value - Light Mode - cool, white, warm. ? also does dimming

dpID 4 - value - Light Mode - cool, white, warm. ? also does dimming

I think the dimming/brightening might have something to do with the int: command maybe? It's the one that changes

Setup with this code - it kinda works

startDriver TuyaMCU
setChannelType 1 Toggle
setChannelType 3 Dimmer
setChannelType 4 Dimmer
tuyaMcu_setDimmerRange 0 1000
linkTuyaMCUOutputToChannel 1 bool 1
linkTuyaMCUOutputToChannel 3 val 3
linkTuyaMCUOutputToChannel 4 val 4

dpID 1 - Turns light ON if off but will not turn light OFF if on

dpID 2 - Nothing

dpID 3 - Query brightness level - The slider does change light but the slider defaults back to 0. Brightness does stay changed

dpID 4 might be the mode change as when moving the slider the temperature of light changes depending on where you move the slider but it doesn't work correctly and the slider defaults back to 0. Light does stay changed temperature. Light also does not change to all temperature levels

I've tried changing the channel type to see if there is something that might work better than sliders and toggles but still can't get anything to work.

Will keep trying to work this out and will post here if I get it sorted. I've not worked with TuyaMCU before so I'm sure it's something I'm doing.

Cool? Ranking DIY

About Author

wolfieeewolf wolfieeewolf

Level 11

Offline

wolfieeewolf wrote 93 posts with rating 20, helped 7 times. Been with us since 2023 year.

ADVERTISEMENT
#2 20813016 13 Nov 2023 12:39

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Posts: 14649

Help: 655

Rate: 12660
Helpful post? (0)

Post #2
20813016 13 Nov 2023 12:39

Some TuyaMCU devices needs to be "paired" first before using. Can you try forcing the 0x04 WiFi state (paired) and retry?
Add the following line to autoexec.bat script after TuyaMCU init:
Code: text Expand Select all Copy to clipboard
tuyaMcu_defWiFiState 4

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#3 20817475 16 Nov 2023 07:24

wolfieeewolf wolfieeewolf

Level 11

Posts: 93

Help: 7

Rate: 20
Topic author Helpful post? (0)

Post #3
20817475 16 Nov 2023 07:24

I added the code to the autoexec.bat but still nothing.

I'm sure I don't have the dpID's set up right. I just have to work out what is going on.

I did try to dump some data using the TuyaMCU Analyzer but it returns nothing. I don't have the stock firmware so I can't reflash the device and see if that produces anything.

Might just have to keep playing around with things. The physical buttons work fine, I just can't get anything to work with the webGUI.

Added after 2 [hours] 40 [minutes]:

So I ran my OBK log through TuyaMCU analyzer and it spits out this

I tried this

Code: text Expand Select all Copy to clipboard
startDriver TuyaMCU tuyaMcu_defWiFiState 4 setChannelType 1 Toggle setChannelType 3 Dimmer setChannelType 4 Dimmer tuyaMcu_setDimmerRange 0 255 linkTuyaMCUOutputToChannel 1 1 1 linkTuyaMCUOutputToChannel 3 2 3 linkTuyaMCUOutputToChannel 4 2 4

Still had issues with power, brightness and temperature mode so I turned on Flag 8 and this fixed the problem.

It appears this device is now working. Every now and then it is a bit slow to update. Would be nice to see the webGUI have a temperature slider and brightness slider like you get with the RGB lights but as I don't really use the webGUI it's not a huge issue.
Create an account, log in here. You will receive points by participating in discussions.
Join this discussion.

Install Elektroda application

Didn't find an answer? Ask Artificial Intelligence

*I agree to send the question to OpenAI, Anthropic PBC, Perplexity AI, Inc., Kagi Inc., Google LLC - owners of language models in order to prepare the best response. The companies may monitor and log information entered into the form.

*I agree to publicly display my question and answer. The question and answer will be publicly available to everyone. The process may take a few minutes. Upon completion, you will be redirected to the page with the answer.

Wait...(2min)

Reply Cool? Ranking DIY | New topic

Notify about new articles

📢 Listen (AI):

Report a violation of the law

Home page
/
Forum
/
Smart Home
/
Smart Home IoT
/
Smart Home Devices
/
Mirabella Genio Wi-Fi LED USB Desk Lamp With Wireless Charger - Teardown

FAQ

TL;DR: For OpenBeken users fixing this WB3S lamp, the working setup used 3 mapped dpIDs and one crucial change: "Flag 8 fixed the problem." It solves the common issue where Mirabella Genio desk lamp buttons still work after flashing, but web controls fail for power, brightness, or color temperature. [#20817475]

Why it matters: This thread shows that TuyaMCU mapping errors can mimic firmware failure, even when the hardware and physical controls are still working.

Configuration path	Observed result	Specific detail
Initial profile.json assumption	Incorrect mapping	dpID 1 looked like enum mode in the profile
Raw OBK log analysis	Better mapping clues	dpID 1 behaved as bool on/off
Added `tuyaMcu_defWiFiState 4` only	Not enough alone	Device still did not respond correctly
Added Flag 8 with revised mapping	Working control	Power, brightness, and temperature started working

Key insight: Trust the live OBK/TuyaMCU logs over the original profile when they disagree. On this lamp, the breakthrough came from remapping dpIDs from real traffic and then enabling Flag 8. [#20817475]

Quick Facts

Mirabella Genio Wi-Fi LED USB Desk Lamp with wireless charger, model I003867, used a WB3S BK7231T module with TuyaMCU. [#20804782]
The lamp was bought from Bunnings Warehouse for $29.95 AUD, and the poster noted it appeared to be end-of-line stock. [#20804782]
Working light control used dpID 1 = bool power, dpID 3 = value, and dpID 4 = value, with tuyaMcu_setDimmerRange 0 255. [#20817475]
Logged brightness values ranged from 25 to 255, while the timer button set auto-off after 40 minutes but produced no visible log entry. [#20804782]

How do I configure OpenBeken for the Mirabella Genio Wi-Fi LED USB Desk Lamp with wireless charger using the WB3S BK7231T and TuyaMCU?

Use TuyaMCU with three mapped channels and a 0–255 dimmer range. The working setup was:

startDriver TuyaMCU and tuyaMcu_defWiFiState 4
Set channel 1 as Toggle, channels 3 and 4 as Dimmers
Link dpID 1, 3, and 4, then enable Flag 8

The final mapping used linkTuyaMCUOutputToChannel 1 1 1, 3 2 3, and 4 2 4. That configuration fixed power, brightness, and temperature control on this WB3S BK7231T lamp. [#20817475]

What is TuyaMCU, and how does it control brightness and color temperature in a desk lamp like the Mirabella Genio I003867?

TuyaMCU is the controller that actually drives the lamp functions while the Wi-Fi module passes commands. "TuyaMCU is a secondary microcontroller that handles device features over a serial protocol, while the Wi‑Fi module acts mainly as a network bridge and command sender." In this lamp, the thread showed physical buttons still changed on/off, brightness, and color temperature even when the web GUI mapping was wrong. The observed control values came through dpIDs, especially dpID 3 and dpID 4, with logged values such as 25, 127, and 255. [#20804782]

What is a dpID in TuyaMCU devices, and how do you figure out which dpIDs map to power, brightness, and light mode?

A dpID is the numbered data point TuyaMCU uses to represent one function. "dpID is a protocol data identifier that labels a device feature, such as power or dimming, and lets the MCU report or receive that feature as bool, enum, or value data." You identify it by comparing live OBK logs to a known button press. In this lamp, pressing power produced dpID 1 as a bool, while mode and brightness activity appeared on dpID 3 and dpID 4 as value types. [#20804782]

Why do the physical buttons on my Mirabella Genio lamp still work after flashing, but the OpenBeken web GUI controls do nothing?

The physical buttons still work because TuyaMCU keeps controlling the lamp locally. The web GUI fails when OpenBeken maps the wrong dpIDs, wrong data types, or wrong scaling. That is exactly what happened here: local buttons changed light state and CCT modes, but early GUI mappings did nothing or snapped sliders back to 0. The lamp only started responding correctly after the dpIDs were remapped from live logs and Flag 8 was enabled. [#20817475]

How can I use Tuya CloudCutter and LightLeak to create a profile for a WB3S-based Tuya device?

Use LightLeak to build a CloudCutter profile from the target device and then test that profile against real traffic. The poster created a CloudCutter profile for this WB3S lamp using LightLeak and linked the resulting profile.json. That profile helped start the analysis, but it did not fully match the lamp’s real TuyaMCU behavior. For this device, the final working mapping came from OBK log analysis rather than trusting the original profile alone. [#20804782]

Why does the Mirabella Genio lamp report dpID 1 as a bool in OBK logs when the original profile.json suggested dpID 1 was an enum light mode?

Because the live device traffic contradicted the earlier profile guess. The profile suggested dpID 1 was an enum with modes like breathe, nature, read, and night. But the OBK logs showed power button presses generating dpId 1, dataType 1-DP_TYPE_BOOL with a 1-byte value. That means this lamp’s real implementation used dpID 1 for on/off, not for mode selection. In practice, the logs were the more reliable source for mapping. [#20804782]

What do the TuyaMCU log messages like "Consumed unwanted non-header byte" and long runs of 00 bytes mean when dimming this lamp?

They indicate extra serial data that OpenBeken could not parse as a valid TuyaMCU frame header. In this lamp, holding the dimming control produced repeated runs of 00 bytes, including blocks of 256, 103, 52, 52, and 15 unwanted bytes before a valid command 7 frame appeared again. That suggests the device emitted noisy or non-framed serial traffic during continuous dimming. It did not mean the lamp was dead; it meant the parser only trusted properly framed packets. [#20804782]

How should I set up linkTuyaMCUOutputToChannel and tuyaMcu_setDimmerRange for a TuyaMCU lamp that uses separate values for brightness and color temperature?

Map each value-type dpID to its own dimmer channel and use the range the device actually reports. This lamp worked with tuyaMcu_setDimmerRange 0 255, channel 1 as Toggle, and channels 3 and 4 as Dimmers. The final links were dpID 1 to channel 1, dpID 3 to channel 3, and dpID 4 to channel 4. Earlier use of a 0–1000 range did not produce stable control. The practical rule is simple: match the live value range before tuning the UI. [#20817475]

What does tuyaMcu_defWiFiState 4 do, and why do some TuyaMCU devices need a forced paired Wi-Fi state before they respond properly?

It forces the device to report Wi-Fi state 4, which represents a paired state expected by some TuyaMCU designs. One responder stated, "Some TuyaMCU devices needs to be 'paired' first before using." That matters because certain MCUs ignore or limit remote commands until they believe the Wi-Fi side is already paired. On this lamp, adding tuyaMcu_defWiFiState 4 alone did not fully fix control, but it was still part of the final working configuration. [#20813016]

Why did enabling Flag 8 fix the power, brightness, and temperature control issues on this Mirabella Genio desk lamp?

Enabling Flag 8 fixed the final communication or interpretation mismatch between OpenBeken and this lamp’s TuyaMCU behavior. After the user applied the revised dpID mapping and tuyaMcu_defWiFiState 4, power, brightness, and temperature still had issues. Turning on Flag 8 resolved those remaining problems, and the poster then reported the device was working. The thread does not explain the internal Flag 8 behavior, but it clearly documents the result on this exact lamp. [#20817475]

What is the difference between dpID value channels used for brightness and those used for color temperature on TuyaMCU lighting devices?

Brightness changes light intensity, while color-temperature channels change the warm-to-cool mix. In this lamp, dpID 3 consistently carried brightness-style values such as 25, 246, and 255 during dimming tests. dpID 4 changed between 0, 127, and 255 as the mode button cycled warm/orange, warm/white, and cool light. That behavior showed two separate value channels: one for level and one for CCT position. [#20804782]

How does OpenBeken web GUI control for a CCT desk lamp compare with the RGB-style brightness and temperature sliders users expect?

It works, but it is less polished than the RGB-style controls users usually expect. The poster noted the lamp became functional, yet the web GUI still lacked the dedicated brightness and temperature sliders familiar from RGB lights. Before the fix, the sliders also snapped back to 0 even though the actual brightness or temperature stayed changed. After the fix, control was usable, but updates could still feel a bit slow. [#20817475]

What troubleshooting steps should I try when TuyaMCU Analyzer returns nothing or gives incomplete results from my OBK logs?

Start with raw log correlation instead of relying only on the analyzer. 1. Press one physical button at a time and capture the exact dpID, type, and value. 2. Compare repeated states like power, cool, warm, and dim levels. 3. Rebuild the mapping from those logs, then test tuyaMcu_defWiFiState 4 and Flag 8. In this case, the analyzer initially returned nothing useful, but manual log reading still exposed dpID 1, 3, and 4 well enough to finish the setup. [#20817475]

How can I identify the timer function on a TuyaMCU lamp when holding the timer button changes behavior but produces no visible log entries?

Identify it by testing behavior externally, because this lamp’s timer button produced no visible TuyaMCU log entry. The thread states that holding the timer button set auto-off after 40 minutes, yet nothing new appeared in the logs. That creates an edge case: the timer may use local logic, a hidden MCU path, or an event the current parser does not expose. If logs stay blank, measure the outcome by elapsed time instead of waiting for a dpID. [#20804782]

Where was the Mirabella Genio Wi-Fi LED USB Desk Lamp with wireless charger sold, how much did it cost, and what should I look for if it appears to be discontinued?

It was sold by Bunnings Warehouse for $29.95 AUD, and the poster believed remaining units were last stock. If it appears discontinued, look for the exact Mirabella Genio desk lamp with wireless charger model I003867 and confirm the module is WB3S BK7231T before planning an OpenBeken conversion. That hardware detail matters more than the retail listing because TuyaMCU mapping depends on the actual board inside the lamp. [#20804782]