Cumulus Support

Starting using HTTP in CumulusMX instead of TCP.

Every 20 minutes or so the following errors occur

2025-02-17 15:40:01 - GetSensorIds: No sensor data returned
2025-02-17 15:40:01 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 15:20:00 - GetSensorIds: No sensor data returned
2025-02-17 15:20:00 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 15:00:02 - GetSensorIds: No sensor data returned
2025-02-17 15:00:02 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 14:20:02 - GetSensorIds: No sensor data returned
2025-02-17 14:20:02 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).

Enclosed Diags file

No virus protection on the Raspberry.

The same errors occur on a PC from the same GW1100

Errors don't occur with TCP.

The same router.

Any Idea?

I haven't seen that reported before, I run a GW1100 as a test system and can't say I've seen it either.

You will not see it with the TCP binary protocol as that does not make those calls.

It is getting the live data immediately before and after the failure fine, so the data is not being interrupted.

All those calls are doing of any significance is checking the battery status, so nothing too much to worry about. At some convenient point, stop MX and power cycle the GW1100 and see if that improves things?

I had already powered down the GW1100. The diagnostic files are after the power down. The Raspberry Pi 4 was also rebooted.

These are the latest errors
2025-02-17 21:40:02 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 21:20:00 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 21:00:02 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 20:40:01 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 20:20:03 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 20:00:02 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 19:40:00 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 19:00:01 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 18:20:01 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 18:00:03 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 17:40:02 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 17:20:00 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 17:00:03 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).
2025-02-17 16:40:01 - GetSensorInfo: HTTP Error - Response status code does not indicate success: 500 (Server Error).

It is strange it is every 20 minutes exactly.
When I have my PC running the same error occurs at 20-minute intervals. The PC has Antivirus software, and it does not show any conflicts

MX only makes those calls every 20 minutes.

Some of them do work, 18:40, 19:20.

The calls are made immediately after the previous request for the live data, I'm wondering if adding a small delay will help, it gives the GW1100 a bit of time to "recover" - I'll add it to the next release anyway and we can see...

Thanks Mark

If I run my PC and Raspberry at the same time, will they conflict with each other. Of course, the time on each maybe seconds different.

Ian

Well, it will cause a bit of extra load on the GW, but it should be OK.