Freeze cc2531 greenpower end point

Hello,
excuse me for my expression i’m not english man
So i have a probleme on my zigbee network.
i use with my Jeedom on RPI4 a cc2531 dongle in coordinator zstack3.0
a Xiaomi door sensor
a hue bulb
and 4 green power switch build arround PTM535z from Dolphin Enocean
When i play quickly with a green power switch, thz cc2531 dongle don’t respond and freeze.
What is the problem?
Best Regards

root@raspberrypi:/opt/zigbee2mqtt# npm start

zigbee2mqtt@1.14.4 start /opt/zigbee2mqtt
node index.js

Zigbee2MQTT:info 2020-09-30 15:00:12: Logging to console and directory: ‘/opt/zigbee2mqtt/data/log/2020-09-30.15-00-12’ filename: log.txt
Zigbee2MQTT:info 2020-09-30 15:00:13: Starting Zigbee2MQTT version 1.14.4 (commit #0cd4607)
Zigbee2MQTT:info 2020-09-30 15:00:13: Starting zigbee-herdsman…
Zigbee2MQTT:info 2020-09-30 15:00:18: zigbee-herdsman started
Zigbee2MQTT:info 2020-09-30 15:00:18: Coordinator firmware version: ‘{“meta”:{“maintrel”:2,“majorrel”:2,“minorrel”:7,“product”:2,“revision”:20190425,“transportrev”:2},“type”:“zStack30x”}’
Zigbee2MQTT:info 2020-09-30 15:00:18: Currently 7 devices are joined:
Zigbee2MQTT:info 2020-09-30 15:00:18: 0x00158d0002a12567 (0x00158d0002a12567): Not supported (Router)
Zigbee2MQTT:info 2020-09-30 15:00:18: 0x00158d00046561a9 (0x00158d00046561a9): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
Zigbee2MQTT:info 2020-09-30 15:00:18: 0x001788010412c49e (0x001788010412c49e): 8718696449691 - Philips Hue White Single bulb B22 (Router)
Zigbee2MQTT:info 2020-09-30 15:00:18: 0x0000000001520120 (0x0000000001520120): GreenPower_7 - GreenPower device 7 (GreenPower)
Zigbee2MQTT:info 2020-09-30 15:00:18: 0x00000000015062ba (0x00000000015062ba): GreenPower_On_Off_Switch - GreenPower On/off switch (GreenPower)
Zigbee2MQTT:info 2020-09-30 15:00:18: 0x0000000001512d98 (0x0000000001512d98): GreenPower_On_Off_Switch - GreenPower On/off switch (GreenPower)
Zigbee2MQTT:info 2020-09-30 15:00:18: 0x0000000001512d9d (0x0000000001512d9d): GreenPower_On_Off_Switch - GreenPower On/off switch (GreenPower)
Zigbee2MQTT:warn 2020-09-30 15:00:18: permit_join set to true in configuration.yaml.
Zigbee2MQTT:warn 2020-09-30 15:00:18: Allowing new devices to join.
Zigbee2MQTT:warn 2020-09-30 15:00:18: Set permit_join to false once you joined all devices.
Zigbee2MQTT:info 2020-09-30 15:00:18: Zigbee: allowing new devices to join.
Zigbee2MQTT:info 2020-09-30 15:00:18: Connecting to MQTT server at mqtt://localhost:1883
Zigbee2MQTT:info 2020-09-30 15:00:18: Connected to MQTT server
Zigbee2MQTT:info 2020-09-30 15:00:18: MQTT publish: topic ‘zigbee2mqtt/bridge/state’, payload ‘online’
Zigbee2MQTT:info 2020-09-30 15:00:18: MQTT publish: topic ‘zigbee2mqtt/0x00158d00046561a9’, payload ‘{“battery”:100,“contact”:false,“linkquality”:84,“voltage”:3015}’
Zigbee2MQTT:info 2020-09-30 15:00:18: MQTT publish: topic ‘zigbee2mqtt/0x001788010412c49e’, payload ‘{“brightness”:0,“linkquality”:84,“state”:“OFF”}’
Zigbee2MQTT:info 2020-09-30 15:00:18: MQTT publish: topic ‘zigbee2mqtt/0x0000000001520120’, payload ‘{“linkquality”:86}’
Zigbee2MQTT:info 2020-09-30 15:00:18: MQTT publish: topic ‘zigbee2mqtt/0x00000000015062ba’, payload ‘{“linkquality”:84}’
Zigbee2MQTT:info 2020-09-30 15:00:18: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d98’, payload ‘{“linkquality”:84}’
Zigbee2MQTT:info 2020-09-30 15:00:18: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“linkquality”:92}’
Zigbee2MQTT:info 2020-09-30 15:00:18: MQTT publish: topic ‘zigbee2mqtt/bridge/config’, payload ‘{“commit”:“0cd4607”,“coordinator”:{“meta”:{“maintrel”:2,“majorrel”:2,“minorrel”:7,“product”:2,“revision”:20190425,“transportrev”:2},“type”:“zStack30x”},“log_level”:“info”,“network”:{“channel”:11,“extendedPanID”:“0x00124b0019368b75”,“panID”:6754},“permit_join”:true,“version”:“1.14.4”}’
Zigbee2MQTT:info 2020-09-30 15:01:47: MQTT publish: topic ‘zigbee2mqtt/0x001788010412c49e’, payload ‘{“brightness”:0,“linkquality”:73,“state”:“OFF”}’
Zigbee2MQTT:info 2020-09-30 15:01:47: MQTT publish: topic ‘zigbee2mqtt/0x001788010412c49e’, payload ‘{“brightness”:41,“linkquality”:73,“state”:“ON”}’
Zigbee2MQTT:info 2020-09-30 15:01:51: MQTT publish: topic ‘zigbee2mqtt/0x001788010412c49e’, payload ‘{“brightness”:0,“linkquality”:73,“state”:“OFF”}’
Zigbee2MQTT:info 2020-09-30 15:02:08: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“action”:“toggle”,“linkquality”:84}’
Zigbee2MQTT:info 2020-09-30 15:02:09: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“action”:“release”,“linkquality”:81}’
Zigbee2MQTT:info 2020-09-30 15:02:19: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“action”:“toggle”,“linkquality”:86}’
Zigbee2MQTT:info 2020-09-30 15:02:20: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“action”:“release”,“linkquality”:84}’
Zigbee2MQTT:info 2020-09-30 15:02:21: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“action”:“toggle”,“linkquality”:84}’
Zigbee2MQTT:info 2020-09-30 15:02:21: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“action”:“release”,“linkquality”:84}’
Zigbee2MQTT:info 2020-09-30 15:02:22: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“action”:“toggle”,“linkquality”:84}’
Zigbee2MQTT:info 2020-09-30 15:02:22: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“action”:“release”,“linkquality”:84}’
Zigbee2MQTT:info 2020-09-30 15:02:45: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“action”:“toggle”,“linkquality”:86}’
Zigbee2MQTT:info 2020-09-30 15:02:48: MQTT publish: topic ‘zigbee2mqtt/0x0000000001512d9d’, payload ‘{“action”:“release”,“linkquality”:86}’
Zigbee2MQTT:error 2020-09-30 15:03:32: Publish ‘set’ ‘state’ to ‘0x001788010412c49e’ failed: ‘Error: Command 0x001788010412c49e/11 genOnOff.on({}, {“timeout”:10000,“disableResponse”:false,“disableDefaultResponse”:false,“direction”:0,“srcEndpoint”:null,“reservedBits”:0,“manufacturerCode”:null,“transactionSequenceNumber”:null}) failed (Data request failed with error: ‘MAC no resources’ (26))’
Zigbee2MQTT:info 2020-09-30 15:03:32: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{“message”:“Publish ‘set’ ‘state’ to ‘0x001788010412c49e’ failed: ‘Error: Command 0x001788010412c49e/11 genOnOff.on({}, {“timeout”:10000,“disableResponse”:false,“disableDefaultResponse”:false,“direction”:0,“srcEndpoint”:null,“reservedBits”:0,“manufacturerCode”:null,“transactionSequenceNumber”:null}) failed (Data request failed with error: ‘MAC no resources’ (26))’”,“meta”:{“friendly_name”:“0x001788010412c49e”},“type”:“zigbee_publish_error”}’
(node:31909) UnhandledPromiseRejectionWarning: Error: SREQ ‘–> ZDO - mgmtPermitJoinReq - {“addrmode”:15,“dstaddr”:65532,“duration”:254,“tcsignificance”:0}’ failed with status ‘(0x10: MEM_ERROR)’ (expected ‘(0x00: SUCCESS)’)
at Znp. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:291:27)
at Generator.next ()
at fulfilled (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:24:58)
(node:31909) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:31909) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Zigbee2MQTT:error 2020-09-30 15:03:42: Publish ‘set’ ‘state’ to ‘0x001788010412c49e’ failed: ‘Error: Command 0x001788010412c49e/11 genOnOff.off({}, {“timeout”:10000,“disableResponse”:false,“disableDefaultResponse”:false,“direction”:0,“srcEndpoint”:null,“reservedBits”:0,“manufacturerCode”:null,“transactionSequenceNumber”:null}) failed (Data request failed with error: ‘MAC no resources’ (26))’
Zigbee2MQTT:info 2020-09-30 15:03:42: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{“message”:“Publish ‘set’ ‘state’ to ‘0x001788010412c49e’ failed: ‘Error: Command 0x001788010412c49e/11 genOnOff.off({}, {“timeout”:10000,“disableResponse”:false,“disableDefaultResponse”:false,“direction”:0,“srcEndpoint”:null,“reservedBits”:0,“manufacturerCode”:null,“transactionSequenceNumber”:null}) failed (Data request failed with error: ‘MAC no resources’ (26))’”,“meta”:{“friendly_name”:“0x001788010412c49e”},“type”:“zigbee_publish_error”}’
^CZigbee2MQTT:info 2020-09-30 15:04:00: MQTT publish: topic ‘zigbee2mqtt/bridge/state’, payload ‘offline’
Zigbee2MQTT:info 2020-09-30 15:04:00: Disconnecting from MQTT server
Zigbee2MQTT:error 2020-09-30 15:04:00: Failed to stop zigbee

I think only this part is interessant, but i don’t understand where is the problem

(node:1572) UnhandledPromiseRejectionWarning: Error: SREQ ‘–> ZDO - mgmtPermitJoinReq - {“addrmode”:15,“dstaddr”:65532,“duration”:254,“tcsignificance”:0}’ failed with status ‘(0x10: MEM_ERROR)’ (expected ‘(0x00: SUCCESS)’)
at Znp. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:291:27)
at Generator.next ()
at fulfilled (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:24:58)
(node:1572) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1572) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

that is the answer in the terminal during the freeze