Skip to main content

Rewards Troubleshooting

A guide to interpreting mobile app error messages, understanding their meanings, and taking appropriate actions to resolve them.

No wallet

It seems that you haven't connected a wallet to your account yet. Please note that in order to receive rewards, you must connect a wallet address. Here's what you need to do:

  1. Learn how to add or edit a wallet address.
  2. Then, follow the instructions for joining Arbitrum Sepolia and see your $WXM tokens.

Once you've completed the above steps, you'll be all set to claim your rewards. Please wait until the Reward Mechanism (RM) completes. This usually takes until the following day and see "How to Claim Rewards" for further guidance.


No Station Data

It seems that your station did not transmit any data at all, which may indicate that it was either offline or not connected to the network.

Here's what you need to do:

For the M5 (WG1000 - WiFi gateway)

M5 icons explanation
Red=Problem, Green= Good

  1. RF connection with the station.
  2. Connection to WeatherXM Network.
  3. GPS receiver.
  4. WiFi connection.
  1. Check if the station's battery level is low through mobile app settings. If the battery is low, the connection between your station and the M5 gateway will be unstable resulting in data loss.
  1. Follow the Troubleshooting guide regarding No WiFi connection.
  2. Check that your station connection (RF) to the gateway is stable by following the guide here.
  3. Also read through the guide to add the included external antenna here.

For the WS-2000 (Helium version)

  1. Check if the station's battery level is low through mobile app settings.
  2. Check for Helium coverage in your area.

Sensor Problems

If you got this error, it means our data evaluation services detected that the received weather packets, did not meet our quality standards. To ensure the accuracy of the information sent by our weather stations, we evaluate all data packets using our Quality of Data (QoD) algorithm. For more information about this algorithm, please refer to this here.

Below are some of the possible errors and the appropriate actions you can take to resolve the issues:

Out of Bounds Data

It's possible that a sensor sends a completely irrational value, which implies to a faulty sensor. If this error persists for multiple days, it is recommended to perform a complete power cycle.

Power cycle procedure:
  1. Remove batteries.
  2. Cover the solar panel so the station isn't powered by the panel while the batteries are out.
  3. Press the reset button a few times to drain all stored power.
  4. Wait a few minutes.
  5. Put batteries back in place and wait for the station to boot up.

If the above doesn't work, you should contact our support team for sensor replacement.

Spikes on Data

One or more of your sensors are exhibiting irrational spikes. You should first check your station if it is optimally deployed and then you should contact support. Take a look at our Deployment Examples and Best Practices to ensure that your station is deployed correctly.

Constant Values

One or more of your sensors report constant values which implies a bad installation, or less often, a problematic sensor. If your station is optimally installed and the constant value errors persist for a few days, you should perform a power cycle and if you continue to receive it, contact support.

Take a look at our Deployment Examples and Best Practices to ensure that your station is deployed correctly.

Power cycle procedure:
  1. Remove batteries.
  2. Cover the solar panel so the station isn't powered by the panel while the batteries are out.
  3. Press the reset button a few times to drain all stored power.
  4. Wait a few minutes.
  5. Put batteries back in place and wait for the station to boot up.

If the above doesn't work, you should contact our support team for sensor replacement.

Frozen Sensor

You should remove excess snow or ice from the weather station, and make sure wind cups and wind vanes rotate freely.

tip

If you encounter any errors, it is recommended that you observe it for a few days before reaching out to our support team. In case you still receive the error after a couple of days, please do not hesitate to contact our support team for further guidance.


Weather Data Gaps

Some data gaps were detected during our data quality checks. Perhaps the indoor or outdoor units are not properly connected to the network, or to each other.

Here's what you need to do:

For the M5 (WG1000 - WiFi gateway)

M5 icons explanation
Red=Problem, Green= Good

  1. RF connection with the station.
  2. Connection to WeatherXM Network.
  3. GPS receiver.
  4. WiFi connection.
  1. Check if the station's battery level is low through mobile app settings. If the battery is low, the connection between your station and the M5 gateway will be unstable, resulting in data loss.
  1. Follow the Troubleshooting guide regarding No WiFi connection.
  2. Check that your station connection (RF) to the gateway is stable by following the guide here.
  3. Also read through the guide to add the included external antenna here.

For the WS-2000 (Helium version)

  1. Check if the station's battery level is low through mobile app settings.
  2. Check for Helium coverage in your area.

Bad Station Deployment

It appears that your weather station could benefit from some improvements in terms of its deployment. The Quality of Data (QoD) algorithm evaluates all data packet received by a weather station every day, so a proper installation becomes mandatory to receive the maximum amount of rewards. We recommend that you take a look at our Deployment Examples and Best Practices for inspiration on how and where to install your station.


No location Data

Your weather station was suspended from rewards because it did not report GPS data. Please check the troubleshooting guides for your station below, before contacting our support team.support team.

For the M5 (WG1000 - WiFi gateway)

  1. No location (GPS) data (arrow icon is red)
  2. Place the M5 near a window (for better GPS signal)

For the WS-2000 (Helium version)

  1. No location (GPS) data
  2. Installation instructions

Location Not Verified

It appears that the location of your weather station is different from the one you had originally set while claiming it. Please verify your location through the mobile app.

In detail, the Proof of Location (PoL) mechanism flagged your weather station because the location reported by its GPS receiver(s) is different than the location you declared during the setup and claiming of the station.

This could happen because either you have moved your station from its initial installation site, or you had declared a wrong location during the onboarding process of the station on your mobile app.

As a result, your station will not be eligible for reward distribution until it is moved back to the declared location or the location is updated by using the "relocate station" function on your mobile app.

tip

When discussing the weather, we always mention a specific location, either directly or indirectly. Therefore, the data provided by weather stations in the WeatherXM Network is meaningless unless we know the location of each station at all times. It is crucial for the stability of the Network to have weather stations that can report their current location and remain stationary.

note

During the beta phase and while the project is still on a testnet, the Proof of Location (PoL) mechanism penalty imposed to devices that went through a relocation is reduced to 2 days for testing purposes, however this may change once the project moves to mainnet.


User Relocation Penalty

Our Proof of Location (PoL) mechanism reported a relocation event. It seems like you used the relocation feature and you edited the location of your weather station through the app. Please wait 7 days and your weather station will start earning rewards again.

WeatherXM places great importance on station continuity, and discourage relocations therefore It is important for the Network that a station remains at the same location throughout its lifetime.

note

During the beta phase and while the project is still on a testnet, the Proof of Location (PoL) mechanism penalty imposed to devices that went through a relocation is reduced to 2 days for testing purposes, however this may change once the project moves to mainnet.