The AVATTO (RoomsAI) two-gang switch (_TZ3000_ogpla3lh) stopped exporting the "power-on behavior" sensor.

What happened?

I have several AVATTO (RoomsAI) switches with 1, 2, or 3 gangs.
They have all always reported the "power-on behavior" attribute.
It is an important attribute.

The 1-gang and 3-gang switches continue to report the attribute, but the two-gang switch no longer displays it (it was dropped in a Zigbee2MQTT update).

What did you expect to happen?

I would like the device to report this attribute again, as it is important for my automations.

How to reproduce it (minimal and precise)

You need to have the device and install it in Z2M. The "power-on behavior" attribute does not appear as published in Z2M, even though it shows up in the "state".

Zigbee2MQTT version

2.12.0

Adapter firmware version

EmberZNet 8.0.2 [GA]

Adapter

Sonoff Dongle E - amber

Setup

Raspberry Py 4b
Sonoff Zigbee Dongle E

Device database.db entry

{"id":23,"type":"Router","ieeeAddr":"0xa4c138e28e958a91","nwkAddr":47563,"manufId":4417,"manufName":"_TZ3000_ogpla3lh","powerSource":"Mains (single phase)","modelId":"TS0002","epList":[1,2,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":256,"inClusterList":[3,4,5,6,57344,57345,0],"outClusterList":[25,10],"clusters":{"57344":{"attributes":{"53251":"AAAAAgAA"}},"genBasic":{"attributes":{"65503":"E��1\u0012","65506":56,"65508":0,"65534":0,"stackVersion":0,"dateCode":"","manufacturerName":"_TZ3000_ogpla3lh","zclVersion":3,"appVersion":83,"modelId":"TS0002","powerSource":1}},"genOnOff":{"attributes":{"onOff":1,"onTime":0,"offWaitTime":0,"tuyaBacklightMode":2,"moesStartUpOnOff":0,"tuyaBacklightSwitch":1}},"manuSpecificTuya3":{"attributes":{"powerOnBehavior":0,"switchType":1}}},"binds":[{"cluster":6,"type":"endpoint","deviceIeeeAddress":"0xe8e07efffeace055","endpointID":1}],"configuredReportings":[],"meta":{}},"2":{"profId":260,"epId":2,"devId":256,"inClusterList":[4,5,6,57345],"outClusterList":[],"clusters":{"genOnOff":{"attributes":{"onOff":0,"onTime":0,"offWaitTime":0}},"manuSpecificTuya3":{"attributes":{"powerOnBehavior":0}}},"binds":[{"cluster":6,"type":"endpoint","deviceIeeeAddress":"0xe8e07efffeace055","endpointID":1}],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":83,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{"configured":"0.0.0"},"lastSeen":1782338207838}

Debug log

Zigbee State Report:

{
"backlight_mode": "ON",
"countdown_l1": 0,
"countdown_l2": 0,
"device": {
"applicationVersion": 83,
"dateCode": "",
"friendlyName": "Interruptor escritório 2 canais",
"hardwareVersion": 1,
"ieeeAddr": "0xa4c138e28e958a91",
"manufacturerID": 4417,
"manufacturerName": "_TZ3000_ogpla3lh",
"model": "37022463-2",
"networkAddress": 47563,
"powerSource": "Mains (single phase)",
"stackVersion": 0,
"type": "Router",
"zclVersion": 3
},
"indicator_mode": "on/off",
"last_seen": "2026-06-24T22:02:19.399Z",
"linkquality": 132,
"power_on_behavior_l1": "off",
"power_on_behavior_l2": "off",
"state_l1": "ON",
"state_l2": "OFF",
"switch_type": "state"
}

Notes

The device that does not display the "power-on behavior" control (but previously did it):

Device from the same manufacturer (3-gang) that displays the control correctly:

Start by locating the device converter for manufacturer _TZ3000_ogpla3lh and model TS0002, then compare its two-gang exposure with the reported power_on_behavior_l1 and power_on_behavior_l2 state fields and the working three-gang device. Reproduce the device in Zigbee2MQTT and verify that both power-on behavior controls are published and remain available in the resulting state.