new WLL does not work

[HansR]

I am helping somebody with CMX/CUtils configuration and he just changed his Davis console for a WLL.
The logfile says sometimes it reads, sometimes it does not.

The logfile attached has debug and datalogging on.

(search for Error processing WLL response in the debug on section).

[mcrossley]

I get the odd current condition request fail, not like that though.
Is there anything other programs talking to the WLL?

[PaulMy]

Like Mark, I get the occasional error, but then pretty well immediately following is ok.
This is about the same for each of my 3 CMX WLL installs that run at the same time.


v3-b3173

Code: Select all

2022-04-21 16:40:08.005 GetWllCurrent: Sending GET current conditions request 1 to WLL: http://192.168.0.100/v1/current_conditions ...
2022-04-21 16:40:08.021 GetWllCurrent: Error processing WLL response
2022-04-21 16:40:08.021 GetWllCurrent: Error: The underlying connection was closed: The connection was closed unexpectedly.
2022-04-21 16:40:09.031 GetWllCurrent: Sending GET current conditions request 2 to WLL: http://192.168.0.100/v1/current_conditions ...
2022-04-21 16:40:09.046 WLL Broadcast: {"did":"001D0A713613","ts":1650573609,"conditions":[{"lsid":358318,"data_structure_type":1,"txid":1,"wind_speed_last":2.00,"wind_dir_last":360,"rain_size":2,"rain_rate_last":0,"rain_15_min":0,"rain_60_min":0,"rain_24_hr":43,"rain_storm":43,"rain_storm_start_at":1650531181,"rainfall_daily":43,"rainfall_monthly":307,"rainfall_year":928,"wind_speed_hi_last_10_min":12.00,"wind_dir_at_hi_speed_last_10_min":360}]}

Test 4 MXdiags

Code: Select all

2022-04-21 15:50:30.121 GetWllCurrent: Sending GET current conditions request 1 to WLL: http://192.168.0.100/v1/current_conditions ...
2022-04-21 15:50:30.162 GetWllCurrent: Error - The WLL rejected our request
2022-04-21 15:50:31.152 GetWllCurrent: Sending GET current conditions request 2 to WLL: http://192.168.0.100/v1/current_conditions ...
2022-04-21 15:50:32.101 GetWllCurrent: response - {"data":{"did":"001D0A713613","ts":1650570631,"conditions":[{"lsid":358318,"data_structure_type":1,"txid":1,"temp": 62.7,"hum":61.5,"dew_point": 49.3,"wet_bulb": 53.8,"heat_index": 61.8,"wind_chill": 62.7,"thw_index": 61.8,"thsw_index": 72.6,"wind_speed_last":2.00,"wind_dir_last":360,"wind_speed_avg_last_1_min":2.56,"wind_dir_scalar_avg_last_1_min":360,"wind_speed_avg_last_2_min":3.31,"wind_dir_scalar_avg_last_2_min":360,"wind_speed_hi_last_2_min":9.00,"wind_dir_at_hi_speed_last_2_min":360,"wind_speed_avg_last_10_min":5.93,"wind_dir_scalar_avg_last_10_min":360,"wind_speed_hi_last_10_min":16.00,"wind_dir_at_hi_speed_last_10_min":360,"rain_size":2,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":43,"rain_storm":43,"rain_storm_start_at":1650531181,"solar_rad":710,"uv_index":3.6,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":43,"rainfall_monthly":307,"rainfall_year":928,"rain_storm_last":88,"rain_storm_last_start_at":1650311161,"rain_storm_last_end_at":1650492061},{"lsid":358316,"data_structure_type":4,"temp_in": 81.5,"hum_in":27.8,"dew_point_in": 45.1,"heat_index_in": 79.3},{"lsid":358315,"data_structure_type":3,"bar_sea_level":30.078,"bar_trend": 0.076,"bar_absolute":29.200}]},"error":null}

Test 3 MXdiags

Code: Select all

