# zigbee2mqtt error message

**URL:** <https://community.gladysassistant.com/t/message-derreur-zigbee2mqtt/6846>\
**Category:** Configuration\
**Created:** [January 23, 2022, 9:15pm UTC](https://community.gladysassistant.com/t/message-derreur-zigbee2mqtt/6846 "2022-01-23T21:15:21Z")\
**Posts on this page:** 1\
**Page:** 6

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [October 14, 2022, 5:02am UTC](https://community.gladysassistant.com/t/message-derreur-zigbee2mqtt/6846/102 "2022-10-14T05:02:28Z")

</div>

> [@lmilcent](#):
>
> When deleting / re-creating the wireless button (which very, very heavily slowed down my Raspberry Pi system):
> 
> - We can see that it is indeed `node` that uses the majority of the disk (and the monitoring agent `netdata` that adds to it, but that’s personal, outside Gladys)

Hi everyone!

I’m coming back to this topic — I’ve developed a fix for this limitation so it will be clearer in the future 🙂

When deleting a device with many states, the user will see this kind of message:

 ![Screenshot 2022-10-14 at 11.57.50](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/3/32aa4181907958a5e5c93f681ae9dc894ffdd69e.jpeg)

The PR:

> <https://github.com/GladysAssistant/Gladys/pull/1620>
>
> \### Pull Request check-list
> 
> To ensure your Pull Request can be accepted as fa…st as possible, make sure to review and check all of these items:
> 
> \- \[x\] If your changes affects code, did your write the tests?
> \- \[x\] Are tests passing? (\`npm test\` on both front/server)
> \- \[x\] Is the linter passing? (\`npm run eslint\` on both front/server)
> \- \[x\] Did you run prettier? (\`npm run prettier\` on both front/server)
> \- \[x\] If you are adding a new features/services, did you run integration comparator? (\`npm run compare-translations\` on front)
> \- \[x\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to \[the community\](https://community.gladysassistant.com/) for testing before merging.
> \- \[x\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)
> \- \[x\] If you are adding a new features/services which needs explanation, did you modify the user documentation? See \[the GitHub repo\](https://github.com/GladysAssistant/v4-website) and the \[website\](https://gladysassistant.com).
> \- \[x\] Did you add fake requests data for the demo mode (\`front/src/config/demo.js\`) so that the demo website is working without a backend? (if needed) See \[https://demo.gladysassistant.com\](https://demo.gladysassistant.com).
> 
> NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
> 
> \### Description of change
> 
> \<img width="1512" alt="Screenshot 2022-10-14 at 11 57 50" src="https://user-images.githubusercontent.com/7365207/195765766-7e075905-14a3-48e9-99a0-69eb73917388.png"\>

[Previous page](https://community.gladysassistant.com/t/message-derreur-zigbee2mqtt/6846.md?page=5)