Troubleshooting Accessory Module Alarms
Accessory Modules upload their data through the Node-S, so they need to be both physically connected and paired on the Dashboard. This article covers the alarms you might see when something isn't right, and how to fix each.
For a Module to work correctly, it must be:
- Physically connected to the Node-S.
- Paired to that same Node-S on the Clarity Dashboard.
If either step is missing, you may see one of these alarms:
Module not responding
The Node can't communicate with the Module.
If a Module is connected to the Node, check the connection on both the Module and the Node — unplug and re-plug both. Listen for the Module-specific sounds for your Module type.
Unpaired module detected
The Node detects a physical connection with a Module, but no Module was paired to it on the Dashboard.
Pair the Module on the Dashboard, following the deployment guide for your Module type (linked below).
Module paired but not detected
The Node was paired with a Module on the Dashboard, but no physical connection is detected.
- If the Module is connected to the Node, check the connection on both the Module and the Node — unplug and re-plug both. Listen for the Module-specific sounds for your Module type.
- If the Module has been disconnected from the Node, unpair the Module to avoid this alarm in future.
Module power error
The Node is having trouble powering the Module.
Verify the Module is paired correctly. See how to unpair a Module if you need to reset the pairing.
Module deployment guides
If these steps don't resolve the issue, or you have questions, email support@clarity.io and we'll get back to you shortly.
What's next
Was this article helpful?
Yes, thanks! / Not really
Still need a hand? Email us at support@clarity.io or create a support ticket, and our team will get back to you.