Some pictures of an assembled unit with 3d printed case

I had seemingly unending problems getting sensors to be reliable and about gave up until i switched to ebyte modules.

Since redesigning boards to use their slightly different pinout and moving to their modules I haven't had any issues. A complete turnaround from what i was experiencing before - highly recommended.

@Yveaux this has resolved it, thank you

@ncollins

throw this somewhere in your code:

void reboot() {
  wdt_disable();
  wdt_enable(WDTO_15MS);
  while (1) {}
}

and then calling the reboot (in the entire loop):

void loop() {

  if (motion_change) {
    motionDetected=!motionDetected;
    if (motionDetected) {
      send(msg.set("1"));  // motion detected
    }
    else {
      digitalWrite(LED_BUILTIN,LOW);  //turn-off LED to signify motion no longer detected
      send(msg.set("0"));  // send all-clear to prepare for future detections
    }    
    
    NRF_LPCOMP->EVENTS_CROSS=0;
    motion_change=false;
  }
  else { //must be a scheduled wake-up.  Time to report voltage as a heartbeat.
    batteryVoltage=((float)hwCPUVoltage())/1000.0;  //take voltage measurement after transmission to hopefully measure lowest voltage that occurs. 
    send(msg_S_MULTIMETER_V_VOLTAGE.set(batteryVoltage,3));  //send battery voltage with 3 decimal places
    time = millis();
    if (time > 14400000 ) {
      reboot();
    }
  }
  mySleep(1200000);  //sleep for 20 minutes
}```

try another radio? My gateway is a Pi Zero W and works fine so there's no reason it shouldn't work for you.

irq=18 worked for me for anyone who comes along wondering

@ncollins good news

I wonder if this has anything to do with it?
https://forum.mysensors.org/topic/10705/nrf52-watchdog-problem-myboardnrf5

my pi3b does this as well. it's far and few in between. I even made a watchdog in openhab to "ping" the msgw (requesting an ack) and mysgw responds but it doesn't send out new sensor readings. i thought about expanding the watchdog to watch for all sensor readings and throw up a restart to the gw if it receives no readings in a 10 minute period but mine doesn't fail nearly as consistently as yours so I haven't worried about it too much...

would still like to see a resolution to this as I've moved most of my PIRs and temp sensors to mysgw so when it goes down it can be a bit of a problem.

@scalz
Thanks for the link to the 3.3v USBASP mod!
i have been pulling my hair out trying to get bare 328p chips programmed using a generic ASP

thank you!!!

It's looking more and more like the code is fine and its the sensors i'm using that are the problem.

I got some BM612 (cheaper) from ali supposedly the same as am612 but they don't seem to work right. It's like they trigger once and then never again. Can't find a data sheet for them...

I hooked up a 312 just for kicks and it seems to be working. I doubt I'll deploy any 312s due to what seems to be a VERY narrow range and plus it doesn't match the profile of the round board etc...

Anyway, wanted to say that i think this is all working as its supposed to I just got a bad batch of sensors or they're slightly different in some way

I had initial problems with the 2.4 binding and went MQTT only.
I can't help you at the moment with your problem but if it were me, I'd make it work with MQTT only rather than introduce another binding unless there was no other way. I think I do a couple things with null values and it works fine but I haven't touched it in months (since it just works) so i'm of no actual help right now

@olka
Can't say I remember what I did anymore. Probably suppressed sending in the case of 85 degrees.

@NeverDie
where did you find them for $1.08??

I didn't tune speed at all so they should be running at 2mbps and I've had no issue.

This one in particular for my SMD needs
http://www.ebyte.com/en/product-view-news.aspx?id=111

I haven't used any of the larger, non-SMD versions but i would expect to have similar success.

I had 2 or 3 different SMD versions from no-name vendors (not blobs, at least) that had various issues communicating. These issues included not communicating at all to garbled characters and loads of NACKS.

The pinout is slightly different so I had to make a small change to my board design but other than that everything else was the same. The ebyte modules have (for me) worked first time, every time.

I had seemingly unending problems getting sensors to be reliable and about gave up until i switched to ebyte modules.

Since redesigning boards to use their slightly different pinout and moving to their modules I haven't had any issues. A complete turnaround from what i was experiencing before - highly recommended.

try another radio? My gateway is a Pi Zero W and works fine so there's no reason it shouldn't work for you.

@ncollins good news

I wonder if this has anything to do with it?
https://forum.mysensors.org/topic/10705/nrf52-watchdog-problem-myboardnrf5

@neverdie thanks, i'll look into it and keep my eye on it.

I've been sticking with atmega328p as I've tried nrf51 and 52 but i'm just not smart enough code-wise to get them to work reliably enough. the atmega on the other hand is very reliable and gives me almost no trouble.

i've had many PCBs done by JLPCB and they've all been top notch as far as I can tell.

I'm getting ready to make an integrated nrf24/atmega328 qfn board with them putting the components down soon so I can't answer how the part placement is but if it's like their PCBs it should be good.