Thanks for your reaction!!!
I am going to experiment with it and post proceedings later!

@mfalkvidd

Somebody has to make that mistake again!
This time it was me!

Thanks.

@mfalkvidd

I did some tests.
I put a byte counter I a loop without delay.
The nano was able to publish every fourth number. So the network is functioning but for not a very high speed requirement.

I did the same with a MQTT client on a Wemos D1 mini module. The difference in speed was dramatic. No gaps between numbers and much faster.

Because of the envisioned use for controlling a model railroad track layout I decided to go for the higher performance of the Wemos with all negative consequences as far s complexity of decoder composition is concerned.

Thanks for the support!

@mfalkvidd

I did some tests.
I put a byte counter I a loop without delay.
The nano was able to publish every fourth number. So the network is functioning but for not a very high speed requirement.

I did the same with a MQTT client on a Wemos D1 mini module. The difference in speed was dramatic. No gaps between numbers and much faster.

Because of the envisioned use for controlling a model railroad track layout I decided to go for the higher performance of the Wemos with all negative consequences as far s complexity of decoder composition is concerned.

Thanks for the support!

@mfalkvidd

Somebody has to make that mistake again!
This time it was me!

Thanks.

@mfalkvidd

I again need your advice

} void loop() { data1 = data1 + 1; bericht[1] = data1; send(msg.set(data1)); send(msg.set(bericht, 1)); }

data1 is transferred to Mosquito with a changing value.
bericht[1] is transferred with the originally assigned value.
it is not updated to the new value.
what could be causing this?

@mfalkvidd It works!
Bytes put into the message are transferred in Hex. They show up in the Mosquitto toppic!

Thanks a lot.

Thanks for your very fast reply!

Up to the next step!

I succeeded to transfer one single byte. It is not clear to me how I can construct a message in the payload which contains ten bytes.
The normal concatenation seems not to work.
I tried several things but no luck.

Thanks for your reaction!!!
I am going to experiment with it and post proceedings later!

I installed the ESP8266 MQTT gateway. When I close a switch on a NANO client I see the message being published on Mosquitto. Thus sofar so good.
What I am looking for is a description of how to insert BYTE type data into several payload bytes.
It would be most helpful to be able to construct in the Arduino sketch the complete message in accordance with the protocol description, coded by myself.

As far as I can understand the MyMessage.h and MyMessage.ccp it should be possible. But my knowledge is not sufficient to come up with a procedure myself.

I installed the MySensors gateway on Rasp3. I attached two clients, one on Nano and one on Mega.
Both clients are incorporated into the radio network correctly. I have a simple "door" sketch on the clients. By closing a contact a simple message is transmitted. Using the gateway in debug mode before install shows that these messages arrive at the gateway correctly.

After install I do not know how to see if messages are still arriving at the gateway.
I assume this will be OK.
Configuring MQTT gateway with IP-Address 172,0,0,1 and debug.
Testing with two separate terminal sessions shows that mosquito is working OK. In Terminal window 1 type:
mosquitto_sub -t -v rocnet/rs.

In Terminal window 2 type:
mosquitto_pub -d -t rocnet/rs -m "Hello from Terminal window 2!"

The message pops up in the first terminal.

Now closing the contact on a client should provoke the gateway to publish a message in topic rocnet/rs.
No message pops up on the subscription terminal.

I do not see where the Logfile of the gateway resides. So I am stuck debugging. Some body any idea how to proceed?

I would like to test the interaction between the gateway on a Raspi and mosquito on a separate Raspi.
Where resides the "gateway log" of the gateway on the Raspi?