Author Topic: WH31B not connecting to GW1000  (Read 1051 times)

0 Members and 1 Guest are viewing this topic.

Offline zakatak

  • Member
  • *
  • Posts: 5
WH31B not connecting to GW1000
« on: January 11, 2021, 05:43:10 PM »
Hi, I'm new here.

For Christmas my wife bought me a GW1000 + WH32. I like them so much that I bought 3 of the WH31B sensors from Amazon to use around the house. I cannot get one of the WH31B sensors to connect to the GW1000 regardless of channel. I have one sensor on CH1 and another on CH2, but it doesn't seem to matter if I set the third to CH3, 4, 5, 6, 7, or 8 it never seems to connect. I will probably return it, but before I do, is there anything I should try?

Thanks!

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WH31B not connecting to GW1000
« Reply #1 on: January 11, 2021, 05:54:25 PM »
Double check that you haven't inadvertently locked all the available channels to an old ID. In the WS View app click on re-register for any channel not being used or not yet showing data.
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline zakatak

  • Member
  • *
  • Posts: 5
Re: WH31B not connecting to GW1000
« Reply #2 on: January 11, 2021, 06:02:00 PM »
I click "Re-register" and it shows a window with a checkbox and "Success" underneath. On the left under the CH3 ID: I see "Learning..." and that's all.

Can it take hours to successfully connect?

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WH31B not connecting to GW1000
« Reply #3 on: January 11, 2021, 07:45:11 PM »
The WH31 sensors transmit every 60 seconds. It should only take that long for the GW1000 to see the new WH31 after you click re-register. If it still isn't working I would give it one last go by pulling the batteries out of the WH31, then setting the channel dip switches, then reinserting the batteries. You'll know the WH31 is working when you see the LCD come to life. If this still doesn't work then you probably have a defective WH31.
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline zakatak

  • Member
  • *
  • Posts: 5
Re: WH31B not connecting to GW1000
« Reply #4 on: January 11, 2021, 08:18:49 PM »
Thank you very much! Looks like I got a dud.

Offline wardie

  • Senior Contributor
  • ****
  • Posts: 212
Re: WH31B not connecting to GW1000
« Reply #5 on: January 12, 2021, 02:55:24 AM »
Maybe worth just double checking it isn’t anther WH32B (not multi channel) by mistake instead of a WH31B? The difference between these confused me at first. Would also show pressure if so.
Froggit HP1000SE Pro-C console (HP2551-C)
Froggit HP1000SE Pro ultrasonic multi sensor with Ecowitt EC0002 heater (WS80)
Ecowitt Anemometer 5-in-1 array (WS68)
Froggit DP80 rain gauge (WH40) with spikes
Froggit indoor temp/humidity/pressure (WH32B)
Froggit DP50 Internal temp/humidity x2 (WH31)
Ecowitt Outdoor temp/humidity & RS-00001 shield (WH32)
Froggit DP200 PM2.5 outdoor (WH41)
Ecowitt indoor CO2 PM2.5 PM10 (WH45)
Froggit DP100 soil moisture (WH51)
Froggit DP60 Lightning detector (WH57)
Froggit DP1500 server dongle (GW1000A) x2
Raspberry Pi 4 / WeeWx-GW1000 API interface
WU: IKNEBW2

Offline zakatak

  • Member
  • *
  • Posts: 5
Re: WH31B not connecting to GW1000
« Reply #6 on: January 12, 2021, 08:12:06 AM »
Thanks!

I have dip switches for changing the channel. Whichever channel I configure via the dip switches reflects on the LCD. I think that indicates this is a WH31B rather than a WH32B, right?

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WH31B not connecting to GW1000
« Reply #7 on: January 12, 2021, 08:29:00 AM »
Yes. But it probably isn't a WH31B, as Ambient has stopped selling those and now they are all WH31E. The WH31B and WH31E are the same thing except for the WH31E has an extra function which is an RCC. But that RCC does nothing for your station. The RCC is only used for the WS-3000 and perhaps some other smaller displays that don't connect to the Internet for time synchronization.
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline zakatak

  • Member
  • *
  • Posts: 5
Re: WH31B not connecting to GW1000
« Reply #8 on: January 12, 2021, 09:08:38 AM »
Good to know! I bought mine from Amazon, I wonder if they have some older stock...

I have started the return process after leaving the sensor out all night and it not connecting. Here's hoping the next one works like the other 2 did.

Offline Jai Soone

  • Senior Member
  • **
  • Posts: 61
Re: WH31B not connecting to GW1000
« Reply #9 on: January 15, 2021, 06:11:04 PM »
Note that the WH31E seems to hang you out to dry if it can't pick up the RCC signal. From the WS-3000 manual:

