@dbemowsk the Flashforge Finder dont have a heatbed and only uses PLA. And if you dont clean the bed with IPA it will lift. I always print with brim just to be sure.

Just do a regular calibration. Just hand tight the knobs, no force needed. Then start the calibration. Slowly rotate the knob until it the printer beeps. When the calibration is done. Print one of these that fits the bed thingiverse calibration
Carefully check the result. You should have a consistent print. If not, twist the knob closest to where you need to move re-calibrate. Thin line, the bed need to be closer to the nozzle, thick line that curls, move the bed away.
Note, when turning the knobs, just move it 1/4th turn each time. And make a note wich knob, the direction (clock wise or counter clock wise).

To get more info, search on youtube for flash forge finder calibration, there are a lot of videos there.

I bought Buildtak that I replaced the bed with. I don’t use glue. I did print out a couple of calibration figures that I downloaded from Thingiverse. After a couple of re-calibrations and printing with the calibration figures I have not touched the calibration again.
However, when I printed the MySensors box from Thingiverse the corners still lifted.
That was when I found the suggestion to print with a rim.
Now my prints never lift.
I also clean the bed after each print with IPA.

Print with a rim. There is a tickbox for it.

Yes, and I am very pleased with it.

@ahmedhodhod did it work with the suggested links?

eeprom write long

PLease, DON’T write to eeprom in the loop(), you will destroy the eeprom. The lifecycle for the eeprom is 100000 writes/read, after that it is destroyed.
info about eeprom writes at arduino

EDIT: With the current code (write to eeprom every second) the eeprom will be destroyed after aprox 69 days.

I don't know if it affecting your case, but according to the source code for the BH1750 library you need to set the mode:
Source code for bh1750 library
Note that the begin() function needs a mode parameter, and that is used in configure, it if is not provided it is an invalid mode,

void BH1750::begin(uint8_t mode) {

  Wire.begin();
  //write8(mode);
  configure(mode);
}


void BH1750::configure(uint8_t mode) {

    switch (mode) {
        case BH1750_CONTINUOUS_HIGH_RES_MODE:
        case BH1750_CONTINUOUS_HIGH_RES_MODE_2:
        case BH1750_CONTINUOUS_LOW_RES_MODE:
        case BH1750_ONE_TIME_HIGH_RES_MODE:
        case BH1750_ONE_TIME_HIGH_RES_MODE_2:
        case BH1750_ONE_TIME_LOW_RES_MODE:
            // apply a valid mode change
            write8(mode);
            _delay_ms(10);
            break;
        default:
            // Invalid measurement mode
            #if BH1750_DEBUG == 1
            Serial.println("Invalid measurement mode");
            #endif
            break;
    }
}```

@pepson said in RFM69 new driver delay:

And tell me how you have connected Gateway to RPI3? By ethernet or by serial ? Because i see in your building Gateway that you dont use parameter ETHERNET on port 5003

I use Ethernet to connect to my Domoticz.
The reason that you don't see my configuration for ETHERNET or PORT is because they are default when you configure.
If you look at the file Makefile.inc you will see the build options. In my case the file looks like this:

SOC=BCM2837
CPPFLAGS=-march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_RFM69 -DMY_RFM69_NEW_DRIVER -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_RFM69_FREQUENCY=RFM69_868MHZ -DMY_IS_RFM69HW 
LDFLAGS=-pthread 
PREFIX=/usr/local
CC=gcc
CXX=g++
BUILDDIR=build
BINDIR=bin
GATEWAY_DIR=/usr/local/bin
INIT_SYSTEM=systemd
SPI_DRIVER=BCM

So in my case I have these defines:
MY_RADIO_RFM69
MY_RFM69_NEW_DRIVER
MY_GATEWAY_LINUX
MY_DEBUG
LINUX_SPI_BCM
LINUX_ARCH_RASPBERRYPI
MY_RFM69_FREQUENCY=RFM69_868MHZ
MY_IS_RFM69HW