# Upgrade to v4.1.0

**URL:** <https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395>\
**Category:** General\
**Created:** [30 July 2025 15:33 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395 "2025-07-30T15:33:27Z")\
**Posts on this page:** 10\
**Page:** 2

<div class="post-metadata">

**Author:** ![Tany](https://avatars.discourse-cdn.com/v4/letter/t/dfb087/32.png) [@Tany](https://discourse.nodered.org/u/Tany)\
**Post date:** [2 August 2025 07:59 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395/21 "2025-08-02T07:59:58Z")

</div>

Back on the wailing wall…  
all higher described updates look ok, but NR zigbee2mqtt-nodes cannot retrieve zigbee device list.  
NR v4.1.0, Z2M v2.5.1, contrib-aedes v0.15.0, contrib-zigbee2mqtt v2.7.5  
AEDES : interacting with ESP32  
WindFront (UI of Z2M) : all devices visible and can be controlled  
node bridge : online  
node out : no device

Do i open a new topic ?

---

<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:** [2 August 2025 08:22 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395/22 "2025-08-02T08:22:10Z")

</div>

Don't bother with the zigbee2mqtt nodes, just use the normal mqtt nodes. There is no need to use an additional contrib node that doesn't really add anything useful.

---

<div class="post-metadata">

**Author:** ![Tany](https://avatars.discourse-cdn.com/v4/letter/t/dfb087/32.png) [@Tany](https://discourse.nodered.org/u/Tany)\
**Post date:** [2 August 2025 09:33 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395/23 "2025-08-02T09:33:57Z")

</div>

They say AI is the sound of the future, but IA is the sound of a… donkey !  
3 AI platforms have doubts on the version compatibility of the contribs. Z2M is a major upgrade, and aedes also refreshed recently.  
My mentor teached… less is more.  
So i took your advice and tested with in/out aedes nodes. Works.  
Meaning i completely uninstall contrib-z2m ? no other hick-ups to expect ?  
And about the greengolfer-suggestion of going mosquito ?  
AEDES is native NR and stable, so why make laaif complicate ? Or am i missing something ?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [2 August 2025 09:45 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395/24 "2025-08-02T09:45:26Z")

</div>

> [@Tany](#):
>
> AEDES is native NR and stable, so why make laaif complicate ? Or am i missing something

Yes. Aedes runs in the same single thread as node-red so there are times when delays can occur due to blocking requests. Also, no Mqtt v5 features, connection drops when you deploy. Loss of mqtt when node-red is restarted.

A standalone mqtt broker is also 100x faster and much more stable. But, if you are happy with how everything is working, then nothing to see here, move along 😂

---

<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:** [2 August 2025 09:48 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395/25 "2025-08-02T09:48:23Z")

</div>

> [@Tany](#):
>
> Meaning i completely uninstall contrib-z2m ?

If you have removed all the z2m nodes then yes, in Manage Palette you should be offered the Remove option. Unless the node uses a Config node, in which case check first in Configuration Nodes, click Unused at the top, and delete the z2m config node(s) first.

---

<div class="post-metadata">

**Author:** ![Tany](https://avatars.discourse-cdn.com/v4/letter/t/dfb087/32.png) [@Tany](https://discourse.nodered.org/u/Tany)\
**Post date:** [2 August 2025 13:15 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395/26 "2025-08-02T13:15:08Z")

</div>

This is interesting :

- i removed aedes broker node from the flow
- replaced all z2m nodes (in/ou() by standard mqtt in/out nodes
- deploy and restart nr
- all zigbee devices are now controllable (standard mqtt-node) from nr web socket, or with manual inject
- !!! all z2m nodes remained not branched on the flow… now show online. So comm with Mosquitto
- BUT… the flows addressing ESP32 (standard mqtt in/out AND connected) do not function anymore

With the WiFi-manager the ESP gets the static IP of the broker, which is the same as aedes. and all on 1 RPI.  
None of the topics changed id, neither in ESP nor in mqtt-node

---

<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:** [2 August 2025 13:38 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395/27 "2025-08-02T13:38:39Z")

</div>

To access the broker from remote devices you have to configure mosquitto to allow that.  
Create a file /etc/mosquitto/conf.d/mossy.conf  
The actual file name doesn't matter as long as it is .conf  
In there put

```auto
listener 1883
allow_anonymous true

```

I also add

```auto
# human readable timestamps in log
log_timestamp true
log_timestamp_format %Y-%m-%d %H:%M:%S

```

which formats the mosquitto log with readable timestamps.

Then restart mosquitto  
`sudo systemctl restart mosquitto`

Check it is running with  
`systemctl status mosquitto`

If it isn't, then look in /var/log/mosquitto.log to see why. Most likely a typo in the conf file.

Edit, sorry, the log file to look in for errors is /var/log/mosquitto/mosquitto.log

---

<div class="post-metadata">

**Author:** ![Tany](https://avatars.discourse-cdn.com/v4/letter/t/dfb087/32.png) [@Tany](https://discourse.nodered.org/u/Tany)\
**Post date:** [2 August 2025 14:00 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395/28 "2025-08-02T14:00:22Z")

</div>

hallelujaaaaa. Solved.  
I am constant in discover-mode.  
Thanks.

why are there 2 reply-buttons ? 1 individual reply and 1 to everyone ?

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/c/3caf9aad3d8717d710a35a0dae4a2e8ff5c65c19.png)

---

<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:** [2 August 2025 15:04 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395/29 "2025-08-02T15:04:40Z")

</div>

The one by the post indicates that you are replying to a particular post. The one at the bottom is for if you want to add a comment but it is not a reply to a particular post.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [31 October 2025 15:05 UTC](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395/30 "2025-10-31T15:05:09Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/upgrade-to-v4-1-0/98395.md?page=1)