Inserting custom data into payload bytes

[mfalkvidd]

@eporocrail it should be possible to use

MyMessage& set(void* payload, uint8_t length);

See https://www.mysensors.org/download/sensor_api_20#message-manipulation for details.

[eporocrail]

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

[eporocrail]

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.

[mfalkvidd]

@eporocrail I think you can simply use byte myByteArray[10] and set each byte (0-9) to your payload. Then call message.set(myByteArray, 10)

[eporocrail]

Thanks for your very fast reply!

Up to the next step!

[eporocrail]

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

Thanks a lot.

[eporocrail]

@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]

@eporocrail arrays start numbering for zero. So send(bericht, 1) will send the first byte of bericht, but data1 was written to the second byte.

Either use bericht[0]=data1 (if you want to send only one value) or use send(bericht, 2) if you want to send two values (bericht[0] and bericht[1] together)

[eporocrail]

@mfalkvidd

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

Thanks.

[eporocrail]

@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]

@eporocrail very nice, great work! Thanks for reporting back.

You might know this already, but it is possible to run the Wemos at 160MHz instead of default 80MHz. Not sure if you need it or if it helps, but it might be good to know. Just select the higher frequency in the Tools menu in Arduino IDE.