@demeda1 Possibly a silly question, but since any detection method will require space they pass through to be constrained, have you considered conductivity across one axis and a simple microswitch across the the other to detect all objects passing ?

@dzjr I believe the point @Grubstake was making is to ensure solid and stable connection for voltage and ground to the board itself, not elsewhere, the issue is to ensure stability.
Glad the stronger pullup solved your problem but would caution on choice of cable. Telephone wire or Cat5 as also stated is known to work well and reliably for One-Wire, is cheap and readily available. Screening or grounding unused cores does affect capacitance, which may lead to problems in final layout.

@alowhum But that is where you are confusing matters when you refer to the Gateway in some role of PRE-controller to make up for a perceived inadequacy in the selected Controller.
From the Node to the Controller the Gateway is a simple access point for various pathways no matter how complex or simple the Node or Controller functionality.
Likewise your first example quotes a thermostat and BME280 as if each has some inherent capability to communicate as a Node, despite prior mention of the NRF52 to which they would normally be connected, which Node would then communicate the individual data streams to the Controller.

How these individual streams are treated at the Controller are down to the User's selected Controller and how it is configured, adding complexity anywhere else in the pipeline doesn't make it more user friendly at all.

@dzjr Sorry for any misunderstanding, the loops I was referring to are the sensor cable loops in your photo.
I did read somewhere that different pullup resistors were recommended by different suppliers of the waterproof versions, values from 10k to 2k2, rather than the usual 4k7, some said the pullup should be on the Arduino end, others on the last sensor on the line, so worth experimenting, perhaps even a sacrificial length of additional cable to alter or extend spacing ?
What is crucial to these devices is digital signal timing, hence constraints on layout architecture and cable capacitance, the pullup resistor only alters the circuit's speed of High/Low transitions.
Here bare DS18B20s on Cat5 cable (low capacitance) works fine on a 3v Arduino for 12 sensors, so it can be done.

@dzjr Now you have to figure out why only #8 did not work, so progress even if a digital device on One-Wire has not yet sunk in...
There is no physical loop 8 I can see, so how is#8 connected in the chain?

