I don't know why, but by adding "--my-rf24-channel=13" in my configuration and compile it again, it seems that all are working as expected now!!!

Believe me, I always used "make clean" so don't know why it didn't refresh the build. Perhaps that option force the compiler to rebuild it!!!"

@mfalkvidd I used a LE33 transistor to power up the radio after converting the 5v from Arduino Uno(tried 3.3v pin as well, same).
I am also using 4.7mF capacitor on positive and negative pols as well.
I am sure radio is ok, as as soon as I change the Channel back to 76, it quickly register in my first Network.
When I change the Channel to for instance 13, the GW on channel 13 does not register and see that Node....

@mfalkvidd I really don't know what is wrong...I just getting this error all the time
Cleared the EEPROM first and have set the radio channel to 13 for both GW and Node!)

Here is log on GW side (Serial on Linux)

Any idea why they cannot find each other?

@boozz Ok, if we say we have serial GW on Linux and also a Node:

• Does channel only need to be changed in MyConfig.h file in MySensors Library before I compile for my Serial GW on Linux

• and for the Node, I only need to add a define in Sktech?

#ifndef MY_RF24_CHANNEL
#define MY_RF24_CHANNEL (83)
#endif

Also have a question about your setting, I see the channels for NRF24L01 only are:

0 => 2400 Mhz (RF24 channel 1)
1 => 2401 Mhz (RF24 channel 2)
76 => 2476 Mhz (RF24 channel 77)
83 => 2483 Mhz (RF24 channel 84)
124 => 2524 Mhz (RF24 channel 125)
125 => 2525 Mhz (RF24 channel 126)

How did you set channel 13 and 58?

@mfalkvidd What you are saying make scenes, because when I start the Node, it goes straight to other Gateway and even when I turn the Network1 Gateway off, it still comes up with Nodeid of Network1but does not register to Network2 Gateway !!!
I will try it, tomorrow...

Hello all,
Hope like always you can help me to understand if this concept is possible or not.

I have an already established MySensor network for my home. So I have controller, nodes (sensors) and all working fine.

I need to test another device in another MySensor network by running Domoticz and Gateway again.
So the second server, has Domoticz installed with MySensor Gateway as Serial but cannot communicate with devices properly.
It seems that having the sensors running in same place, make the system tricky and nodes can register only in one of the networks.
I tried to resolve this by changing the network channel (from 76 to 83 in MyConfig.h file) for both my second Gateway and a Node I want to use in second network but seems that it's not working as expected either!

So , can you please any one have this experience, explain that what is the best practice to make it working as two separate MySensors Network in same location please?

Thanks for your time and hope I could explain the case scenario

@bjacobse Yes, you are absolutely right, and that password only is required when you trig the device inside controller.
I mean, if you click the icon in controller for that device and device is protected, it asks for password.
And if you also use HTTP API, you need to provide password as well.

So if you want to trig the device from other Mysensor node (my case), it does not know about the protection and you can directly send the message to trig the device on or off.

@mfalkvidd when will be the estimate release date of Mysensors library working with esp8266 v2.4.2?

Getting compile error if I use 2.4.2 library for Lolin d1 mini pro device....

Thanks

silly me
It seems that it even doesn't care the device is protected or not! it just could change the status of the device even if it is protected...

@anticimex At the moment, I have a workaround and doing the logic through the LUA script.
In LUA, I can send the request to the switch with passcode as I explained above.

That works fine but that would be great if Mysensor can have an option to send the message directly to controller for particular IDX (like what it does now) plus an option to pass the passcode to controller for protected devices.

Perhaps, if it's not in the features, that would be good to have it in future releases....