Debugging & Troubleshooting
A really common problem, inherent in the way I've designed this platform is things can get out of sync.
for Example: You create a schema, then attach a rule to it, then delete the schema. Your action will now never fire because there's no schema.
The health check screen is designed to find these issues automatically so you can fix them!
Debugging & Troubleshooting
This page is under construction! I'm working on it :)
When things aren't working, Inventronix Connect gives you tools to find out why.
Health Check
The Health button in your project runs diagnostics across your entire setup.
What It Checks
- Schemas - Are there any schemas? Are any deprecated?
- Schema Fields - Do all fields have valid types and validators?
- Dashboards - Do dashboard charts reference valid schemas and fields?
- Rules - Are rules referencing valid schemas, fields, and actions?
- Actions - Do device commands reference valid schemas?
- Invalid Payloads - Have any recent payloads failed validation?
Severity Levels
- Error (red) - Something is broken and needs fixing
- Warning (yellow) - Potential issue, might be intentional
Example Findings
1 | |
Healthy Project
If everything is configured correctly, you'll see a green checkmark with no findings.
Live Debug Stream
The Live Debug button opens a real-time log of everything happening in your project.
What You'll See
Payload ingestion:
1 | |
Rule evaluation:
1 | |
Action execution:
1 | |
Webhook calls:
1 | |
Email notifications:
1 | |
Errors and warnings:
1 | |
Log Levels
- info (blue) - Normal operation
- warn (yellow) - Potential issue
- error (red) - Something failed
Tips
- Leave the debug stream open while testing
- Clear the log to focus on new events
- Auto-scroll keeps you at the latest logs
- Logs are not persisted - they only appear while connected
Invalid Payloads
When a payload fails schema validation, it's stored as an "invalid payload" for debugging.
Where to Find Them
Invalid payloads appear in:
- Health check - Warning if recent invalid payloads exist
- Live Debug - Real-time validation failure messages
- Payloads Explorer - Validation Failures tab
Common Causes
Wrong field type:
1 | |
Missing required field:
1 | |
Failed validation:
1 | |
Unknown schema: X-Schema-ID header doesn't match any schema, or payload doesn't match any active schema's structure.
Debugging Steps
- Check the Live Debug stream for the validation error
- Compare your payload structure to the schema definition
- Verify field types match (number vs string vs boolean)
- Check if required fields are present
- Ensure validators pass (min/max values, allowed values)
Common Issues
"No rules triggered"
Check:
- Is the rule enabled?
- Are all conditions being met? (check Live Debug)
- Is the action on cooldown?
- Does the schema match what your device sends?
"Device not receiving commands"
Check:
- Is the device calling `sendPayload()` regularly?
- Is the action's schema correct for this device?
- Is the command name spelled correctly?
- Check Live Debug for "queued" and "delivered" messages
"Webhook failing"
Check:
- Is the URL correct and accessible?
- Are required headers included?
- Is the body valid JSON (if required)?
- Check Live Debug for HTTP status codes
"Dashboard not updating"
Check:
- Is the schema active (not draft or deprecated)?
- Do the chart sources match your payload fields?
- Is your device sending data?
- Check browser console for WebSocket errors
"Validation keeps failing"
Check:
- Field names are case-sensitive
- Numbers must be numbers (not strings like "23")
- Booleans must be `true`/`false` (not `1`/`0` or `"true"`)
- Check Live Debug for specific validation errors
Getting Help
If you're stuck:
- Check Live Debug - Most issues are visible in real-time
- Run Health Check - Catches configuration problems
- Review the schema - Most validation issues start here
- Check device serial output - The Arduino library logs errors
Next Steps
- Schemas - Review field types and validators
- Rules and Actions - Understand how rules evaluate
- Sending Data - Verify your payload format