Thanks for your feedback frits.
This is what I found searching this forum and already replied to my own post, but it takes some time the post to become visible.

With best regards
Alberto

@frits: if the MQTT GW do not support the dynamic ID assignement, then what happened to my other sensors (those based on the Nano) They got the Node_IDs from the GW. All the sensors are on the same GW.

@frits : This is my first GW, but during my early experiments I run it as an Ethernet GW, then I reconfigured to MQTT.
Currently I don't have a controller running but I'm using Node-Red + Influx-DB + Grafana.

So probably during these first experiments, while in Ethernet mode, the Node_IDs were distributed.
I will erase the EEPROMs by the next opportunity and will check the behaviour of my Nano sensors after re-boot.

Thanks for your explanation frits, it helped me to learn more about MySensors.

@frits : This is my first GW, but during my early experiments I run it as an Ethernet GW, then I reconfigured to MQTT.
Currently I don't have a controller running but I'm using Node-Red + Influx-DB + Grafana.

So probably during these first experiments, while in Ethernet mode, the Node_IDs were distributed.
I will erase the EEPROMs by the next opportunity and will check the behaviour of my Nano sensors after re-boot.

Thanks for your explanation frits, it helped me to learn more about MySensors.

@frits: if the MQTT GW do not support the dynamic ID assignement, then what happened to my other sensors (those based on the Nano) They got the Node_IDs from the GW. All the sensors are on the same GW.

Thanks! this made the change. Now the ID is 25 as intended.
But how to explain that a Node_ID of 3 was set, when the #define statement was after the MySensors?

I also tried with the static Node_ID 24, there was no change in the behaviour. Then I tried with 25 and it is working now.

#define MY_RADIO_RF24

#include <MySensors.h>

#define MY_NODE_ID 25
#define OPEN 1
#define CLOSE 0

But the Node_ID seems to be 3 and not 25.

16 MCO:BGN:INIT NODE,CP=RNNNA---,FQ=8,REL=255,VER=2.3.2
28 TSM:INIT
28 TSF:WUR:MS=0
36 TSM:INIT:TSP OK
38 TSF:SID:OK,ID=3
40 TSM:FPAR
45 ?TSF:MSG:SEND,3-3-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
653 TSF:MSG:READ,0-0-3,s=255,c=3,t=8,pt=1,l=1,sg=0:0
659 TSF:MSG:FPAR OK,ID=0,D=1
2054 TSM:FPAR:OK
2054 TSM:ID
2056 TSM:ID:OK
2058 TSM:UPL
2062 TSF:MSG:SEND,3-3-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
2070 TSF:MSG:READ,0-0-3,s=255,c=3,t=25,pt=1,l=1,sg=0:1
2076 TSF:MSG:PONG RECV,HP=1
2078 TSM:UPL:OK
2080 TSM:READY:ID=3,PAR=0,DIS=1
2086 TSF:MSG:SEND,3-3-0-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
2095 TSF:MSG:READ,0-0-3,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
2103 TSF:MSG:SEND,3-3-0-0,s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=OK:2.3.2
2111 TSF:MSG:SEND,3-3-0-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=OK:0
2164 TSF:MSG:READ,0-0-3,s=255,c=3,t=6,pt=0,l=1,sg=0:M
2172 TSF:MSG:SEND,3-3-0-0,s=5,c=0,t=0,pt=0,l=0,sg=0,ft=0,st=OK:
2181 MCO:REG:REQ

Is there a kind of offeset in the ID?

Alberto

I successfully implemented a MQTT gateway on a PI and my Nano based sensors are working fine.

As a next step I'm trying to build a Pro mini 3.3 V based sensor.
However the allocation of the node id seems not to work.
The protocol received on the serial interface of the Pro mini looks always like this:

 __  __       ____
|  \/  |_   _/ ___|  ___ _ __  ___  ___  _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| |  | | |_| |___| |  __/ | | \__ \  _  | |  \__ \
|_|  |_|\__, |____/ \___|_| |_|___/\___/|_|  |___/
        |___/                      2.3.2

