Hi,
I answer to myself as it may help some other beginners like me.

• there's a way to get the debug info via telnet session to the ESP8266 gateway: look fro MyNetDebug library in this forum.
  https://forum.mysensors.org/topic/7044/debug-messages-over-wi-fi

• be careful if you reuse sketches from 2.2.0 with 2.3.0 library release : now instead of
  #define MY_ESP8266_SSID "MySSID"
  #define MY_ESP8266_PASSWORD "MyVerySecretPassword"

you should use:
#define MY_WIFI_SSID "MySSID"
#define MY_WIFI_PASSWORD "MyVerySecretPassword"

br,

Hi,
I found the cause of the error..
Since 2.3.0, we shouldn't write anymore:

#define MY_ESP8266_SSID "MySSID"
#define MY_ESP8266_PASSWORD "MyVerySecretPassword"

but:

#define MY_WIFI_SSID "MySSID"
#define MY_WIFI_PASSWORD "MyVerySecretPassword"

I found because I discovered than compiling was OK with 2.2.0 and not anymore with 2.3.0 (even without the MyNetDebug library) and I looked at the example in the 2.3.0 library..
I had been misleaded by the fact than in release description, it was stated that 2.3 is backward compatible and that network had not to be modified.. So I had thought that no change was required in the sketch..

I could test the library MyNetDebug and it seems working: the only thing is that it seems slow. Letters show up one after the other fairly slowly (much more slowly than if Serial Monitor used alone). I hope it's not disturbing radio communication..
But it's great to be able to catch debug messages without plugging the ESP8266 in a computer ! I'll have to investigate if the debug status can be switched on/off by a remote command to the ESP8266 gateway to avoid overloading the device if not necessary.

Thanks again for your efforts!

Hi,
Thanks for your help.
Yes, I defined them before the Mysesnors.h.
here's my ino (I anonymised ssid and password):

// Application details
#define APPLICATION_NAME    "Gateway RFM95 Eric"
#define APPLICATION_VERSION "0.0.0.Beta Eric"

// Enable debug prints to serial monitor
#define MY_DEBUG

// Use a bit lower baudrate for serial prints on ESP8266 than default in MyConfig.h
#define MY_BAUD_RATE 115200 

// Enable and select radio type attached
#define   MY_RADIO_RFM95

#define   MY_DEBUG_VERBOSE_RFM95
//#define   MY_DEBUG_VERBOSE_RFM95_REGISTERS
//#define MY_RFM95_ATC_TARGET_RSSI (-70)  // target RSSI -70dBm
//#define   MY_RFM95_MAX_POWER_LEVEL_DBM (20)   // max. TX power 10dBm = 10mW
#define   MY_RFM95_FREQUENCY (RFM95_434MHZ)
//#define   MY_RFM95_MODEM_CONFIGRUATION (RFM95_BW500CR45SF128)
//below was used in first successful testings then modified to try improving coverage
//#define MY_RFM95_MODEM_CONFIGRUATION RFM95_BW125CR45SF128
#define MY_RFM95_MODEM_CONFIGRUATIONRFM95_BW125CR48SF4096
#define MY_TRANSPORT_STATE_TIMEOUT_MS  (3*1000ul)
#define RFM95_RETRY_TIMEOUT_MS  (3000ul) 

#define   MY_RFM95_IRQ_PIN 5
#define   MY_RFM95_IRQ_NUM MY_RFM95_IRQ_PIN
#define   MY_RFM95_CS_PIN 15


#define MY_GATEWAY_ESP8266


// Set WIFI SSID and password
#define MY_ESP8266_SSID "nameofmywifi"
#define MY_ESP8266_PASSWORD "mypassword"

#define MY_HOSTNAME "lora-gateway"

#define MY_PORT 5003

//added for MyNetdebug
// How many clients should be able to connect to this gateway (default 1)
#define MY_GATEWAY_MAX_CLIENTS 2

#if defined(MY_USE_UDP)
#include <WiFiUdp.h>
#endif
// end added for Mynetdebug

