If you are using the RFID with the new Wasp Asset app and your RFID tags are reading with several leading 0s and extra 3s inserted in front of other digits (E.g., 000000000000000030303338 instead of 0038), there’s an update needed to your Scan Parsing rule.

On the web page, expand Mobility and click Scan Parsing Configuration. These two lines specifically need to be updated/added, or you can overwrite the full rule with the one below. The changes should match exactly what is given here.

1. The Rule Name needs to be changed:
<Rule Name="some_rule_identifier">

2. You need to add a line for the Repeater Mode after the comment, before the Position line:
<!-- Repeater refers to the character that is repetitive and padded along with

actual data. mode refers whether padding is at the beginning or at the end.-->
<Repeater mode="Prefix">0</Repeater>
<Position>0</Position>

After making those changes, click Save.

On the mobile app, go to Home > Settings and tap Sign Out, then enter your login information again to ensure that the rule update is retrieved by the device, rather than just using the Sync button.

===========

For convenience, here is the full rule with the above changes:

<Rules>
<Rule Name="some_rule_identifier">
<Condition>
<Type>Always</Type>
<Length />
<Position>0</Position>
<Character />
<InputField>AssetTag</InputField>
</Condition>
<Fields NumberofFields="1">
<Field Field_ID="Field 1">
<Action>Parse</Action>
<!-- Repeater refers to the character that is repetitive and padded along with
actual data. mode refers whether padding is at the beginning or at the end.-->
<Repeater mode="Prefix">0</Repeater>
<Position>0</Position>
<Length>64</Length>
<!-- If tag value is in hex, convert it into ASCII
Conversion will be done if this tag is set to 1-->
<Conversion>1</Conversion>
<Prefix />
<Postfix />
<InputField>AssetTag</InputField>
</Field>
</Fields>
</Rule>
</Rules>