Cumulus Support

dazza1223 wrote: ↑Mon 10 Jun 2024 2:41 pm

freddie wrote: ↑Mon 10 Jun 2024 2:35 pm Sounds almost like the hub is crashing after sending x requests to CMX. That will be a problem with the hub, not MX, if that is the case. Interesting to hear you experienced the same issue dazza.

i got them to send me a new hub and it the same happened to that one to

Interesting. The GW1000 and 1100 work just fine with the MX web server. I've also created my own server for intercepting Ecowitt data calls (I have to manipulate it a bit before passing it to MX) and the GW1100 works just fine with that too. It looks increasingly like there may be a bug in the GW2000 firmware.

It would be informative to hear if anyone else on the forum is using a GW2000 to pass extra sensor data to MX - and whether they are experiencing the same issue.

Yes, hub lights go out and updating on Ecowitt and CMX stops. I have tried 2 hubs. Also a 2560. All with same results.

Picked this up to add solar and UV.

Thanks.

It sounds a bit like CMX does not respond correctly to the http request when the error happens and Ecowitt’s firmware does not have any timeout, and this causes gateway to halt all.

Did I understand correctly, that it is enough to stop CMX and the gateway will immediately recover without needing to reboot?

Two hubs and a 2560 both have the same issue. If no suggestions, I may try to go back to V3 of CMX.

Thanks

Going back to v3 won't change anything mate I hade this problem even on the v3

Also discovering Ecowitt Cloud isn’t working. While logs show the data being received by CMX, it doesn’t use it for extra sensors. I ordered a GW1100 and will try it next. Thought this would be easy

Ok, GW1100 works as expected. It is showing it needs to upgrade firmware. Can anyone verify this upgrade is stable for CMX?

Thanks.

jchurch wrote: ↑Wed 12 Jun 2024 4:01 am Ok, GW1100 works as expected. It is showing it needs to upgrade firmware. Can anyone verify this upgrade is stable for CMX?

With upgrades of firmware you always need to give the version you have and what you wish to upgrade to. There have been some stability issues in the past with the GW1000 but using V2.3.2 works fine for me (I use automatic upgrade of fw) and I believe Ecowitt learned their lesson with pushing out upgrades too fast on any change.

So if you are going for V2.3.2, I would say: yes, it is stable.

Thanks! Went to 2.3.2. CMX is on 4.0.1 b4023. Boxed up the old GW2000. GW1100 is stable.
Will stay with what works.

jchurch wrote: ↑Wed 12 Jun 2024 12:40 pm Will stay with what works.

Sensible.

Just a heads up I brought the GW3000 hoping it would fix those random lock up like the GW2000 had but it seem to be the exact the same

Interesting, I likely missed reading this initial thread as I did not have the GW2000 or other Ecowitt console running at the time. But it sounds very familiar with my current GW2000/LDS01 issue. Latest I have heard from Ecowitt support in our exchanges is that they will be doing a firmware update on my GW2000

Please provide your GW2000 MAC address, and we can push a firmware update to your device. You can then update the firmware and check if it is okay.

Enjoy,
Paul

Ah that's kinda hope full if thay do ..... but because i like the 20 second interval I had to switch to HTTP to get one minute intervals now which it's not really helpful

Is there a little hack to get then 20 second interval while using the HTTP?

my GW2000s and my GW3000 (all latest firmware) work flawlessly with CMX (build 3283 and 4084) as they do with other data loggers like weewx, Meteobridge etc. - with all interfaces provided by CMX

Unfortunately your posts are far too implicit for me ... I do not get what your issue seems to be and what exactly you are talking about ...
Being more precise in describing the symptoms and what exactly you are doing and what exactly doesn't (seem to) work would help though.
Example:
"...i like the 20 second interval I had to switch to HTTP to get one minute intervals..."
Sorry to say that, but this sentence doesn't make any sense to me - and my crystal ball is on vacation ...
what exactly are you talking about ? Such implicit talk is horrible for any error tracking ...
http is used in many different scenarios ...
when I properly understand your issue, I might be able to help or to point you in the right direction

My GW2000 update:

Latest I have heard from Ecowitt support in our exchanges is that they will be doing a firmware update on GW2000

I noticed the firmware update and updated both GW2000s. All seems to be ok so far.

Enjoy,
Paul