That sounds like a legitimate thought. If anyone knows where that parameter is, and how to disable, that would be excellent. I wonder if Longer sleep times, would be more apt to skip a temporary issue, rather than a rapidfire re-attempt, triggering that 3 miss limit.

Still no solution. I set the 2 units side-by-side. Works for 4 hours, then just disappears.

Still hoping for a solution. Does the sensors not try to find home again if it loses it until a reset?

@boozz I moved the unit closer and it stayed up a few days just fine. Had to reset the gateway, and it did not come back until I reset the sensor unit. So apparently, once it fails to call home, its goes quiet.

@kimot Tried that. Ca't get domoticz to see the sensor.

Still in a holding patterns. In looking at other sketches, and as above I see My_radio being defined. Do I not need to define the esp radio? If not, I don't see how it will know to look for a gateway, ect.
I really thought this would be the simplest temp/humidity node, with only 2 basic pieces of hardware.
JimD

Running a genuine uno with nrf radio and dht22 sensors. Runs about 12 or so hours then drops sending. Hitting reset button makes it reconnect and instantly update. Any ideas?

@Jim-Danforth Here is the serial output (base is my outer SSID):
connected with base, channel 6
dhcp client start...
cnt
0;255;3;0;9;TSM:PDT
chg_B1:-40
ip:192.168.1.108,mask:255.255.255.0,gw:192.168.1.1

@korttoma right now playing with domoticz. I commented out the radio definition, but it only appeared to run as a server, not look for the real gateway.

Using library linked above
Getting: no matching function for call to 'DHT::readSensor(bool)'