# 🎉 Node-RED 3.1.0-beta.4 released

**URL:** <https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091>\
**Category:** News\
**Created:** [26 July 2023 16:33 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091 "2023-07-26T16:33:51Z")\
**Posts on this page:** 1\
**Showing post:** 44

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [21 August 2023 13:30 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/44 "2023-08-21T13:30:41Z")

</div>

I think I have got it.  
Somehow the problematic mqtt config node has acquired a new option in flows.json  
`"autoUnsubscribe": true,`  
Deleting those lines from flows.json and restarting node-red clears the problem, at least until they re-appear.

I will raise an issue.

---

_[View the full topic](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091)._