@sghazagh Hi all,
I tried to create a empty file and it seems that it does work and does not make any problem for the Radio functionality!

Any idea what this header is and how can I find this genuine library header for future use?

touch /usr/include/stropts.h

Hi all,
I have problem compiling Mysensors library on Ubuntu 20.04 image running on RPi 3/4 or Tinker Board.

Getting the error like:

...
e/Linux/drivers/core -c hal/architecture/Linux/drivers/core/Print.cpp -o build/hal/architecture/Linux/drivers/core/Print.o
g++ -MT build/hal/architecture/Linux/drivers/core/interrupt.o -MMD -MP -DMY_RADIO_RF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_SPIDEV -DMY_LINUX_SERIAL_PORT=\"/dev/ttyUSB01\" -DMY_LINUX_SERIAL_IS_PTY  -Ofast -g -Wall -Wextra -std=c++11 -I. -I./core -I./hal/architecture/Linux/drivers/core -c hal/architecture/Linux/drivers/core/interrupt.cpp -o build/hal/architecture/Linux/drivers/core/interrupt.o
hal/architecture/Linux/drivers/core/interrupt.cpp:33:10: fatal error: stropts.h: No such file or directory
   33 | #include <stropts.h>
      |          ^~~~~~~~~~~
compilation terminated.
make: *** [Makefile:99: build/hal/architecture/Linux/drivers/core/interrupt.o] Error 1

It seems that its missing the <stropts.h> header, but have you any idea how I can resolve that?

Many thanks

P.S: I tried on both RPI3 and 4 also on Tinker board and the problem are same for all of them running Ubuntu 20.04.

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!!!

:point_up: 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

:o silly me :D
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....

@anticimex Perhaps I should explain more...

As you guys know, in Domoticz you can protect a device and set the passcode in setting and use that for devices (Lights, Switches...) to operate if you only provide a correct passcode:

If you use Domoticz API to turn the light On or Off, and device is protected, you need to pass a extra parameter in your HTTP request and send the pass code to be able to operate that protected light or switch:
Something like this:

/json.htm?type=command&param=switchlight&idx=99&switchcmd=Off&passcode=YOUR_SWITCH_PASSWORD_AS_SET_IN_SETTINGS

Now my question is: how we should send the message from Mysensors device/sensor to Domoticz controller to turn it On or Off if the switch/light is protected?

@alowhum PROTECTED device a Switch in Domoticz that only can operate if you use a right pass code.

Hello everyone,
I have a Mysensors RFID Node running the RFID sketch on Arduino Pro Mini which sends the switch on/off command to Domoticz controller.
It just works great if the device is not protected.
I am wondering if I can send the on/off command to a protected device as well.

Is there any way I send the message to controller to turn the protected device on or off?
Can you please advise?

Many thanks

It seems that I could fix the issue by making the pin 15, LOW at boot time as it triggers the SD BOOT option in ESP8266:

void setup() {
  pinMode(15, OUTPUT); 
  digitalWrite(15,LOW);
}

@mfalkvidd Yes, I double checked and it is just before Mysensors.h line.
I see the Mysensors message in console, however, the radio connection is failing....

I see in another post , have mentioned that the Mysensors library 2.3.1 or 4.0.0 will be release to resolve the issue we have when compiling for "Lonin D1 Mini Pro" board. Do you know when that gonna happen?
I afraid maybe the library is mismatching with older version of "Lolin D1 mini pro" which is "Wemos D1 mini pro".

At the moment I see the name Wemos... in the list of devices in Arduino IDE as I am using esp8266 version 4.2.1.
Version 4.2.2 of esp8266 is listing the devise as Lolin ... name. I thought maybe the library is not fully compatible with this device as if I use that library the compile won't be successful.
Do you think that might cause the issue?

@mfalkvidd

I read this in forum:

Ok, after debugging for a while: the problem is with the CSN pin on GPIO pin 15. Pin 15 is also used in the ESP8266 to define boot from SD card. Somehow, at least in my case, after a reset, the NRF chip sets the CSN pin to high (measured it with a multimeter), causing the ESP8266 to start the SD-card procedure, which fails of course. The solution for me is swapping the pins for inclusion with the CSN pin:

So:
CSN -> GPIO 5 -> D1
Inclusion mode -> GPIO 15 -> D78

One question though: I also seem to have SPI pins on the other side of the Devkit, why aren't those used?```

That's the one you addressed in GIT.
I tried to move the CE pin to something else but it seems that it's not working!

// To use native I2C pins CE should be moved. Declare the new GPIO used here.
// GPIO 3 is pin D9 (RX below D8)
#define MY_RF24_CE_PIN D4

All,
I have changed the baud rate to "74880" as @yveaux mentioned and surprisingly I see this message which prevent the device to boot:

 ets Jan  8 2013,rst cause:2, boot mode:(7,7)

waiting for host

Do you know why it's going to this mode and how can I avoid that?

@yveaux thanks for your reply,
The radio connected as usual:

(All cables used with color coding for better understanding of connection pins)

I also have changed the different baud rate...it's not that, because at 115200, with radio power disconnected, I can see all the MySensor messages, also when I reconnect the radio power, I can see that the radio can connect to controller and send.receive data!

Only when radio connected at boot time, device does not boot and does not work properly!