#include <ESP8266WiFi.h>

//added for Mynetdebug
#include <MyNetDebug.h>
#define MY_SERIALDEVICE NetDebug
// end added

#include <MySensors.h>

void setup()
{
  //all block below added for Mynetdebug

     // Echo all data sent by the debug client
  NetDebug.echo(true);
  // Send a carriage return before each line feed
  NetDebug.crBeforeLF(true);
  // If you want the debug message to also be sent to Serial port
  NetDebug.mirror(&Serial);
  // Initialize the serial port if you plan to use it in your sketch or if you are using the mirror function
  // MySensors usually does this for us, however, since we've set up our serial device to be NetDebug,
  // we have to do it ourselves
  Serial.begin(MY_BAUD_RATE);

  // end added Mynetdebug
    // Setup locally attached sensors
}

void presentation()
{
    // Present locally attached sensors here
  sendSketchInfo(APPLICATION_NAME, APPLICATION_VERSION);

}

void loop()
{
  //added for Mynetdebug
   (void)NetDebug.available();
// end added for Mynetdebug
    
    // Send locally attached sensors data here


}

For your info, before I make these changes, it was compiling OK. My changes are embedded within the comments "added for Mynetdebug".
In IDE, I use the setting wemos D1R2 & mini, 80MHz and "4M(3M SPIFFS)".
Maybe I installed the library i a wrong manner ? Shoudl I move the .h and .cpp one level up in folders ?

Thanks,

Hi,
Your initiative seems a bright idea, thanks for that !
I tried your library to debug a gateway on a wemos D1 mini with Mysensors 2.3.0, but I got error messages when compiling. Maybe it's because I didn't follow proper installation of your library as I'm not friendly with Arduino IDE library system.
I did symply download your folders from github and installed Mynetdebug-master folder in same folder than Mysensors library folder. IN the Mynetdebug folder, I have a keywords.txt file and a library.json and library.master, and a src folder where I have the .cpp and .h files.
Is it correct ?
I used your example for ESP8266 to modify my working gateway .ino.
Then, when I compiled, I got following error messages:

Arduino: 1.8.5 (Windows 7), Board: "WeMos D1 R2 & mini, 80 MHz, 115200, 4M (3M SPIFFS)"

WARNING: Category 'MySensors' in library MyNetDebug is not valid. Setting to 'Uncategorized'
In file included from d:\userdata\myname\My Documents\Arduino\libraries\MySensors/MySensors.h:212:0,

                 from D:\userdata\myname\My Documents\Arduino\LoraGTWperso04Mynetdebug\LoraGTWperso04Mynetdebug.ino:67:

d:\userdata\myname\My Documents\Arduino\libraries\MySensors/core/MyGatewayTransportEthernet.cpp: In function 'bool gatewayTransportInit()':

d:\userdata\myname\My Documents\Arduino\libraries\MySensors/core/MyGatewayTransportEthernet.cpp:28:22: error: 'MY_ESP8266_SSID' was not declared in this scope

 #define MY_WIFI_SSID MY_ESP8266_SSID

                      ^

d:\userdata\myname\My Documents\Arduino\libraries\MySensors/core/MyGatewayTransportEthernet.cpp:163:19: note: in expansion of macro 'MY_WIFI_SSID'

  (void)WiFi.begin(MY_WIFI_SSID, MY_WIFI_PASSWORD, 0, MY_WIFI_BSSID);

                   ^

d:\userdata\myname\My Documents\Arduino\libraries\MySensors/core/MyGatewayTransportEthernet.cpp:34:26: error: 'MY_ESP8266_PASSWORD' was not declared in this scope

 #define MY_WIFI_PASSWORD MY_ESP8266_PASSWORD

                          ^

d:\userdata\myname\My Documents\Arduino\libraries\MySensors/core/MyGatewayTransportEthernet.cpp:163:33: note: in expansion of macro 'MY_WIFI_PASSWORD'

  (void)WiFi.begin(MY_WIFI_SSID, MY_WIFI_PASSWORD, 0, MY_WIFI_BSSID);

                                 ^

