https://hackaday.com/2021/07/05/diy-air-quality-sensor/

Ok, finally it's solved. I installed everything from scratch. Then installed your sandeep lib from your github. And finally added the LEDs and Buttons to the variants.h. That compiled successfully. And my problem was that the sensor is sleeping and I couldn'T get a heartbeat answered. So everything is clear and now testing...

Hi, I complied your code for NRF51822 chip but I am getting the following errors at compile Arduino: 1.8.11 (Mac OS X), Board: "MyBoardNRF5 nRF51822, 16 kB RAM, 256 kB flash (xxaa), None, Crystal Oscillator" WARNING: library LIS2DW12-master claims to run on stm32, avr, sam architecture(s) and may be incompatible with your current board which runs on nRF5 architecture(s). /Users/puneit/Google Drive/MySensor/NRF51822/doorsensor/doorsensor.ino: In function 'void board_Init()': doorsensor:417:3: error: 'NRF_NFCT' was not declared in this scope NRF_NFCT->TASKS_DISABLE = 1; ^ doorsensor:419:13: error: 'struct NRF_UICR_Type' has no member named 'NFCPINS' NRF_UICR->NFCPINS = 0; ^ doorsensor:421:3: error: 'NRF_SAADC' was not declared in this scope NRF_SAADC ->ENABLE = 0; ^ doorsensor:422:3: error: 'NRF_PWM0' was not declared in this scope NRF_PWM0 ->ENABLE = 0; ^ doorsensor:423:3: error: 'NRF_PWM1' was not declared in this scope NRF_PWM1 ->ENABLE = 0; ^ doorsensor:424:3: error: 'NRF_PWM2' was not declared in this scope NRF_PWM2 ->ENABLE = 0; ^ doorsensor:425:3: error: 'NRF_TWIM1' was not declared in this scope NRF_TWIM1 ->ENABLE = 0; ^ doorsensor:426:3: error: 'NRF_TWIS1' was not declared in this scope NRF_TWIS1 ->ENABLE = 0; ^ Multiple libraries were found for "Wire.h" Used: /Users/puneit/Library/Arduino15/packages/sandeepmistry/hardware/nRF5/0.6.0/libraries/Wire Not used: /Users/puneit/Documents/Arduino/libraries/Wire Multiple libraries were found for "SPI.h" Used: /Users/puneit/Library/Arduino15/packages/sandeepmistry/hardware/nRF5/0.6.0/libraries/SPI Not used: /Users/puneit/Documents/Arduino/libraries/SPI exit status 1 'NRF_NFCT' was not declared in this scope Invalid library found in /Users/puneit/Documents/Arduino/libraries/ESP8266SdFat: no headers files (.h) found in /Users/puneit/Documents/Arduino/libraries/ESP8266SdFat Invalid library found in /Users/puneit/Documents/Arduino/libraries/SoftwareSerial: no headers files (.h) found in /Users/puneit/Documents/Arduino/libraries/SoftwareSerial Invalid library found in /Users/puneit/Documents/Arduino/libraries/ArduinoHwNRF5-master: no headers files (.h) found in /Users/puneit/Documents/Arduino/libraries/ArduinoHwNRF5-master Invalid library found in /Users/puneit/Documents/Arduino/libraries/arduino-nRF5-master: no headers files (.h) found in /Users/puneit/Documents/Arduino/libraries/arduino-nRF5-master Invalid library found in /Users/puneit/Documents/Arduino/libraries/ArduinoBoards-master: no headers files (.h) found in /Users/puneit/Documents/Arduino/libraries/ArduinoBoards-master This report would have more information with "Show verbose output during compilation" option enabled in File -> Preferences.

Nice project manufacturers datasheets, RF appnotes etc all mention this, with results for different usecases (like gnd plane size etc). I mentioned it a few times on the forum: nothing under or near antenna (keep out zone) their matching circuit, and CE/FCC certif are based on their development boards+their antenna if external, often without enclosure. there are a very few pcb antennas which are resilient to untuning. ceramic or meandered pcb are usually more compact but less resilient (like when you approach your hand and device suddently has better or worst communication) once you change any of these parameters (board shape, gnd size, enclosure etc), it breaks FCC, and may need retuning, still you can get useable range. "ideally" tuning should be done once enclosed for example. manufacturers can't cover all cases. on my side, I try to follow these rules. and when interested in a design or a device, I check this. Mainly the routing+gnd, antenna choice, keepout zone, and orientation vs my usecase (long range needed or not for example)

@Mishka Very nice work indeed. One question though: I don't see an antenna of any kind built into the PCB. Maybe I'm just not seeing it, or is there none? I do see a connection for an off-board near field antenna, but off-hand I don't see where the antenna is for 2.4Ghz RF. Oh, I see it now. You're using a chip antenna. Got it. Well, now that you've been using it for a while, how is the Raybeacon working out for you?

Update on the project. New version added to openhardware.io

@berkseo Good question. The code seemed good at the time I wrote it, but I can't say that it was extensively tested. I may circle back to it at a future date, and if so, I'll take a closer look. Even with more than 500 downloads of the code, no one has posted any feedback on how well (or not) it has run. Also, I not sure how compatible the posted code is with newer releases of the mysensors library.