Q: When importing Data Exchange files, we sometimes receive error messages that tell us endpoints have not been activated or an endpoint does not belong to our utility. What do these messages mean and what should we do when we see them?
A: The error message “The endpoint has not been activated” indicates that the endpoint you are trying to provision is not currently in an active or pre-provisioned state, which is required before it can be fully provisioned. In other words, the system is expecting the endpoint to be in a ready-to-use state (that is, it is active or pre-provisioned and communicating successfully with BEACON), but it is currently inactive or has not gone through the necessary initial activation process.
Here is a breakdown of possible causes for this error:
- Endpoint Activation Not Completed – The endpoint may not have been fully activated. ORION Cellular endpoints can be activated when water flow is detected, but the preferred activation method is to use our IR Communication Device (part number 68779-091) and follow the directions outlined in this document.
- Provisioning Sequence Out of Order – Trying to provision before activation will always trigger the error message that the endpoint has not been activated. The system requires the endpoint to first be active and in a pre-provisioned state before provisioning can proceed.
To resolve the issue, do the following:
- Check the endpoint activation status.
- Review any steps required to activate the endpoint before provisioning. Troubleshoot any potential installation or network issues that might be preventing the endpoint from successfully communicating with BEACON.
- Once the endpoint is active and in the pre-provisioned state, you should be able to import a Data Exchange file to provisioned the endpoint without encountering this error.
The error message stating that an endpoint does not belong to the utility means that BEACON did not find the specified endpoint serial number in your inventory.
There are two possible causes for this:
- There is a typo in the Endpoint_SN field of your Data Exchange file.
- A clerical error resulted in the endpoint being assigned to another utility.
To resolve the issue:
- Verify that the serial number printed on the side of the endpoint matches the value entered in the Endpoint_SN field in your Data Exchange file. If it does not match, correct the type and reimport the file.
- If the serial number on the side of the endpoint matches the value entered in the Endpoint_SN field, contact Badger Meter Technical Support for assistance. TIP: If possible, take a picture of the endpoint showing its serial number so that you can share it with Technical Support. This will speed their ability to assist you.
