Running May 24, 2024 download of windows version of WD on Win 11 pro 22h2 on two machines on same lan. Server is connected to Tempest weather station.
Client is set to stationless with ftp settings for client at default.
I am having two problems:
when the rainfall begins on the tempest, the server station records it properly, but the client records it as 100X greater in the Today section - nothing in last hour, and the monthly and yearly rain totals follow the server as they should.
The solar data from the server is not coming across to the client - neither the Watts nor the UV nor the Lux.
I am using the client to drive pws-wd dashboard - because I didn’t want to experiment on the main server machine - so when the client machine loses its mind with the impossible today rainfall - it sends this over to pwswd - as one would expect. I’d like to fix the problems on the client but don’t know where to begin.
PS - pws-wd is using the WDAPI on and from the Client.
well shutting off the solar switches on the client worked to get the client receiving solar data from the server - but the rain issue persists - whether I have client set up with defaults or to use the clientraw from the server. When using clientraw from the server, however, the lighting count just keeps going up and up on the client.
I am not sure what to make of the fact that the data received box sometimes flashes green but mostly stays grey even when the counter is increasing regularly on the client. The data quality box is always green.
Intuitively – with no logical explanation – I would not expect the client to produce a decent WDAPI output. And WDAPI has nowhere near the same number of fields as clientraw. I run a WD client for convenience: my weather computer is not directly monitored.
What is stopping you “experimenting” with driving pwsWD from the “server” ? What can go wrong?
P.S. Can we have the URL to your pwsWD site?
P.P.S. NorCal Dan is the Tempest man, hope he can comment on the rain.
I am not familiar with the use as a client. But, in general, most issues can be traced to the cron program. I don’t even know if the client mode uses the cron.
The Tempest is a strange animal. Having the WxFlow server in the mix complicates the whole issue. And to make matters worse, WxFlow “massages” the rainfall data using their “near cast” algorithm to “adjust” your rainfall to what they determine is your actual rainfall as compared to other stations near you. The haptic rain sensor is wildly inaccurate and they know it, hence their attempt to “correct” your data. Unfortunately, the cron ignores their corrected data, so the Tempest routinely over/under reads rainfall amounts based on the size of the raindrops.
Best I can suggest is contact Brian to see if any changes are needed to the setup or in the code for the client mode.