Upgrade to v4.1.0

General
21

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 ?

22

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.

23

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 ?

24

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 :joy:

1 Like
25

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.

26

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

27

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

listener 1883
allow_anonymous true

I also add

# 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

28

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

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

image
image447×113 1.79 KB

29

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.