Weather Station Hardware > Ambient Weather and Ecowitt and other Fine Offset clones

HOW to connect a GW1000, a WH2650 (clone) or other consoles to WiFi

(1/3) > >>

Gyvate:
As this has become a frequently reported / posted issue here in the forum, below the instructions and prerequisites for a successful connection of a GW1000 or other consoles with GW1000 functionality (e.g. WH2650, WH2600Pro WiFi, Steinberg sbs-ws-600, Waldberg Halley ....)

Below configuring your console / pairing it with your router is described for the (Android, iOS) WSView or awnet app.
A possibility to do this on a Windows PC is described later in this thread: https://www.wxforum.net/index.php?topic=41575.msg430951#msg430951
 :!: using the WS Tools app as (wrongly) described in some reseller manuals will NOT work - you need the WSView app  :!:

The pairing process consists of several steps which are transparent to the user but need all to be completed for the pairing to be successful. The pairing of your GW1000 with your local WiFi router/access point is successful, when an entry like
GW1000-WIFIxxxx
192.168.xxx.xxx (or other private network segments starting with 10. or 172.)
MAC:XX:XX:XX:XX:xx:xx (the last 4 characters are the 4 x-marked characters in the GW1000-WIFIxxxx entry)
appears in the device list of the WSView app

for WS-2902 / WS-2910C  / WS2320 / WH4000SE / WH3000SE etc. WiFi consoles, the below process is the same - only the entry in the Device List will be a bit different, you CANNOT see live data, you can only configure sensor data posting to Weather Networks and to a customized server.
For Ambient consoles you are supposed to use the awnet app (for all other [re-]sellers the WSView app is to be used - however, Ambient consoles can also be paired with the WSView app, for Weather Networks use the awnet app).

Here the device list entry will be:
EasyWeather-WIFIxxxx V.1.5.9 (or AMBWeather-WIFIxxxx V2.6.8 in the awnet app)
192.168.xxx.xxx
MAC: XX:XX:XX:XX:xx:xx
(the version number will depend on the WiFi-firmware version installed)

In case of an Ambient WS2000/WS5000 console (or an Ecowitt HP2551, Froggit HP1000Pro SE) you can do the weather network configuration either in the WSView/awnet app or in the console itself.
These consoles can also be connected to WiFi from inside the console.

 [ You are not allowed to view attachments ]
clicking on this entry will show the live data of the sensors which the GW1000 receives in the WSView app

Prerequisites:
1. download the latest version of the WSView app to your Android or iOS smartphone/tablet
(sometimes the manuals of clone resellers speak of the also existing WSTool app - this is wrong and will not work for the pairing)

2. if your WIFI router / access point transmits on both 2.4 GHz and 5 GHz bands, switch off the 5 GHz band during the pairing process. You can switch in on again after the successful pairing.

3. de-activate the mobile data option of your smart phone (if you don't know how to do this, put the phone/tablet in flight mode and then switch on the WiFi (only!)). After the successful pairing the mobile phone functionality can be switched on again.
Removing the SIM card temporarily has the same effect as de-activating mobile data (in case you do not figure how to switch it off)  ;) 8-). Same with using a tablet which has no mobile network connection.

background:
During the pairing process the phone needs to connect to a temporary WiFi network coming from the GW1000. Some mobile phones will refuse this WiFi connection because it does not provide Internet service and the pairing process fails. Turning off cellular data forces the mobile phone to use this WiFi connection without Internet.

4. if you are using a Mesh network setup, switch it off during the pairing

Open the WSView app and select "Menu" - "Configure New Devive"
 [ You are not allowed to view attachments ]
select the console by pressing the icon (usually the 2nd row either left or right icon depending on your console)
- then press "Next"
 [ You are not allowed to view attachments ]  
- follow the instructions on the picture shown next, if completed press next.
 [ You are not allowed to view attachments ]  [ You are not allowed to view attachments ]

you will see several messages - find device .... etc.

you will be asked to enter your SSID of your mobile network and the router password;

be careful - these manual entries risk to be easily mistyped - there won't be an error message if your mistype SSID or password.
Passwords tend to be case sensitive. :roll:

once this done the message will say "connected ..." - BUT this doesn't mean that the pairing is already complete.
The pairing is only complete once your get a success message - and usually (not always) the screen closes.

This should in 98% of all cases work.

There are in our experience some other very rarely occurring constellations