2022-04-21 09:58:23.562 GetWllCurrent: Sending GET current conditions request 1 to WLL: http://192.168.0.100/v1/current_conditions ...
2022-04-21 09:58:23.577 GetWllCurrent: Error processing WLL response
2022-04-21 09:58:23.577 GetWllCurrent: Error: The underlying connection was closed: The connection was closed unexpectedly.
2022-04-21 09:58:24.468 WLL Broadcast: {"did":"001D0A713613","ts":1650549503,"conditions":[{"lsid":358318,"data_structure_type":1,"txid":1,"wind_speed_last":4.00,"wind_dir_last":360,"rain_size":2,"rain_rate_last":1,"rain_15_min":1,"rain_60_min":2,"rain_24_hr":43,"rain_storm":43,"rain_storm_start_at":1650531181,"rainfall_daily":43,"rainfall_monthly":307,"rainfall_year":928,"wind_speed_hi_last_10_min":13.00,"wind_dir_at_hi_speed_last_10_min":360}]}

Hans' Post MXdiags

Code: Select all

2022-04-21 18:16:04.503 GetWllCurrent: Error processing WLL response
2022-04-21 18:16:04.503 GetWllCurrent: Error: The server returned an invalid or unrecognized response.
2022-04-21 18:16:51.293 AirLinkHealth: Get WL.com Historic Data
2022-04-21 18:16:51.735 AirLinkHealth: WeatherLink API: No data was returned. Check your Device Id.

This shows dozens and dozens of that first error, and occasionally the AirLink message. Then only the occasional error and then quickly is ok.

Code: Select all

2022-04-21 19:28:53.767 GetWllCurrent: Error processing WLL response
2022-04-21 19:28:53.768 GetWllCurrent: Error: The server returned an invalid or unrecognized response.
2022-04-21 19:28:54.184 WLL Broadcast: {"did":"001D0A715A2F","ts":1650562133,"conditions":[{"lsid":514298,"data_structure_type":1,"txid":4,"wind_speed_last":3.00,"wind_dir_last":92,"rain_size":2,"rain_rate_last":0,"rain_15_min":0,"rain_60_min":0,"rain_24_hr":0,"rain_storm":null,"rain_storm_start_at":null,"rainfall_daily":0,"rainfall_monthly":0,"rainfall_year":0,"wind_speed_hi_last_10_min":10.00,"wind_dir_at_hi_speed_last_10_min":63}]}
2022-04-21 19:28:54.768 GetWllCurrent: Sending GET current conditions request 2 to WLL: http://192.168.178.90/v1/current_conditions ...
2022-04-21 19:28:55.838 GetWllCurrent: response - {"data":{"did":"001D0A715A2F","ts":1650562134,"conditions":[{"lsid":514298,"data_structure_type":1,"txid":4,"temp": 60.1,"hum":39.4,"dew_point": 35.3,"wet_bulb": 44.1,"heat_index": 57.1,"wind_chill": 60.1,"thw_index": 57.1,"thsw_index": 56.0,"wind_speed_last":3.00,"wind_dir_last":66,"wind_speed_avg_last_1_min":4.81,"wind_dir_scalar_avg_last_1_min":74,"wind_speed_avg_last_2_min":4.62,"wind_dir_scalar_avg_last_2_min":71,"wind_speed_hi_last_2_min":10.00,"wind_dir_at_hi_speed_last_2_min":73,"wind_speed_avg_last_10_min":4.62,"wind_dir_scalar_avg_last_10_min":76,"wind_speed_hi_last_10_min":10.00,"wind_dir_at_hi_speed_last_10_min":63,"rain_size":2,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":0,"rain_storm":null,"rain_storm_start_at":null,"solar_rad":67,"uv_index":0.0,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":0,"rainfall_year":0,"rain_storm_last":null,"rain_storm_last_start_at":null,"rain_storm_last_end_at":null},{"lsid":514299,"data_structure_type":2,"txid":5,"temp_1": 53.6,"temp_2": 51.1,"temp_3": 49.3,"temp_4": 49.2,"moist_soil_1":32.1,"moist_soil_2":26.9,"moist_soil_3":18.6,"moist_soil_4":10.4,"wet_leaf_1":0.1,"wet_leaf_2":null,"rx_state":0,"trans_battery_flag":0},{"lsid":514296,"data_structure_type":4,"temp_in": 71.5,"hum_in":44.1,"dew_point_in": 48.5,"heat_index_in": 69.8},{"lsid":514295,"data_structure_type":3,"bar_sea_level":29.881,"bar_trend":-0.010,"bar_absolute":29.798}]},"error":null}

