Adds option to disable N2N (#1439)

[lelouch94]

This pull request adds the configuration option MY_TRANSPORT_N2N_FEATURE_DISABLED,
to disable the node to node transport feature.

see: #1439

[mfalkvidd]

How about adding an else clause here, with something like
TRANSPORT_DEBUG(PSTR("!TSF:RTE:N2N DIS\n")); so people who enable this feature and forget about it (or don’t fully realize what it does) can get some information on why their N2N messages disappear?

[lelouch94]

Okay, I will try it out and check how it works.

[mfalkvidd]

Could you add a small note on when this feature can/should be used? Maybe some sort of use case description?

[lelouch94]

Hi @mfalkvidd, my use case is a node that is located in a dead zone and can only be reached via a repeater.
When the node sends telegrams to other nodes or the gateway, I always get the error message !TSF:RTE:N2N FAIL in the log. This is a waste of node battery energy and in addition it pollutes the airwaves with traffic that interferes with the communication of other nodes.

[mfalkvidd]

Do you know what causes the node to try to sent to other nodes?

[lelouch94]

Hi @mfalkvidd, I am intentionally sending the message to another actuator node which unfortunately is not directly reachable via N2N.

[lelouch94]

Hi @mfalkvidd, I have implemented your suggested change and it works for me so far. I have omitted the '!' because it is not an error, but a setting.

Are there any news regarding the CLA?

[lelouch94]

Hi @mfalkvidd, I have now also extended the log parser for the new N2N disabled message.