@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?

@tekka said in MYSBootloader 1.3.0-beta.3:

@Mark-Swift said in MYSBootloader 1.3.0-beta.3:

@tekka said in MYSBootloader 1.3.0-beta.3:

@Mark-Swift Hmm, that's odd - just tested it here with the latest dev and all is ok. Can you post the logs + node sketch?

@tekka, just tried again, perhaps I'm missing something obvious?

I have the gateway and node using the latest dev branch, I click the node in MYS and then request a signal report - I see a tx in the log but nothing further? Do I need anything in the node sketch or the gateway? Does this work with the NRF's?

Did you try with 1.3.0-beta.4? https://github.com/mysensors/MySensorsBootloaderRF24/tree/development

@tekka that did it, it's now working... now to figure out what the returned signal report numbers mean :)

@tekka said in MYSBootloader 1.3.0-beta.3:

@Mark-Swift Hmm, that's odd - just tested it here with the latest dev and all is ok. Can you post the logs + node sketch?

@tekka, just tried again, perhaps I'm missing something obvious?

I have the gateway and node using the latest dev branch, I click the node in MYS and then request a signal report - I see a tx in the log but nothing further? Do I need anything in the node sketch or the gateway? Does this work with the NRF's?

@tekka said in MYSBootloader 1.3.0-beta.3:

@Mark-Swift This feature only works on MySensors >=2.2.0

@tekka I'm using the latest dev branch on all my nodes and gateway...

@tekka try as I might, I can't get the nodes to respond to the new 'signal report' option in MYS Controller, any ideas why?

I'd also love to use the signal report features, I thought it was enabled by default in MS, seems not to work here when I request an item from MYS?

@tekka it's been some time since I flashed the bootloader, I notice I currently have a lot of different hex files (which I believe I compiled myself), do I no longer need different files for different speeds, i.e 16 / 8 /1Mhz?

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?

@manutremo please share your method so we can all benefit :)

@Yveaux said in ESP8266 WiFi gateway port for MySensors:

@Mark-Swift that issue apparently addressed an issue in the vs1053 library, which surfaced because the esp8266 doesn't support interrupts on spi transfers.
The issue was closed because the vs1053 library was modified to support esp8266, unfortunately not because esp interrupt support for spi was implemented...

@Yveaux You're right, should have read more before jumping to conclusions :(

Damn, I thought I could finally dump my serial gateway!

@hek @Yveaux I see the blocking issue on the ESP side has been closed... Does this mean we can now use the ESP in high traffic environments? How can we test it, I assume we also need to activate IRQ for the NRF in the ESP gateway code?