Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 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
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 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
Latest update MX v3.10.3 build 3120 Again failed to discover
-
- Posts: 13
- Joined: Tue 05 Feb 2019 11:05 pm
- Weather Station: generic
- Operating System: windows 7
Latest update MX v3.10.3 build 3120 Again failed to discover
The latest update Cumulus MX v3.10.3 build 3120, 21-Mar-2021 I am sorry to report again failed to discover any Device.
You do not have the required permissions to view the files attached to this post.
- mcrossley
- Posts: 12765
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Latest update MX v3.10.3 build 3120 Again failed to discover
It is also reporting that it cannot connect to the device either - have you configured an IP address?
-
- Posts: 13
- Joined: Tue 05 Feb 2019 11:05 pm
- Weather Station: generic
- Operating System: windows 7
Re: Latest update MX v3.10.3 build 3120 Again failed to discover
Hi
Yes if i manually do the ip address it works, im hoping the little fix i have done in the router may solve the problem until the next update Have set up the DHCP to allocate the weather station a ip address internet stability where i am is worse than a 4th world so constant dropouts
Thanks for the Quick reply much appreciated
Yes if i manually do the ip address it works, im hoping the little fix i have done in the router may solve the problem until the next update Have set up the DHCP to allocate the weather station a ip address internet stability where i am is worse than a 4th world so constant dropouts
Thanks for the Quick reply much appreciated
You do not have the required permissions to view the files attached to this post.
- mcrossley
- Posts: 12765
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Latest update MX v3.10.3 build 3120 Again failed to discover
Could you post your latest MSdiags file please.
- mcrossley
- Posts: 12765
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Latest update MX v3.10.3 build 3120 Again failed to discover
Please update to version 3.10.4 it addresses a fatal issue with the GW1000 in 3.10.3.
Only the CumulusMX.exe file has changed between these two releases.
Only the CumulusMX.exe file has changed between these two releases.
-
- Posts: 13
- Joined: Tue 05 Feb 2019 11:05 pm
- Weather Station: generic
- Operating System: windows 7
Re: Latest update MX v3.10.3 build 3120 Again failed to discover
Hi Mr Crossley
Due to the time difference between us i have just seen your message
The router fix is working well i appreciate all your work and time and effort i will download the new one
Thank you
Due to the time difference between us i have just seen your message
The router fix is working well i appreciate all your work and time and effort i will download the new one
Thank you
-
- Posts: 13
- Joined: Tue 05 Feb 2019 11:05 pm
- Weather Station: generic
- Operating System: windows 7
Re: Latest update MX v3.10.3 build 3120 Again failed to discover
I just downloaded the new fix still no joy
But the router fix I did is working so im not that worried
I appreciate the work you do
Also just in case this maybe a problem its updated its latest firmware to V1.6.6
Thank you
But the router fix I did is working so im not that worried
I appreciate the work you do
Also just in case this maybe a problem its updated its latest firmware to V1.6.6
Thank you
You do not have the required permissions to view the files attached to this post.
- mcrossley
- Posts: 12765
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Latest update MX v3.10.3 build 3120 Again failed to discover
The discovery depends on Cumulus receiving a muticast message from your GW1000, it could be your router is not forwarding those messages for some reason.
- Gyvate
- Posts: 295
- Joined: Wed 16 Dec 2020 2:14 pm
- Weather Station: GW1x00/WH2650WiFi/HP2553/GW2000
- Operating System: Win 11 (PC/RPi), Raspbian 11,WSL
- Location: Saarbrücken, Germany
- Contact:
Re: Latest update MX v3.10.3 build 3120 Again failed to discover
one side remark here:
Experience of many users shows that using a dynamically assigned IP address for the GW1000 can lead to multiple unwanted issues at the GW1000 end.
Best practice so far is - as the address needs to come via DHCP - to link (bind) that IP address once received to the MAC address of the GW1000
in your router (for IP address & MAC --> WSView app, device list).
Like this it becomes a quasi fixed IP address (and avoids a host of potential issues).
Then, after a (wanted or unwanted) restart, power-cycle, even factory reset of the GW1000,
it keeps on using the same IP address (even though primarily assigned via DHCP).
Therefore auto-detection may be an interesting feature, but often not very useful because of the potentially occurring issues
.
And, once you have more than one GW1000 (or WH2650), you won't want in most cases CumulusMX to select the GW1000 it reads and stores (and publishes) data from,
but you want to choose yourself. Hence configuring the GW1000 IP address in the settings (and making it permanent) is a useful thing to do.
And there are quite a few users with two (or even more) GW1000 (e.g. test and production system).
Experience of many users shows that using a dynamically assigned IP address for the GW1000 can lead to multiple unwanted issues at the GW1000 end.
Best practice so far is - as the address needs to come via DHCP - to link (bind) that IP address once received to the MAC address of the GW1000
in your router (for IP address & MAC --> WSView app, device list).
Like this it becomes a quasi fixed IP address (and avoids a host of potential issues).
Then, after a (wanted or unwanted) restart, power-cycle, even factory reset of the GW1000,
it keeps on using the same IP address (even though primarily assigned via DHCP).
Therefore auto-detection may be an interesting feature, but often not very useful because of the potentially occurring issues
.
And, once you have more than one GW1000 (or WH2650), you won't want in most cases CumulusMX to select the GW1000 it reads and stores (and publishes) data from,
but you want to choose yourself. Hence configuring the GW1000 IP address in the settings (and making it permanent) is a useful thing to do.
And there are quite a few users with two (or even more) GW1000 (e.g. test and production system).
Meteotemplate http://meshka.eu/meteo/template
pwsDashboard http://meshka.eu/pwsWD
CumulusMX http://meshka.eu/CumulusMX
CUtils http://meshka.eu/CUtils
overview (more): http://meshka.eu
pwsDashboard http://meshka.eu/pwsWD
CumulusMX http://meshka.eu/CumulusMX
CUtils http://meshka.eu/CUtils
overview (more): http://meshka.eu