One though is the WLL to internet connection. Has he checked that with the Weatherlink App
Does he have a Pro subscription, and if so is the Weatherlink.com [Data] history all there? And is the Health Data ok?


p.s.

The logfile attached has debug and datalogging on.

Code: Select all

2022-04-21 16:39:39.073 Debug logging :disabled
2022-04-21 16:39:39.073 Data logging  :disabled
2022-04-21 16:39:39.073 FTP logging   :disabled
2022-04-21 16:39:39.073 Email logging :disabled
2022-04-21 16:39:39.073 Spike logging :enabled

Enjoy,
Paul

[HansR]

I get the odd current condition request fail, not like that though.
Is there anything other programs talking to the WLL?

No, just CMX

@Paul: about the debug/data logging. Yes it was off at the start of the logfile and switched on between 19 and 20 hours.

And my conclusion is that apparently we have to live with it and that these errors are normal. I will have a look at it again, we did already check the network. Note that the radio of the Davis is shared with a neighbour who also receives. The neighbour on Tx 1, this device on Tx 4. But he had some problems with the original station/logger as well. Not fully sure on how they have it all setup (I have not seen it, it is running like this already for years... Could age of the Davis be an issue?)

Distance maybe?

Ok definitely outside CMX afaics.
We'll debug further, thanks. If anything useful found I'll be back.

@Paul: no subscription yet, this is brand new out of the box connected at 16h40 .
First hand first experience shock

[HansR]

btw: distance between the station and the WLL is 50 meters

[mcrossley]

Sounds more like the local network connectivity (what is the WLL WiFi RSSI figure like?), or the WLL itself. Losing sensor contact normally does affect the local API, it just reports the sensor status in the messages.

[HansR]

what is the WLL WiFi RSSI figure like?

We did already check general network status which was OK.

Looking at the RSSI it was 60 then the WLL was moved / relocated and it changed to 78 (see screenshots).
The problem seems to have largely disappeared by now.
(tbh: I received these screenshots but I do not understand the minus sign (-) before the Rssi values. To me it seems that after replacement the signal was worse but apparently it is not. Anyway, it seems OK now so I do not question )

Losing sensor contact normally does affect the local API, it just reports the sensor status in the messages.

Are these sensor statuses available to the user (like the normal station statistics which do not seem to be available for the WLL or are they?)

220422 Gerrits WLL RSSI 1.png

220422 Gerrits WLL RSSI 2.png

[mcrossley]

Some of the stats are only available from wl.com via the API. Likewise the sensor status is on the real-time data from the WLL, values just go to null if not available.

[HansR]

OK, so not available through CMX like they are for the regular DAVIS stats.

[ConligWX]

OK, so not available through CMX like they are for the regular DAVIS stats.

not via the WLL. if you have a spare Console you cold get some stats from it too.

I know anything below -90 Davis Talk Rssi or Wifi Rssi, is considered weak and you'll see by those images some are near that value and they have worse signal reception, though anything about -75 and below will start to give bad reception on the Davis stuff.

[mcrossley]

OK, so not available through CMX like they are for the regular DAVIS stats.

Some are, though a console diags screen gives you more data. What is available from CMX is...

tx[n] missed/bad packets
tx[n] packets with CRC errors
tx[n] Good packets
tx[n] - WLL resynch's
tx[n] streak of good packets
tx[n] RSSI
WLL WiFi RSSI

[HansR]

Ah... webtags! I should have consulted the wiki
Thanks. Will add info to Cutils, should have done long ago.