@itbeyond logs would be great it can be improved. As i wrote above, I had some issues as well but they went away when I upgraded all (and made some other changes as well).

@neverdie - I have had boosters on my EasyPCB not working with electrolytic capacitors but switching to a ceramic makes the radio come alive - so I have a real-world example of this. In the same time, I guess the frequency is really important before choosing.

@manos yes you can.

@manos

I want to use it the 5V Arduino Pro mini not the 3V version

Then you need to use the nrf24l01+ version, that works fine - the RFM69 version needs a 3.3v Pro Mini only.

I also want to use the battery monitor

As @gohan said - don't use batteries on a 5v node. Use a 3.3v because it will use up your batteries very quickly. See the guides i have on openhardware for different modes on my PCB.

Is it ok or should I modify "something"
Also all the pcbs have the battery "expansion: or not?

"something" is hard to understand, you can modify i many different ways depending on what you want to do. All the basic "modifications" can be found if you read the project page on openhardware.io

If you have a amplified radio you need a better voltage regulator than the onboard regulator. When the radio transmits it can cause a higher current draw than the regulator can provide.

I don't know what the logs mean... but try the log parser.https://www.mysensors.org/build/parser

@titvs well, its good you figured out its the repeater hanging. Maybe you should look over the hardware? I would suggest trying swapping the capacitor and/or radio. Looking over the nodes debug output is a great idea, but if it just hangs it will not give you anything (unless its a software issue). If so, as I said try first to change the capacitor, maybe try another value (ie if you are using 4,7uF you can try 10uF or 47uF). It can also be good to try another power supply.

How do you power the repeater at the moment? How do you get it to 3.3v? Are you using a strong enough voltage regulator?

@titvs yes, I'm saying it's worth a try... I made some other changes so can't promise.

@titvs did you try to set my_parenr_node_id (gateway = 0) on the repeater? I had some similar issues but I upgraded from 2.2 to 2.3 in the same time so can't tell if it was a version mismatch or that the parent setting helped.

@alowhum any normal user should be good with node > repeater > gw . Atleast that's my maximum.

But I guess you could test by building some repeaters with forced node and parent id.

@harrdy should work just fine.