5.1 Radio Controlled Clock (RCC)
After the remote sensor is powered up, the sensor will transmit weather data for 30 seconds, and then the  sensor will  begin  radio controlled  clock  (RCC) reception. During  the RCC  time  reception  period (maximum 5 minutes), no weather data will be transmitted to avoid interference. If  the  signal  reception is  not  successful within  3 minute,  the  signal  search will  be  cancelled  and  will automatically resume  every  two  hours  until  the  signal  is  successfully  captured.  The  regular  RF link will resume  once  RCC  reception  routine  is  finished.  In  some  locations,  RCC  reception may  take  a couple of days to receive the signal. Once the radio controlled time is received, the RCC reception icon will turn on next to the date and time field.

Offline wardie

  • Senior Contributor
  • ****
  • Posts: 212
Re: WH31B not connecting to GW1000
« Reply #10 on: January 15, 2021, 06:17:22 PM »
Just fr my understanding of this, why does a sensor have an RCC function? Surely that’s a function of a console not a sensor. Curious.
Froggit HP1000SE Pro-C console (HP2551-C)
Froggit HP1000SE Pro ultrasonic multi sensor with Ecowitt EC0002 heater (WS80)
Ecowitt Anemometer 5-in-1 array (WS68)
Froggit DP80 rain gauge (WH40) with spikes
Froggit indoor temp/humidity/pressure (WH32B)
Froggit DP50 Internal temp/humidity x2 (WH31)
Ecowitt Outdoor temp/humidity & RS-00001 shield (WH32)
Froggit DP200 PM2.5 outdoor (WH41)
Ecowitt indoor CO2 PM2.5 PM10 (WH45)
Froggit DP100 soil moisture (WH51)
Froggit DP60 Lightning detector (WH57)
Froggit DP1500 server dongle (GW1000A) x2
Raspberry Pi 4 / WeeWx-GW1000 API interface
WU: IKNEBW2

Offline galfert

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 6822
Re: WH31B not connecting to GW1000
« Reply #11 on: January 15, 2021, 09:24:37 PM »
Jai Soone, that is an incredible find! Good on you for reading the manual. So many times we ignore the manual for what seems like familiar equipment and how to operate it. But now this! Surely this indicates that Ambient has not made a good decision by deciding to only supply the WH31E instead of the WH31B. The WH31E for our stations is most definitely less superior.

For anyone thinking that receiving an RCC should be no big deal I assure you it is nothing but a big deal. I have a few RCC clocks and they don't always receive the RCC signal and this is most troublesome and noticeable when time changes, or every time the batteries need replacing and then you can't get a signal. The typical recommendation to get an RCC signal is to put the device close to a window and to wait for night time when radio signals can better bounce off the ionosphere and reach further distances. Even then there is no guarantee. I've many times given up on depending on WWVB for RCC signals.

Just fr my understanding of this, why does a sensor have an RCC function? Surely that’s a function of a console not a sensor. Curious.
I mentioned it a few posts back. Because the RCC feature was intended for a different model console than our typical weather station setups. It serves no purpose of the WS-2000 / WS-5000 / WS-2902C. Most certainly the decision to only sell the WH31E is to simplify inventory.
« Last Edit: January 15, 2021, 09:27:13 PM by galfert »
Ecowitt GW1000 | Meteobridge on Raspberry Pi
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline wardie

  • Senior Contributor
  • ****
  • Posts: 212
Re: WH31B not connecting to GW1000
« Reply #12 on: January 16, 2021, 03:57:49 AM »
OK so I get that the RCC functionality it only for WH-3000 but clearly the WH31E has different temp/humidity functionality because it gets interrupted by the RCC cycles. I also had a look at the WH-3000 manual on Ambient website and it doesn’t go into detail about the WH31 model variants. The bit I can’t get my head around is why you would now only sell WH31E with any WH-3000 system (e.g. -X5 -X8) why would you want all the sensors to be all trying to sync time via RCC and all have (small) reporting gaps? And then does the console get bombarded by RCC sync’s or only listen to, say CH1? Surely just one would do, with the others ‘normal’ WH31. Which is than a better solution for other consoles too. As said, does seem an odd decision by Ambient for marginal inventory efficiency, if that is the reason.
Froggit HP1000SE Pro-C console (HP2551-C)
Froggit HP1000SE Pro ultrasonic multi sensor with Ecowitt EC0002 heater (WS80)
Ecowitt Anemometer 5-in-1 array (WS68)
Froggit DP80 rain gauge (WH40) with spikes
Froggit indoor temp/humidity/pressure (WH32B)
Froggit DP50 Internal temp/humidity x2 (WH31)
Ecowitt Outdoor temp/humidity & RS-00001 shield (WH32)
Froggit DP200 PM2.5 outdoor (WH41)
Ecowitt indoor CO2 PM2.5 PM10 (WH45)
Froggit DP100 soil moisture (WH51)
Froggit DP60 Lightning detector (WH57)
Froggit DP1500 server dongle (GW1000A) x2
Raspberry Pi 4 / WeeWx-GW1000 API interface
WU: IKNEBW2

 

anything