@kduino thanks for clearing that up.

st=OK:

means that the node is getting a hardware acknowledgement on the sent message. So something (probably the gateway unless you have other MySensors nodes nearby) receives the message and acknowledges it, but then nothing happens.

Could you add #define MY_DEBUG_VERBOSE_RF24 to both sketches to see if that can give a clue?

@kduino looks like all functions (present, setup, loop) are missing.

@coconuts looks like the IRrecv library is present both in your sketch folder and in the libraries folder? IRrecv Should probably only exist in the libraries folder.

@titvs I don’t think burn-in is a problem with these displays, but an elegant solution vould be to turn it on/off based on a PIR/motion sensor. Maybe you already have such a sensor in the same room?

@rmh yes millis is frozen during sleep.
On the atmega328 (which pro mini is based on), sleep uses the watchdog to keep time. No interrupt is involved.

Welcome to the MySensors forum @rmh

The debug log will show details on what is happening. You can also check the return value from the sleep function to see the reason for waking up.

Documentation for the sleep function: https://www.mysensors.org/download/sensor_api_20#sleeping

@ricorico94 did you define these in your sketch, before including MySensors.h?

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

@koresh is it still possible to purchase this board? The ebid link doesn't work anymore.

@neverdie said in Windows PopCom tool shows which USB serial ports are available:

it must be hidden in plain sight

Indeed

@sghazagh did you add the #define before including MySensors.h? (common mistake is to add it after)

I am not familiar with this particular board, but I think other esp8266-based boards use the other SPI for communicating with the flash memory.