-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Pentafive edited this page Jan 4, 2026
·
1 revision
Symptoms: Integration added but no sensors show up in Home Assistant.
Solutions:
- Check callsign format - Must be valid amateur radio callsign (e.g., W1ABC, VK2XYZ/P)
- Wait for activity - If your station isn't currently active, no spots will appear
- Restart Home Assistant - Required after initial installation
- Check logs - Look for errors in Home Assistant logs
# Check logs for PSKReporter errors
logger:
default: info
logs:
custom_components.pskr: debugSymptoms: binary_sensor.feed_health is OFF, sensors show stale data.
Possible Causes:
| Cause | Solution |
|---|---|
| No station activity | Normal if you're not transmitting/receiving |
| Network issue | Check internet connectivity |
| PSKReporter down | Check status.pskreporter.info |
| Firewall blocking | Allow outbound WSS to port 1886 |
Diagnostic Steps:
- Check
sensor.*_message_rate- should be > 0 msg/min when active - Check
sensor.*_connection_status- should show "Connected" - Check
sensor.*_feed_latency- time since last message
Symptoms: MQTT connection failing to PSKReporter.
Solutions:
-
Check network connectivity
# Test from HA host curl -v https://mqtt.pskreporter.info:1886 -
Verify firewall rules - Allow outbound TCP 1886 (WebSocket TLS)
-
Check for IP blocks - PSKReporter may rate-limit aggressive connections
-
Review reconnect count - If high, check for network instability
Symptoms: Global monitor shows 0 spots, but personal monitors work.
Solutions:
- Check sample rate - Default 1:10 means only every 10th message processed
- Wait for accumulation - Global stats reset every 15 minutes
-
Verify topic subscription - Check logs for
pskr/filter/v2/+/FT8/+/+/#
Symptoms: Home Assistant memory increasing over time.
Solutions:
- Enable Count-Only Mode - Options > Count-Only Mode = ON
- Increase Sample Rate - Higher sample rate = less processing
- Reduce stats window - Fewer spots stored (default: 15 min)
- Fully restart Home Assistant (not just reload)
- Clear browser cache
- Check HACS download completed successfully
- Verify URL:
https://github.com/pentafive/pskr-ha-bridge - Select "Integration" as category
- Check GitHub is accessible from your network
| Error | Cause | Solution |
|---|---|---|
| brands | Brand not in HA brands repo | Wait for PR merge or use without |
| topics | Missing repo topics | Already fixed in v2.0.0 |
# Check logs
docker logs pskr-ha-bridge
# Common causes:
# - Missing MY_CALLSIGN
# - Invalid MQTT broker address
# - Network connectivity issues- Enable discovery - Settings > Devices & Services > MQTT > Configure
- Check broker - Container must reach HA's MQTT broker
-
Verify topics - Check broker for
homeassistant/sensor/pskr_*
# Test MQTT from container
docker exec pskr-ha-bridge mosquitto_pub -h $HA_MQTT_BROKER -t test -m test
# Common fixes:
# - Verify HA_MQTT_BROKER address
# - Check credentials in HA_MQTT_USER/HA_MQTT_PASS
# - Ensure broker allows external connectionsHACS Integration:
# configuration.yaml
logger:
default: info
logs:
custom_components.pskr: debug
custom_components.pskr.coordinator: debugDocker:
# .env
DEBUG_MODE=True| Message | Meaning |
|---|---|
Connected to mqtt.pskreporter.info |
MQTT connection successful |
Subscribed to topic: pskr/filter/... |
Topic subscription active |
Received spot from ... |
Spot data being processed |
Feed health: healthy |
Data flowing normally |
Connection lost |
MQTT disconnected (will auto-reconnect) |
- Check existing issues: GitHub Issues
- Enable debug logging and capture relevant logs
-
Open new issue with:
- Home Assistant version
- Integration version
- Debug logs
- Steps to reproduce
- Website: pskreporter.info
- MQTT Feed: mqtt.pskreporter.info
- Status Page: Check for any announced outages