### What happened?
I've executed OTA firmware update on the Xiaomi Aqara plug (…SP-EUC01). Old fw version: 09-22-2020. New version came from zigb222mqtt OTA location, version 20211206.
```
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:30: lumi.plug.maeu01: unknown key dateCode with value 09-22-2020
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:30: lumi.plug.maeu01: unknown key swBuildId with value undefined
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:30: lumi.plug.maeu01: Processed data into payload {}
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:30: Updating to latest '0x54ef441000157f54' (lumi.plug.maeu01)
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:30: Using endpoint '1'
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:30: Received Zigbee message from 'plug_002', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":32,"imageType":24,"manufacturerCode":4447}' from endpoint 1 with groupID 0
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:30: Got OTA request '{"fieldControl":0,"manufacturerCode":4447,"imageType":24,"fileVersion":32}'
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:30: ZigbeeOTA: downloaded main index
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:30: getNewImage for '0x54ef441000157f54', meta {"fileVersion":41,"fileSize":273278,"url":"https://github.com/Koenkk/zigbee-OTA/raw/master/images/Xiaomi/20211209165104_OTA_lumi.plug.maeu01_0.0.0_0041_20211206_0C22EC.ota","sha512":"3d5567a29eb7d4bacaaf823c47b66a700fb1e7b935b1d547673bcacb2ff4efacb7780e8caf72dc80f0ac942c1ec1f6964bf67cfacba359d38132b7bcfe80133b"}
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:30: ZigbeeOTA: downloading firmware image from https://github.com/Koenkk/zigbee-OTA/raw/master/images/Xiaomi/20211209165104_OTA_lumi.plug.maeu01_0.0.0_0041_20211206_0C22EC.ota
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:31: OTA update checksum validation succeeded for '0x54ef441000157f54'
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:31: getNewImage for '0x54ef441000157f54', image header {"otaUpgradeFileIdentifier":{"type":"Buffer","data":[30,241,238,11]},"otaHeaderVersion":256,"otaHeaderLength":56,"otaHeaderFieldControl":0,"manufacturerCode":4447,"imageType":24,"fileVersion":41,"zigbeeStackVersion":2,"otaHeaderString":"ROUTERX-----JN5180--ENCRYPTED000","totalImageSize":273278}
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:31: Got new image for '0x54ef441000157f54'
2022-09-01.13-13-03/log.txt:debug 2022-09-07 08:54:31: Starting upgrade
```
The upgrade completed without problems.
After that update, whenever I press the button on any IKEA E1812 or E1743, the plug toggles its state which is really undesired. It happens only when the button is connected to that plug (routed via it). Repairing the button using another router helps for a moment but as the network reconfigures itself, the buttons are again routed via the plug, so random buttons start to turn that router plug on and off. Since that plug is not solely a router but provides power to my home office, this is very annoying and made the device unusable. It didn't brick it, but the functionality became useless.
This is in the logs when I press an unrelated button routed through the plug, and switching it:
```
debug 2022-09-07 16:09:48: Received Zigbee message from 'switch_006', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info 2022-09-07 16:09:48: MQTT publish: topic 'zigbee2mqtt/switch_006', payload '{"action":"on","battery":87,"linkquality":47,"update":{"state":"idle"},"update_available":null}'
info 2022-09-07 16:09:48: MQTT publish: topic 'zigbee2mqtt/switch_006', payload '{"action":"","battery":87,"linkquality":47,"update":{"state":"idle"},"update_available":null}'
info 2022-09-07 16:09:48: MQTT publish: topic 'zigbee2mqtt/switch_006/action', payload 'on'
debug 2022-09-07 16:09:48: Received Zigbee message from '0x54ef441000157f54', type 'attributeReport', cluster 'genOnOff', data '{"245":128283218,"onOff":1}' from endpoint 1 with groupID 0
info 2022-09-07 16:09:48: MQTT publish: topic 'zigbee2mqtt/0x54ef441000157f54', payload '{"consumer_connected":false,"consumption":0,"current":0,"device_temperature":27,"energy":0,"linkquality":47,"power":0,"power_outage_count":0,"power_outage_memory":true,"state":"ON","update":{"state":null},"update_available":null,"voltage":229}'
```
I accidentally realized that these ghost switches work when zigbee2mqtt is down, ie. the plug works in a binding manner with all switching devices that are routed through it. In the meantime sensors routed through it work fine. It seems like when the firmware got upgraded to the one on the OTA server, it makes the plug and all routed switches like binded devices. It may be that the firmware is corrupt, but I have found no way to roll back. I've tried to unbind the switches that are routed through the plug via zigbee2mqtt GUI. The unbind gives a success message but the faulty behaviour remains.
Apparently happened to ohers but not too much traffic in that thread: https://community.home-assistant.io/t/aqara-plug-sp-euc01-lumi-plug-maeu01-toggles-without-reason/451671/2
### What did you expect to happen?
After the firmware upgrade the device behaviour is identical and can be switched by binded devices or via zigbee2mqtt.
### How to reproduce it (minimal and precise)
1. Get a Xiaomi Aquara plug with original firmware (mine was 09-22-2020).
2. OTA upgrade via zigbee2mqtt.
3. Make a few switches route through it in a zigbee network. I used the following:
IKEA | E1812 | 20210727 | 2.3.080
IKEA | E1743 | 20210722 | 2.3.079
5. Toggle the switch.
6. Observe that it will toggle the status of the plug.
### Zigbee2MQTT version
1.27.2
### Adapter firmware version
20220219
### Adapter
Slaesh CC2652RB
### Debug log
_No response_