Fixed, seems in V2.1.1 it changed to "getControllerConfig".

I'm amazed this hasn't got more attention. A superb contribution to the community and one which I'm sure has taken many hours... Thank you!

In case it helps anyone, after a week I've resolved this.

1. If using the PA version of the nRF with the ESP, it needs to be placed a good distance from the ESP itself. Also, ensure to wrap the nRF board in film and foil (making sure that the foil touches the gold antenna connector).

2. Keep the wires connecting the nRF to the ESP / Arduino as short as possible, I choose to shield mine too as it helped with range.

After a week it's rock solid, and I'm getting circa 400-500 metres!

Just got 4 of these, happy to say they're all '+' models and connect without issues, bingo!

If I recall I tried that, I seem to remember it only works for the sensebender board? Perhaps I'm mistaken though, it was over 1 year ago. @tekka, can you confirm?

@hek I did (Not that I don't trust you), and you're right. Go get yourself a beer and pat yourself on the back

Now if I could just get my ESP8266 to actually not reply to 50% off messages with st=fail.

I've only been trying to get this all working for 3 weeks (sigh).

@pdey That's fantastic, the only thing I was missing with the modified boot loader was debug...

@hek @tekka Any reason why we can't implement this into development, it seems a great feature.

Now if I can only figure out how to apply @pdey 's fix to the current dev branch....

Awesome work Erik!

Thread revival.

I have a sensor powered by 2 AA batteries, does this still stand as a simple way to obtain their status? It was super easy to implement!

That's a possibility, it's outside in a sealed box.

I've brought it inside and will test it in the morning....

@dustin-thurston Mine are certainly plus models, as they connect at 250kbps without issue (nor do they need debug turned on).

@mfalkvidd said in Auto resend on NACK:

https://forum.mysensors.org/post/33832

Would someone be kind enough to point me in the direction of a good software acknowledgement example? I've been building MySensors for 4 years and still have sensors that don't send reliable messages. While most have been replaced with ESP's - these sensors are extremely remote and battery powered (MySensors wins here!).

Currently I use:

void resend(MyMessage &msg, int repeats) {
        int repeat = 1;
        const int repeatDelay = 100;
        boolean sendOK = false;
        while ((sendOK == false) and (repeat <= repeats)) {
                if (send(msg) == true) {
                        sendOK = true;
                } else {
                        sendOK = false;
                        #ifdef MY_DEBUG
                        Serial.print(F("Send error: "));
                        Serial.println(repeat);
                        #endif
                        repeat++;
                        wait(repeatDelay);
                }
        }
}

But this doesn't seem to ensure reliable delivery (some nodes send 10 msgs before sleeping). Often I get multiple messages arriving (I assume this is the burst), but some (often vital) never make it.

@tekka I also see this, issue posted on GitHub.

@fruijs I bought them here: https://www.aliexpress.com/item/32980796969.html?spm=a2g0s.9042311.0.0.61584c4dSzvgS3

Just got 4 of these, happy to say they're all '+' models and connect without issues, bingo!

Is there any indication how the deep sleep performs on these?

Hi,

Thanks for this excellent HA component.

Currently I create children for the voltage and percentage and display them in the HA frontend (lovelace).

It would be nice however if we can utilise the battery_level attribute already present and create a new entity using the dynamic battery icon option. This would prevent unrequired children (less transmissions and data, I have over 25 sensors), and also make it easy to identify sensor battery level. I realise this can be done via a value template, but that's not an ideal solution...

Many thanks in advance.

Hi Guys,

Is anyone here using the Pi with OTA updates? I'm finding them painfully slow (1-2 stream messages every few seconds). It's taking 1 hour per OTA update compared with 2-3 minutes when using the Arduino gateway!

Trying it with the extra config command:

--extra-cxxflags="-DMY_OTA_LOG_RECEIVER_FEATURE"

Hello,

How can I enable 'MY_OTA_LOG_RECEIVER_FEATURE' on the Pi gateway?