So when you say "reporting" do you mean on the console screen or at Ambientweather.net?
To be clear here:
a WS-2000 station consists of three parts:
- the outdoor sensor array [WH65] (which has batteries, but only as backup, usually runs on solar energy)
- the indoor temp/hum/pressure sensor [WH32B](which has batteries)
- the WS-2000 console which doesn't have any batteries
so,
- exchanging batteries at the outdoor array would usually not have any effect on sensor readings
- exchanging batteries on the indoor 3-in-1 sensor could (rarely) have some effect on the sensor readings
- even though the sensors (7-in-1 array, 3-in-1 indoor sensor combo) may but need not to have their own firmware, this is not updated
- the only firmware which is updated is the WiFi firmware for the external weather network communication and the internal console firmware for the console display and sensor processing - WiFi update goes via WSView/awnet app, console via microSD card
Now, what exactly is out of the usual ? the values shown on the console display ? the values posted to a weather network e.g. WU, Ambient ... ? Both ?
Having this information could be helpful for a better assessment of your situation.
In principle, the console can run properly and the weather network posting can be wrong (due to old WiFi firmware). Both the console and weather network data for the same sensors can be wrong due to old WiFi firmware and old console firmware.
In principle you should be able to download the older console firmware from Ambient, put it on a microSD card and start the update process (which would be a downgrade when you provide a user.bin or factory.bin file of an older console firmware version).
If your observed issue is caused by the firmware or not is not forcing - it could be coincidental.