Troubleshooting
Common issues and solutions for ArgusAI.
Installation Issues
Python Version Error
Error: Python 3.11 or higher is required
Solution:
# Check Python version
python3 --version
# Install Python 3.11+ via pyenv
pyenv install 3.11.0
pyenv global 3.11.0
Node.js Version Error
Error: Node.js 18 or higher is required
Solution:
# Check Node version
node --version
# Install via nvm
nvm install 20
nvm use 20
Database Migration Failed
Error: alembic.util.exc.CommandError: Can't locate revision
Solution:
cd backend
alembic stamp head
alembic upgrade head
Camera Issues
RTSP Connection Failed
Symptoms: Camera shows offline, no frames captured
Checklist:
- Verify RTSP URL format:
rtsp://user:pass@ip:port/path - Test with VLC:
vlc rtsp://... - Check firewall allows RTSP port (usually 554)
- Verify camera credentials
UniFi Protect Connection Failed
Error: Unable to connect to Protect controller
Solutions:
- Use IP address instead of hostname
- Verify local user credentials (not Ubiquiti SSO)
- Check port 443 is accessible
- Disable SSL verification for self-signed certs
USB Camera Not Found
Error: No video devices found
Solutions:
# List available devices
ls -la /dev/video*
# Check permissions
sudo usermod -a -G video $USER
# Logout and login again
AI Provider Issues
API Key Invalid
Error: 401 Unauthorized or Invalid API key
Solutions:
- Verify API key is correct (no extra spaces)
- Check key has required permissions
- Ensure key is not expired
- Try regenerating the API key
Rate Limited
Error: 429 Too Many Requests
Solutions:
- Reduce frame count per analysis
- Enable cost caps in settings
- Use fallback providers
- Wait and retry
Timeout Errors
Error: Request timeout or AI analysis failed
Solutions:
- Check network connectivity
- Reduce image size/quality
- Try a different provider
- Increase timeout in settings
Push Notification Issues
Notifications Not Working
Checklist:
- HTTPS is enabled (required for web push)
- Browser notifications are allowed
- Service worker is registered
- Test notification works
HTTPS Not Working
Error: SSL certificate error
Generate self-signed certificate:
openssl req -x509 -nodes -days 365 -newkey rsa:2048 \
-keyout data/certs/key.pem \
-out data/certs/cert.pem \
-subj "/CN=localhost"
Configure environment:
SSL_ENABLED=true
SSL_CERT_FILE=data/certs/cert.pem
SSL_KEY_FILE=data/certs/key.pem
Push Only Works Once
Issue: First notification works, subsequent ones don't
Solutions:
- Check service worker console for errors
- Verify push subscription is persisted
- Clear browser cache and re-subscribe
- Check backend push service logs
HomeKit Issues
Bridge Not Discoverable
Solutions:
- Ensure mDNS/Bonjour is working
- Check no firewall blocking discovery
- Restart HomeKit bridge service
- Reset pairing and try again
Pairing Failed
Error: Accessory not responding
Solutions:
- Reset accessory in ArgusAI settings
- Remove old pairing from Home app
- Restart both ArgusAI and Home app
- Check network connectivity
MQTT Issues
Connection Refused
Error: MQTT connection refused
Solutions:
- Verify MQTT broker is running
- Check host and port are correct
- Verify credentials if auth is enabled
- Check firewall allows MQTT port
Devices Not Appearing in Home Assistant
Solutions:
- Verify MQTT discovery is enabled in HA
- Check topic prefix matches HA configuration
- Restart Home Assistant
- Check MQTT broker logs
Performance Issues
High CPU Usage
Solutions:
- Reduce number of active cameras
- Lower frame rate for analysis
- Disable motion detection on quiet cameras
- Increase event processing interval
High Memory Usage
Solutions:
- Reduce frame buffer size
- Enable aggressive cleanup
- Reduce concurrent AI requests
- Restart services periodically
Slow Event Processing
Solutions:
- Use faster AI provider
- Reduce frame count
- Enable multi-frame instead of video mode
- Check network latency to AI providers
Getting Help
If these solutions don't resolve your issue:
- Check GitHub Issues
- Search for similar problems
- Create a new issue with:
- ArgusAI version
- Operating system
- Relevant logs
- Steps to reproduce