No Email after WLL lost contact

[ConligWX]

Mark

I'm still investigating why my Airlink and WLL went offline earlier today but I only noticed this after a few emails from weatherlink and AWEKAS had notified me of no data had been received.

CumulusMX alarms are set like so:

Screenshot 2023-02-22 223029.png

yet I never received a single email from CumulusMX. Are my alarm settings correctly setup for email or is this feature broken?

logfile below.

[ConligWX]

seems like I have random disconnects of the WLL and Airlink after I had disabled syslog from my UDM Pro. dont kow as yet if this is the cause as yet but it is likely since timings are very close. I have submitted my support file and syslog to Unifi for diagnosis.

[mcrossley]

I get data stopped emails regularly - at least once a week when my router does its scheduled reboot.

have you setup the email server correctly in Internet Settings?

Does sending a test email work?

[ConligWX]

yes test emails work fine. no blocking of emails. I just thought it strange I did not see anything from cumulus, before other web services reported hours later.

[ConligWX]

is it because the WLL error did not report the actual words of sensor contact lost?

Code: Select all

2023-02-22 16:01:30.868 WLL Health: Get WL.com Historic Data
2023-02-22 16:01:31.395 AirLinkHealth: Outdoor - FW version = 2020-10-21
2023-02-22 16:01:31.396 WLL FW version = 2021-11-05
2023-02-22 16:01:31.396 WLL: Percentage good packets received from WLL 99.22% - (1387,177490)
2023-02-22 16:03:27.515 GetWllCurrent: Error processing WLL response
2023-02-22 16:03:27.515 GetWllCurrent: Error: No route to host
2023-02-22 16:03:27.515 ERROR: No current data received from the WLL, DataStopped triggered
2023-02-22 16:03:31.920 ERROR: No broadcast data received from the WLL for 30 seconds
2023-02-22 16:03:36.730 GetWllCurrent: Error processing WLL response
2023-02-22 16:03:36.730 GetWllCurrent: Error: No route to host
2023-02-22 16:03:45.947 GetWllCurrent: Error processing WLL response
2023-02-22 16:03:45.947 GetWllCurrent: Error: No route to host
2023-02-22 16:03:55.163 GetWllCurrent: Error processing WLL response
2023-02-22 16:03:55.163 GetWllCurrent: Error: No route to host
2023-02-22 16:04:00.071 *** Data input appears to have stopped
2023-02-22 16:04:01.920 ERROR: No broadcast data received from the WLL for 30 seconds
2023-02-22 16:04:04.379 GetWllCurrent: Error processing WLL response
2023-02-22 16:04:04.379 GetWllCurrent: Error: No route to host
2023-02-22 16:04:27.867 GetWllCurrent: Error processing WLL response
2023-02-22 16:04:27.867 GetWllCurrent: Error: No route to host
2023-02-22 16:04:31.920 ERROR: No broadcast data received from the WLL for 30 seconds
2023-02-22 16:04:47.483 GetWllCurrent: Error processing WLL response
2023-02-22 16:04:47.483 GetWllCurrent: Error: No route to host
2023-02-22 16:05:00.093 *** Data input appears to have stopped

[ConligWX]

i'm guessing the error shows:

Code: Select all

ERROR: No current data received from the WLL, DataStopped triggered

which is a "Data connection is lost" and not a "Sensor contact lost" alarm? Therefore I needed emails ticked for the "Data connection is lost"?

[mcrossley]

Sorry I missed that distinction.

Yes, sensor contact lost is when the station stops recieving the data from some/all of its sensors. Data stopped is when MX stops receiving any useful data from the station.