exit status 1
Error compiling for board WeMos D1 R2 & mini.

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

Can you help me ?
br,
Ricorico94

Hi,
I built a ESP8266 gateway using a wemos D1 mini and RFM95. I'd like to debug some communications with sensors with being attached to serial port of a computer, so I tried to connect via telnet.
I can connect as telnet, but I don't see many details.. First, text in telnet is not aligned on the left, and second, it only lists some raw values instead of displaying same kind of verbose debug info like in the serial monitor.
Is there a way to display same verbose text than in serial monitor ?

Thanks,
ricorico94

THanks a lot for your explanations. I should have thought about that indeed..
I tried to play with antenna positonning to see impact on RSSI, but it was not obvious (a few dB maybe). Maybe it was because I made the test at very close distance (30 cms.. between antennas) and so strength is too high to get meaningfull readings.

Do you know until which RSSI level, we can have reliable communication ? -80? -120 ?..

Regarding the lower frequency band mentioned by mfalkvidd, does it exist in RFM95 compatible devices ?

Ricorico94

Hi,
I'm currently using MYsensors with Domoticz, which is a great controller. But I'd like to be able to store all datas coming from some sensors and displaying them (as graph or at least table) : I don't think Domoticz is suitable for that because it's averaging values over time, so it's difficult to do fine analysis of datas received or to analyse them a long after (I don't care about volume of stored data).
For instance, I'd like to visualize radio signal strengths when I move a sensor... but I couldn't find how to do it with Domoticz if I don't have the arduino software conected to gateway with its serial monitor (well, there's way y clicking on settings of the hardware device in domoticz and showing childs then their values, but it requires to be permanently in fron of screen and I can't look at historical data..)

Any idea on which controller I could use or also how to do it with Domoticz ?

br
Ricorico94

Hello,

