Joshua Rich

Similar errors for me: ``` This error originated from a custom integration. Logger: custom_components.ecowitt Source: custom_components/ecowitt/__init__.py:274 Integration: Ecowitt Weather Station First occurred: 9:22:07 AM (39 occurrences) Last logged: 10:00:44 AM...

Hi @wallies, you could say that Heartbeat draws inspiration from Pingbeat and vice versa ;) Heartbeat does a lot of what I wanted to do with Pingbeat eventually (i.e., other...

Hi @zach929, this field should still be there. Rather than adding `loss: false` to every good ping, pingbeat just adds `loss: true` to failed pings (along with the `reason` field...

Hi @zach929 okay, the loss processing is still there, but some refactoring of the code meant that some "loss" conditions were no longer being recorded. With 4f9c249696fcc20b615e3cd0619d8a85e67456ad: * Destination Unreachable...

@atomicom @jegade @zach929 looks like I really made a mess of that last release. Can you try 5.4.1: https://github.com/joshuar/pingbeat/releases/tag/v5.4.1 This should fix both tracking of loss and also stop any...

Hi @ampodobas this could just be a temporary problem. Is it consistently failing at the same place? Can you try with a different user account on the machine (it might...

Hi @joedissmeyer thanks for reporting! I don't actually test on Windows as I don't have easy access to that OS. Just out of curiosity, is this error occurring whether you...

Possibly related to this: https://github.com/tatsushid/go-fastping/issues/14 So right, now, it's likely the losses are false positives a lot of the time with a lot of hosts and small periods. I might...

Hey @drewr I've been working on a re-write of pingbeat that removes the dep on go-fastping. My rough preliminary testing is proving positive results and I'm hoping this artificial loss...

Hey @elvarb, Yep that's definitely one solution. I'd also like to have the option of doing it in pingbeat, either by using/hijacking this functionality that already exists in libbeat, or...