Hi @sandim_kaushik, welcome to the forum!

Have you tried the gas sensor example? If so, what were the results?

Hi @bignik, welcome to the forum!

Using hardware serial should work. Did you use this? If so, what were the results?

// Enable this if RS485 is connected to a hardware serial port
//#define MY_RS485_HWSERIAL Serial1

If anyone can help @reshma-oueseph, please post in the original thread so we don't split our efforts in multiple places.

@miclane use dns and a convention for naming the broker like mysensors-mqtt.local?

@hakha4 the code looks good to me. What does the device page in Domoticz look like? What do the node and gateway debug logs say?

Maybe the presentations are putting too much strain on the power supply or radio (the debug output will show whether that is the case). Try adding wait(100) after each presentation statement.

@chisight I'm not fond of the infinite scroll method, but perhaps the "Enable In-Topic Searching" feature on your profile settings can be useful?

@deluka yes. Just use present() and send() as you would on a normal sensor node.

@yveaux I agree. But I would assume that the default value (20) was chosen for a reason?

avr-size and readelf might help you track what's using up the space. Some details in https://forum.mysensors.org/post/46683 (focused on ram usage, but the same tools can show information about the flash usage)

Great work @koresh !

How much more ram does the queue require? (I assume the queue size is configurable, but what would a reasonable size be?)

Edit: I guess you'll use MY_RX_MESSAGE_BUFFER_SIZE just as for nrf24. So the ram impact will be MY_RX_MESSAGE_BUFFER_SIZE x (MAX_MESSAGE_LENGTH + 1) which is 20 x (32 + 1) = 660 bytes. That'll be tough to fit on atmega328 nodes, right? But esp8266, esp32, samd and nrf5x will handle it without problems.