You are using the same ChildID's for relays and tripped/door states. Imo this is messing things up, so e.g. use 11+12 for tripped values.
Remark: If you are looking for a good example on using arrays for that kind of tasks, see korttomas work here: https://forum.mysensors.org/post/51488

As you already did some differnenciation wrt. to the ChildID, this seemed not to be to far beyond your actual knowledge. Sth. like

if (incomingOutlet == 0 && (message.type == V_LIGHT || message.type == V_DIMMER))

should do the trick .
Wrt. to arrays to avoid all the repeatings in the code, it's not that easy. Assuming, the send-codes to be longint type of data, sth. like

const uint16_t RF_CODES[NUMBER_OF_PLUGS] = {
{4072574,4072566},
{4072572,4072564},
{4072570,4072562},
{1386894,1386886},
{1386892,1386884},
{1386890,1386882}
};

might easen addressing sendCode to sth. like

RF_CODES[incomingOutlet-1][incomingLightState]

Note: This is completely untested...
Within MySensors, array coding is not really part of the default sketches, so you should have a look at the normal arduino examples.

Two short remarks:

• last if-branch in receive() additionally needs clarification to only be meant for ChildID 0; this should "cure" the problem you are working on.
• For the general structure of your code imo it would help much to use arrays to store all the info.

@GieBek

6137 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:

Imo this indicates your node doesn't have a NodeID yet. When using RS485 you have to assign the ID's manually in the sketch, auto doesn't work... (e.g. #define MY_NODE_ID 123)

@1kohm Perhaps you have a look at this sketch to get a good example on how to "loop" alsmost eveything:
https://forum.mysensors.org/topic/4847/multi-button-relay-sketch/33

@pepson I'd suggest you make a test with the "simple" variant of the sketches. Then we could lateron discuss how to deal with an array containing the hardcoded addresses.
Pls. make also a test with the hardcoded version. Afai remember, it will print the needed array to serial, as long as #define PRINT_ARRAY isn't commented.

@pepson That's not necessary: The sketch reads the bus to get all the necessary info and will just send whatever is found.

If you want a "hardcoded version", you'd have to addopt the sketch for something in between these variants: if you use an array for the 1-wire addresses like https://github.com/rejoe2/MySensors-Dallas-Address-ChildID-Consistency/blob/master/Dallas_Addresses_Array_Solution/Dallas_Addresses_Array_Solution.ino does, just built the comment char-array based on that info.

@pepson said in About DS18B20 onewire.:

@mfalkvidd
OK but also must add defined description to all address. But how add also description?

Don't know, if that really works, because I never tested it since my controller sw supports comments: https://github.com/rejoe2/MySensors-Dallas-Address-ChildID-Consistency/blob/master/DallasTemperatureSimple/DallasTemperatureSimple.ino

@uwek Special-Debug only gives some more info about the sketch, so this most likely will not help.
Wrt to ACK, I'm not familiar how the MySensors lib handles that internally, but FHEM will keep all the messages seperate from each other.
I also have little experience with RFM modules; for nRF interrupt handling is not necessary, but most likely, this is the exception. Anyhow: It seems to work to some extend, so I'd not bet to much on this as the root cause of your problems.

So ok, you want to learn the hard way ...
If the mcu is an ESP8266 also on the node's side, forget about PIN2/3 beeing special, this applies to standard ATMega32P. But perhaps you'd have to define a different interrupt pin for the RFM.
Frankly spoken, imo it's easier to start off with a more default setup...