I tried to build a Mysensors gateway based on LORA using the ideas above. I used a RA-O2 SX1278 connected with a wemos D1 mini as a LAN gateway and connected with a pro mini as a sensor.
(the radio module I used is:
aliexpress SX1278 RA-02
As antennas, I used 2 like this:
link to antenna
and I also tried replacing the gateway antenna by this one:
link to high gain antenna

As wiring, I used the one from jkandasa above and I used the following settings:

#define MY_DEBUG
#define MY_BAUD_RATE 115200 // or 9600 ?
#define   MY_RADIO_RFM95
#define   MY_DEBUG_VERBOSE_RFM95
#define   MY_RFM95_FREQUENCY (RFM95_434MHZ)
#define MY_RFM95_MODEM_CONFIGRUATION RFM95_BW125CR45SF128
#define   MY_RFM95_IRQ_PIN 5
#define   MY_RFM95_IRQ_NUM MY_RFM95_IRQ_PIN
#define   MY_RFM95_CS_PIN 15
#define MY_GATEWAY_ESP8266 

and I used the default gateway sketch from website (I did not use the OTA version which I'm not familiar with).

For the node, I used these settings:

#define   MY_RADIO_RFM95
#define   MY_DEBUG_VERBOSE_RFM95
#define   MY_RFM95_MAX_POWER_LEVEL_DBM (20)   // max. TX power 10dBm = 10mW
#define   MY_RFM95_FREQUENCY (RFM95_434MHZ)
#define MY_RFM95_MODEM_CONFIGRUATION RFM95_BW125CR45SF128
#define MY_DEBUG

#define NODE_ID (int8_t) AUTO
#include <MySensors.h>

int Send_rssi, Rec_rssi;                     // RSSI RFM95 chip
#define CHILD_ID_RSSI_HIGH  7                // RSSI received signal level
#define CHILD_ID_RSSI_LOW   8                // RSSI background noise level
#define CHILD_ID_BATTERY 1
MyMessage msgRSSI1(CHILD_ID_RSSI_HIGH, V_LEVEL);
MyMessage msgRSSI2(CHILD_ID_RSSI_LOW, V_LEVEL);
MyMessage voltage_msg(CHILD_ID_BATTERY, V_VOLTAGE);

and I used a basic node sketch in which I send a simple counter and also send an indicator copied from sketches in above posts but which I don't fully understand..:

Send_rssi = transportGetSendingRSSI();  // read RSSI in RFM95. Measure reception signal from gw

In practice, the value sent for send_RSSI is about (-21) when antennas are in direct sight at approx 20-30cm distance. I tried to move the node to the lower floor (ie one concrete floor between gateway and node in a building) and it says -38 or -44. I tried to go to basement (10 floors below) and I receive nothing.. whereas that was my main motivation for trying long range LORA radio...
I had selected the 433MHz version as I though the lower frequency would go further through walls than the 868MHz.

So I have a few questions..

1. are these -21 or -40 values common values? is it normal to have -21 even at a few cm distance ?
2. do you think the antennas I used are best otions to try going far away through several fllors of concrete ?
3. in terms of wiring, I simply connected the wemos D1 mini and the pro mini to the RA-02 without any capacitor. Is it like NRF24 where adding some capacitors could help ?
4. in terms of settings, I did not try yet all the settings mentioned in previous posts. I'll try the modem config with slow setting, but I'm not sure about the other settings: I guess I would need maximum power, maximum sensitivity, etc. Maybe also using the timeout setting used by jkandasa. What could you advise me ?
5. do you think I'd have better result with a LORA of another frequency ?

In case it matters: I don't plan sending a lot of data through the sensor. Target would be to use it to detect opening of a door

Thanks a lot for your help,
Ricorico94

Thank you for the clarification !

@mfalkvidd : thanks a lot ! I had searched for such version history and couldn't find it.
Indeed it seems introduction of the switches for log files was introduced in February, so I should probably update my install.

Precisely, talking about upgrade process: I read in previous posts that we should uninstall/unregister the install/service. WHat would be commands to do so ? Should it be:

sudo systemctl disable mysgw.service

and executed before anything else ? So upgrade process would be:

sudo systemctl disable mysgw.service
make
sudo make install
sudo systemctl enable mysgw.service

(and maybe test the gateway before the "systemctl enable..")
Is there anyfile to remove manually ? or any other command to apply before or after ?

oups, indeed. I'll edit my post as well to avoid confusion as well. Thank you for your support, I appreciated a lot.
By the way, I could never find how to get the logs in my gateway installed on raspPI. But that's another post. ;-)

Thanks to another arduino forum, I found what was wrong.. probably indeed a stability of power due to step-up converter. In that forum, they were explaining that receiving is more sensitive to power noise than sending data and that in such case, it's good to add a 100uF capacitor on 3.3V and GRD of radio module. I tried 100uF and it worked.. I then tried with 47uF and it's still working. (I had tried with 0.47uF and it was not working at all)

In the "Connect Radio" guidelines, of Mysensors, it is stated that a capacitor of 0,47-47uF is improving reliability but that "the exact size usually doesn't matter" which was misleading in my case.
Could I suggest to rephrase that sentence into "the exact size usually doesn't matter, but you can try 47uF if 0.47uF still doesn't work, especially if sending data works well and not receiving data." ?

Edit for Erratum: please read 4.7-47uF instead of 0,47uF-47uF. Tests I had made were with 4.7uF as well, not 0.47uF
br,
Ricorico94

Thank you for this explanation. So I guess in my case, I have the gtw as server since I had to fil in Domoticz the IP address of the gtw (even though it was 127.0.. as local IP).
Is there any difference of behavior between the 2 settings ? Like if the Mysensor gtw is in server mode, it means that multiple controllers could connect to it and receive the sensors flux ?
I tried to find some documentation on that but no success so far. It's more for my own curiosity at this stage. ;-)

@ikkeT : would you mind sharing full details of your sketch and hardware setup (diagrams, ..) ?
That would be great since you already share the 3D case print.
Thanks,
ricorico94

Hi,
Reading again various pages to try solving a problem, I noticed this statement (in the raspberry pi gateway):
"To set the gateway as a client that connects to a controller, use:"
What does it mean ? what is the difference between a client or not ? I saw nothing in the "getting started pages" or in "selecting gateways" explaining that.

br,
Ricorico94

Hi,
I try to access log info from my gateway installed on my domoticz raspberry pi, but I get no success..
First, I can't find the mysensors.conf file : nothing in the /etc folder. I tried to use "find / -name 'mysensors.conf' 2>/dev/null" command, but it finds nothing.
I tried creating such a file (then it's found by the fond command above) and in which I have the lines

log_pipe=0
log_pipe_file=/tmp/mysgw.pipe

as instructed above.
I restarted the wole Raspberry PI, then tried the command cat /tmp/mysgw.pipe but error message:

cat: /tmp/mysgw.pipe: Aucun fichier ou dossier de ce type

(= no file or folder like that)
I then tried this: sudo mysgw -c /etc/mysensors.conf and I got also error message:

mysgw: invalid option -- 'c'

I installed the Mysensor gateway on 17th October 2017 and my raspberry pi is working on Wheezy. In Domoticz, I see the Mysensor gateway has version 2.1.1.
MY gateway seems working fine, communicating properly with sensors (both ways). I'm trying to find log because I face an issue with a new sensor which works properly when powered with external FTDI 3.3V and only 1 way (sensor to gateway only) when powered on battery (I raised question in another post, where I was suggested to check log fil on gtw side..)

Any idea of what I should do (except "reinstall whole raspberry pi with latest OS..) ?
Thanks a lot,
Ricorico

Thanks for the advice, I'll try that.
For the log on the gateway side : I use a gateway on the raspberry pi itself (as per https://www.mysensors.org/build/raspberry ) of my Domoticz installation. Is there an easy way (like via telnet) to get the logs other than by creating the new line in the config file ? Maybe the 3rd option proposed with "mysgw.pipe" ? (in such case, do I need to reboot whole raspberry after modifying the config file?)

Hi,
As regulator I use a stepup like that one:
https://fr.aliexpress.com/item/DC-DC-0-8-3-3V-to-3-3V-Step-Up-Boost-Power-Module-For-Arduino/32819660926.html?spm=a2g0s.9042311.0.0.27426c37HEbdcz

I use a NRF24L01 as radio module following the connection guidelines from Mysensors. I did not add any capacitor to 3.3 and ground of the NRF24L01.
I connected the vO of the stepup to the VCC (the VCC between RX and GRD and not the RAW) of the arduino pro mini 3.3V as indicated in this post:https://forum.mysensors.org/topic/4045/solar-powered-soil-moisture-sensor
I use indeed a similar lamp with its small NiMh battery (1.2v) and its solar panel.
The NRF24L01 is connected on GRD (between RST and RAW) and on VCC (between A3 and RST). I hadn't put any capacitor.
I tried following your advice to add a 0.1uF ceramic capcitor between VCC (the one between RX and GRD) of pro mini and its ground, but apparently, I face same issue.
(I did not solder the capcitor yet, I only connected through the pins I usually use for the FTDI)

16 MCO:BGN:INIT NODE,CP=RNNNA---,VER=2.2.0
26 TSM:INIT
28 TSF:WUR:MS=0
34 TSM:INIT:TSP OK
36 TSF:SID:OK,ID=4
38 TSM:FPAR
75 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2084 !TSM:FPAR:NO REPLY
2086 TSM:FPAR
2123 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4130 !TSM:FPAR:NO REPLY
4132 TSM:FPAR
4169 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6176 !TSM:FPAR:NO REPLY
6178 TSM:FPAR
6215 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8222 !TSM:FPAR:FAIL
8224 TSM:FAIL:CNT=1
8226 TSM:FAIL:DIS
8228 TSF:TDI:TSL
18229 TSM:FAIL:RE-INIT
18231 TSM:INIT
18237 TSM:INIT:TSP OK
18241 TSF:SID:OK,ID=4
18243 TSM:FPAR
18280 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20289 !TSM:FPAR:NO REPLY
20291 TSM:FPAR
20328 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
22337 !TSM:FPAR:NO REPLY
22339 TSM:FPAR
22376 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
24385 !TSM:FPAR:NO REPLY
24387 TSM:FPAR
24424 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
26433 !TSM:FPAR:FAIL
26435 TSM:FAIL:CNT=2
26437 TSM:FAIL:DIS
26439 TSF:TDI:TSL
36442 TSM:FAIL:RE-INIT
36444 TSM:INIT
36450 TSM:INIT:TSP OK
36454 TSF:SID:OK,ID=4
36456 TSM:FPAR
36493 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
38502 !TSM:FPAR:NO REPLY
38504 TSM:FPAR
38541 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
40550 !TSM:FPAR:NO REPLY
40552 TSM:FPAR
40589 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
42598 !TSM:FPAR:NO REPLY
42600 TSM:FPAR
42637 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
44646 !TSM:FPAR:FAIL
44648 TSM:FAIL:CNT=3
44650 TSM:FAIL:DIS
44652 TSF:TDI:TSL
54657 TSM:FAIL:RE-INIT
54659 TSM:INIT
54665 TSM:INIT:TSP OK
54669 TSF:SID:OK,ID=4
54671 TSM:FPAR
54708 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
56717 !TSM:FPAR:NO REPLY
56719 TSM:FPAR
56756 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
57493 TSF:MSG:READ,0-0-4,s=255,c=3,t=8,pt=1,l=1,sg=0:0
57499 TSF:MSG:FPAR OK,ID=0,D=1
58765 TSM:FPAR:OK
58767 TSM:ID
58767 TSM:ID:OK
58769 TSM:UPL
58806 !TSF:MSG:SEND,4-4-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
60815 TSM:UPL
60852 !TSF:MSG:SEND,4-4-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=1,st=NACK:1
62861 TSM:UPL
62863 TSF:MSG:SEND,4-4-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=2,st=OK:1
64872 TSM:UPL
64909 !TSF:MSG:SEND,4-4-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
66918 !TSM:UPL:FAIL
66920 TSM:FPAR
66957 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=1,st=OK:
68964 !TSM:FPAR:NO REPLY
68966 TSM:FPAR
69003 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
71012 !TSM:FPAR:NO REPLY
71014 TSM:FPAR
71051 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
73060 !TSM:FPAR:NO REPLY
73062 TSM:FPAR
73099 TSF:MSG:SEND,4-4-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
75108 !TSM:FPAR:FAIL
75110 TSM:FAIL:CNT=4
75112 TSM:FAIL:DIS
75114 TSF:TDI:TSL

Apparently, it sends correctly packets but can't receive any ACK or message from the gateway.
I got this log by connecting a FTDI adapter with only the RX/TX cables. If ever I connect also the GRD and 3.3V of the FTDI, then I get no error message at all (even without the capacitor) and Domoticz receives all updates (and also sends as I use Domoticz to send customized sleep duration to the sensor).

Should I try adding both the 0.1uF to VCC/GRD of arduino and also a 4.7uF to the 3.3/GRD of the NRF24 as suggested in the "Connect the Radio" page ?
Any idea ?
br,
Rico

Hi,
I'm trying to build a Soil Moisture sensor with NiMh battery and solar panel as in another post. I use a stepup converter to 3.3V connected on the VCC of a pro-mini 3.3V. The sensor seems working when connected to FTDI USB device, ut once I remove the power from FTDI, no more communication. I measured the voltage on the output of the stepup which indicates 3.26V. Is it norml or a defective step-up ? And should I remove the regulator of the pro-mini as suggested above or not ? (in article above, it states the regulator is not necessary, but it doesn't say if pro-mini would still work if regulator remains there).
Thanks for your support

This is even one step further as I understand you get rid of the sandwich Arduino pro mini by soldering directly an ATMEGA328p. It makes the overall setup much more dense indeed. Congratulations !

Could you share the details on software (scripts..) you used for the whole setup ?
I'm also interested in settings you use, because based on another thread, I had seen that some settings for RFM95 had an impact on error rates.