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?
Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Using HTTP with Ecowitt GW 1100 instead of TCP
Moderator: mcrossley
-
BrunswickWeather
- Posts: 87
- Joined: Fri 11 Mar 2011 2:04 am
- Weather Station: Ecowitt GW1103
- Operating System: windows 11 Pro/Raspberry pi 4
- Location: Brunswick Australia
Using HTTP with Ecowitt GW 1100 instead of TCP
You do not have the required permissions to view the files attached to this post.
- mcrossley
- Posts: 14384
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Using HTTP with Ecowitt GW 1100 instead of TCP
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?
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?
-
BrunswickWeather
- Posts: 87
- Joined: Fri 11 Mar 2011 2:04 am
- Weather Station: Ecowitt GW1103
- Operating System: windows 11 Pro/Raspberry pi 4
- Location: Brunswick Australia
Re: Using HTTP with Ecowitt GW 1100 instead of TCP
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
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
- mcrossley
- Posts: 14384
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Using HTTP with Ecowitt GW 1100 instead of TCP
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...
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"
-
BrunswickWeather
- Posts: 87
- Joined: Fri 11 Mar 2011 2:04 am
- Weather Station: Ecowitt GW1103
- Operating System: windows 11 Pro/Raspberry pi 4
- Location: Brunswick Australia
Re: Using HTTP with Ecowitt GW 1100 instead of TCP
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
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
- mcrossley
- Posts: 14384
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Using HTTP with Ecowitt GW 1100 instead of TCP
Well, it will cause a bit of extra load on the GW, but it should be OK.