@alowhum { I don't mind that MySensors uses one node I per device "under the hood". But perhaps the gateway could present the one device as 6 separate devices to the controller? And when it gets requests for one of those 6 devices, it just merges things back?}
I really look forward to you developing this concept further with a proven working mechanism, but until your solution is revealed, I guess I don't mind either, the multiple devices per node "on the roof" via a dumb gateway are working just fine, leaving the Controller to do the smart stuff.

@dzjr If you cannot daisy chain them because there is no sequential route between locations, use a separate pin for each data line (powered via resistor) and communicate with each line in turn.
The line here is using 3 cores in 20-30m of Cat5e cable to ensure each chip is physically sequential on the line.
When I added a further sensor location, a loop had to be spliced in to keep the line a daisy chain. It is a small house, the length is purely down to the route, and cable is cheap.

@dzjr Check that you can address all the sensors and retrieve the temperatures, from your previous post you may have a problem with your topology not conforming to the One-Wire architecture.
Also see my reply to @oneyb, locking the chip unique addresses to child IDs saves on analgesics...

@gerard-van-seventer One year, one Node, 12 sensors, send Temp every 5 minutes, Domoticz, never skipped a beat. Quirky ?

@oneyb Sure, you can Google it but will post my own node's sketch as it is to hand, have omitted the Node device specific lib from the top however...

/**
   The MySensors Arduino library handles the wireless radio link and protocol
   between your home built sensors/actuators and HA controller of choice.
   The sensors forms a self healing radio network with optional repeaters. Each
   repeater and gateway builds a routing tables in EEPROM which keeps track of the
   network topology allowing messages to be routed to nodes.
   Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
   Copyright (C) 2013-2015 Sensnology AB
   Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
   Documentation: http://www.mysensors.org
   Support Forum: http://forum.mysensors.org
   This program is free software; you can redistribute it and/or
   modify it under the terms of the GNU General Public License
   version 2 as published by the Free Software Foundation.
 *******************************
   DESCRIPTION
   Example sketch showing how to send in DS1820B OneWire temperature readings back to the controller
   http://www.mysensors.org/build/temp
   Enhanced Version to keep ChildIDs fix based on petewill's http://forum.mysensors.org/topic/2607/video-how-to-monitor-your-refrigerator.
  - Present Dallas-Hardware-ID as comment https://github.com/rejoe2/MySensors-Dallas-Address-ChildID-Consistency
*/

// Enable debug prints to serial monitor
//#define MY_DEBUG

// Enable to print out an array of the attached DallasSensors to Serial
// comment this after initial setup and adopt MAX_ATTACHED_DS18B20 accordingly
////#define PRINT_ARRAY

// Enable and select radio type attached
////#define MY_RADIO_NRF24
#define MY_RADIO_RFM69  // Define for using RFM69 radio
#define MY_RFM69_FREQUENCY RF69_433MHZ  // Define for frequency setting. Needed if you're radio module isn't 868Mhz (868Mhz is default in lib)
#define LedPin 6
#define MY_RFM69_NETWORKID 101  // Default is 100 in lib. Uncomment it and set your preferred network id if needed
#define MY_NODE_ID 5  //Manually set the node ID here. Comment out to auto assign
#include <SPI.h>
#include <MySensors.h>
#include <DallasTemperature.h>
#include <OneWire.h>
#define COMPARE_TEMP 1 // Send temperature only if changed?
#define ERASE_HASH // Clear EEPROM, if no 1w-device is present?
#define ONE_WIRE_BUS 16 // Pin where dallase sensor is connected 
#define MAX_ATTACHED_DS18B20 12

uint8_t DS_First_Child_ID = 7; //First Child-ID to be used by Dallas Bus; set this to be higher than other Child-ID's who need EEPROM storage to avoid conflicts
OneWire oneWire(ONE_WIRE_BUS); // Setup a oneWire instance to communicate with any OneWire devices (not just Maxim/Dallas temperature ICs)
DallasTemperature sensors(&oneWire); // Pass the oneWire reference to Dallas Temperature.
float lastTemperature[MAX_ATTACHED_DS18B20];
unsigned long SLEEP_TIME = 300000; // Sleep time between reads (in milliseconds)WAS 30000
boolean metric = true;

// Initialize temperature message
MyMessage DallasMsg(0, V_TEMP);
//MyMessage msgId(0, V_ID);

#ifdef PRINT_ARRAY
DeviceAddress dallasAddresses[8];
#else
DeviceAddress dallasAddresses[] = {
  {0x28, 0xFF, 0xB0, 0xA8, 0x74, 0x16, 0x03, 0x67},
  {0x28, 0xFF, 0x78, 0xED, 0x74, 0x16, 0x04, 0x99},
  {0x28, 0xFF, 0x86, 0xC7, 0x73, 0x16, 0x05, 0xD2},
  {0x28, 0xFF, 0xE6, 0xD4, 0x73, 0x16, 0x05, 0x73},
  {0x28, 0xFF, 0xD6, 0xDB, 0x74, 0x16, 0x03, 0xCA},
  {0x28, 0xFF, 0x6E, 0x29, 0x80, 0x16, 0x05, 0x03},
  {0x28, 0xFF, 0xB9, 0xE1, 0x73, 0x16, 0x05, 0x40},
  {0x28, 0xFF, 0x9B, 0x5E, 0x80, 0x16, 0x05, 0x59},
  {0x28, 0xFF, 0x5F, 0xFC, 0x74, 0x16, 0x03, 0x04},
  {0x28, 0xFF, 0x18, 0xD0, 0x73, 0x16, 0x05, 0x79},
  {0x28, 0x23, 0xAE, 0x10, 0x0A, 0x00, 0x00, 0x32},
  {0x28, 0xAF, 0xA7, 0x10, 0x0A, 0x00, 0x00, 0x56},
};
#endif

int  resolution = 10;
int  conversionTime = 750;

void before() {
  conversionTime = 750 / (1 << (12 - resolution));
  // Startup up the OneWire library
  sensors.begin();
  // requestTemperatures() will not block current thread
  sensors.setWaitForConversion(false);
  // Fetch the number of attached temperature sensors
  //numSensors = sensors.getDeviceCount();
#ifdef PRINT_ARRAY
  printAddressArray();
#endif

}

void presentation()  {
  // Send the sketch version information to the gateway and Controller
  sendSketchInfo("Dallas Temp, fix Array", "1.0");
  // Register all sensors to gw (they will be created as child devices)
  // Fetch the number of attached temperature sensors
  // Present all sensors to controller
  for (int i = 0; i < MAX_ATTACHED_DS18B20; i++) {
    present(DS_First_Child_ID + i, S_TEMP);
  }
}

void setup() 
{
//  for (int i = 0; i < MAX_ATTACHED_DS18B20; i++) {
//      send(msgId.setSensor(DS_First_Child_ID + i).set(dallasAddresses[i], 8));
//  }
//metric = getControllerConfig().isMetric;
pinMode(LedPin, OUTPUT);
}


void loop() {
  // Fetch temperatures from Dallas sensors
  sensors.requestTemperatures();
  // sleep() call can be replaced by wait() call if node need to process incoming messages (or if node is repeater)
  wait(conversionTime);
  // Read temperatures and send them to controller
  for (int i = 0; i < MAX_ATTACHED_DS18B20; i++) {
    // Fetch and round temperature to one decimal; original method uses "sensors.getTempCByIndex(i)"
    float temperature = static_cast<float>(static_cast<int>((metric ? sensors.getTempC(dallasAddresses[i]) : sensors.getTempF(dallasAddresses[i])) * 10.)) / 10.;

    // Only send data if temperature has changed and no error @@@@@@@@@@ The compare is not working properly here
#if COMPARE_TEMP == 1
    if (lastTemperature[i] != temperature && temperature != -127.00 && temperature != 85.00) {
#else
    if (temperature != -127.00 && temperature != 85.00) {
#endif
      // Send in the new temperature
      send(DallasMsg.setSensor(i + DS_First_Child_ID).set(temperature, 1));
      // Save new temperatures for next compare
      lastTemperature[i] = temperature;
    }
  }
  wait(25);
  digitalWrite(LedPin,HIGH);
  wait(25);
  digitalWrite(LedPin,LOW);
  wait(25);
  
  sleep(SLEEP_TIME);
}


//Helper funktion for setting things up
////void printAddressArray() {
  // start serial port
////  Serial.begin(115200);
  // show the addresses we found on the bus
////  Serial.println("Copy the following to the DallasAddresses array,");
////  Serial.print("set MAX_ATTACHED_DS18B20 to ");
////  Serial.println(sensors.getDeviceCount());
////  Serial.println("and comment line #define PRINT_ARRAY for regular operation");
////  for (uint8_t i = 0; i < sensors.getDeviceCount(); i++) {
////    if (!sensors.getAddress(dallasAddresses[i], i))
////    {
////      Serial.print("Unable to find address for Device ");
////      Serial.println(i);
////      Serial.println();
////    }
////    Serial.print("{");
////    for (uint8_t j = 0; j < 8; j++)
////    {
////      Serial.print("0x");
////      // zero pad the address if necessary
////      if (dallasAddresses[i][j] < 16) Serial.print("0");
////      Serial.print(dallasAddresses[i][j], HEX);
////      if (j < 7) Serial.print(", ");
////      else Serial.println("},");
////    }
////  }
////  wait(SLEEP_TIME * 20);
////}

This is the work of others more clever but it works a treat, hopefully it helps.
The REM'd part at the bottom if I recall correctly test runs the individual devices... It's been a while....