In 1.5% of the cases you may be using special characters like %, $, , & etc. in your password, and this can create conflicting situations due to so-called code page issues. If you have such a router password, create a new one only from numbers and letters. Letters can be upper- and lower case. In future firmware versions the entry of potentially problematic special characters will be rejected.

In 0.5% of the cases, there can be a conflict with a neighbor WiFi network whose router is transmitting on the same channel as yours but with a stronger signal than yours. Then you will either have to change the channels in your router, or first try to get smartphone and console very close to the router for the pairing to complete.

In even less % of the cases another IoT "gadget" may have gone rogue in your household (or your neighbor's if you live rather close to each other) and disturb the whole WiFi network - but then you will also have general WiFi issues not only with your console.

addendum:
One more possible (but not console related issue): if you happen to run out of IP addresses from your DHCP budget, the pairing cannot complete.
I know of at least one case where this happened.


other options/situations:

* pairing and configuring under Windows )
see post further down - https://www.wxforum.net/index.php?topic=41575.msg430951#msg430951
(due to attachments limitations we have to open a new post) 


* Regarding firmware updates, WiFi and console firmware updates, see https://www.wxforum.net/index.php?topic=40730.msg426256#msg426256


* the console and the router have paired but the console still doesn't appear in the device list
see post further down - https://www.wxforum.net/index.php?topic=41575.msg430977#msg430977
(due to attachments limitations we have to open a new post)

broadstairs:
May I ask one question - Why does the 5ghz wifi have to be turned off this should never be necessary just to get a device to connect.

Stuart

galfert:

--- Quote from: broadstairs on February 25, 2021, 11:08:34 AM ---May I ask one question - Why does the 5ghz wifi have to be turned off this should never be necessary just to get a device to connect.

Stuart

--- End quote ---

Good question. Here is the answer...

The pairing process requires the GW1000 (or other consoles) to receive the credentials for the local WiFi network. Being that the GW1000 (and other consoles) only have radios that work with 2.4 GHz means that you cannot pass 5 GHz band credentials for pairing. This requires that the mobile device therefore be on the 2.4 GHz in order to pass only those credentials during the pairing process.

Technically speaking you can leave the 5 GHz on if you can ensure that the mobile device is only using the 2.4 GHz band. The way to accomplish this is to ensure that your 2.4 GHz SSID and the 5 GHz SSID are different names. Then you make sure that the mobile device is set to only use the 2.4 GHz SSID (it must also not have the 5 GHz SSID remembered or it may use it). That then guarantees that only the 2.4 GHz SSID credentials are passed during the pairing process. But unfortunately many WiFi networks have the 2.4 GHz and the 5 GHz configured to be the same SSID and they do this so that device can arbitrarily move in and use either 2.4 GHz or 5 GHz depending on signal quality. If your 2.4 GHz SSID and your 5 GHz SSID are different you still need to be sure that the 5 GHz SSID is not saved as a connection possibility or the mobile could be using it instead of the 2.4 GHz.  If your 2.4 GHz and 5 GHz are the same SSID then the pairing process might fail. It is just much simpler to tell users to temporarily turn off the 5 GHz band than to explain all this.

Other smart IoT devices have a much nicer pairing experience because they either support both 2.4 GHz and 5 GHz bands or they use Bluetooth to pass along the WiFi credentials of which then that pairing process asks which 2.4 GHz SSID to pass along. The pairing process of the GW1000 does not ask you which SSID to use..it just uses the one that is currently in use. Adding Bluetooth or adding both 2.4 GHz and 5 GHz to these stations would increase the price point.

Even if you could join your station to the 5 GHz band I would argue that it is not an efficient use of your 5 GHz band. The 5 GHz band should be reserved for devices that really benefit from the increased bandwidth that way there is more of it to go around and the use of wider channels can be employed by the 5 GHz band without needing to downsize to smaller bandwidth channels for the sake of compatibility reasons.

plunet:
I can confirm that some of the resellers instructions (looking at you Mr Waldbeck) do still ship out products and tell you to use the WS Tool app to configure the console unit. Which is really annoying because the tool will see the unit but can't do the configuration. That wasted me at least 20mins at the weekend...

broadstairs:
I've been looking into this some more and if you really need to switch off 5ghz to set the device up it is very sloppy programming in the device itself if it only supports 2.4ghz as it should never see 5ghz. If it does both then I can see some benefit but what happens when the router is rebooted and the device reconnects? Recovery from a power failure could be problematic perhaps!

Stuart

Navigation

[0] Message Index

[#] Next page

Go to full version