16 MCO:BGN:INIT NODE,CP=RNNNA---,FQ=8,REL=255,VER=2.3.2
28 TSM:INIT
28 TSF:WUR:MS=0
36 TSM:INIT:TSP OK
38 TSM:FPAR
40 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
339 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0
346 TSF:MSG:FPAR OK,ID=0,D=1
2050 TSM:FPAR:OK
2050 TSM:ID
2052 TSM:ID:REQ
2056 TSF:MSG:SEND,255-255-0-0,s=4,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
4063 TSM:ID
4063 TSM:ID:REQ
4067 TSF:MSG:SEND,255-255-0-0,s=223,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
6074 TSM:ID
6074 TSM:ID:REQ
6078 TSF:MSG:SEND,255-255-0-0,s=186,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
8085 TSM:ID
8085 TSM:ID:REQ
8089 TSF:MSG:SEND,255-255-0-0,s=149,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
10096 !TSM:ID:FAIL
10098 TSM:FAIL:CNT=1
10100 TSM:FAIL:DIS
10102 TSF:TDI:TSL
20105 TSM:FAIL:RE-INIT
20107 TSM:INIT
20113 TSM:INIT:TSP OK
20115 TSM:FPAR
20119 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
21071 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0
21078 TSF:MSG:FPAR OK,ID=0,D=1
22128 TSM:FPAR:OK
22130 TSM:ID
22130 TSM:ID:REQ
22134 TSF:MSG:SEND,255-255-0-0,s=114,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
24143 TSM:ID
24143 TSM:ID:REQ
24147 TSF:MSG:SEND,255-255-0-0,s=79,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
26157 TSM:ID
26157 TSM:ID:REQ
26161 TSF:MSG:SEND,255-255-0-0,s=45,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
28170 TSM:ID
28170 TSM:ID:REQ
28174 TSF:MSG:SEND,255-255-0-0,s=10,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
30183 !TSM:ID:FAIL
30185 TSM:FAIL:CNT=2

I tried with a new upload of the code, but the results is always the same.
(As mentioned above the other sensors are working fine).

Is there something else I have to consider, while using a Pro mini instead of a Nano?
Thanks in advance for your feedback.

Alberto

Thanks for your feedback frits.
This is what I found searching this forum and already replied to my own post, but it takes some time the post to become visible.

With best regards
Alberto

Solved.

I found the rootcause of my problem by reading one of the posts on MQTT GW issues with sending MQTT msg.
By adding the "#" in the topic definition of my MQTT node in Node red, I can see all messages now
and have just to sort them out based on the sub topics.

WBR
Alberto

Hello,

I'm Alberto and I'm new to this forum, so first of all I would like thank all of you for your excellent contributions I found in this forum which helped mit to start with MySensers. THANK YOU!

I'm using a Rasberry Pi for my IOT. I already implemented the Mosquito MQTT, Node red, Infulx and Graphana and was able to work with my ESP32 based sensors and all is working fine. Then I thought about using sensors with much lower power consumption than the EPS32 and besides ZigBee I came to rf24.

I implemented MySensors GW in MQTT mode on a second PI (as long as I'm in this experimental stage, I'm trying to avoid problems with my first Pi ).
As test sensors, I implemented the DOOR script from the MySensors API description on two Arduinos Nano, just to have something providing some data.

I was albe to confirm that the communication between the GW and the Sensors is working fine, by means of MYScontroller from tekka as well as by MyController.org from jkandasa (many thanks to these guys).

Now, I’m trying to forward the data received by the GW, to my first PI, where the Mosquito MQTT broker an Node Red is running. I did this in the same way as for my other ESP32 sensors using the MQTT node and just the debug node to see when something was received, but nothing is coming.

The connection from the MySensors GW to MQTT is working fine. I see the confirmation that the GW is connected

Nov 08 11:15:19 DEBUG GWT:RMQ:CONNECTING...
Nov 08 11:15:19 DEBUG connected to 192.168.XX.YY
Nov 08 11:15:19 DEBUG GWT:RMQ:OK
Nov 08 11:15:19 DEBUG GWT:TPS:TOPIC=mysensors-out/0/255/0/0/18,MSG SENT
Nov 08 11:15:19 DEBUG TSM:READY:NWD REQ

and I see that the data was send out:

Nov 08 11:23:04 DEBUG TSF:MSG:READ,1-1-0,s=5,c=1,t=16,pt=1,l=1,sg=0:0
Nov 08 11:23:04 DEBUG GWT:TPS:TOPIC=mysensors-out/1/5/1/0/16,MSG SENT
Nov 08 11:23:16 DEBUG TSF:MSG:READ,1-1-0,s=5,c=1,t=16,pt=1,l=1,sg=0:1
Nov 08 11:23:16 DEBUG GWT:TPS:TOPIC=mysensors-out/1/5/1/0/16,MSG SENT
Nov 08 11:23:27 DEBUG TSF:MSG:READ,1-1-0,s=5,c=1,t=16,pt=1,l=1,sg=0:0
Nov 08 11:23:27 DEBUG GWT:TPS:TOPIC=mysensors-out/1/5/1/0/16,MSG SENT

but nothing seems to arrive on the MQTT node. I verified the node red flow using MQTT.fx-1.7.1 and send the same commands (using mysensors-out as topic) by hand to my MQTT broker and this is working fine.

Maybe my understanding of how the MySensors GW is working is completely wrong and hence what I am trying to do will not work.
So I would be glad if someone from you could help me to solve this riddle an point me to my error. Many thanks in advance.

With best regards
Alberto