Pull feeds let ProbeHarbor fetch HTTPS JSON on a schedule when your probe already serves a public URL (or a TLS relay). For the full push and pull walkthrough that matches today’s Devices UI, start with adding push and pull devices.
Setup steps
- Verify the feed with curl: nested probes under a root object (default
temp). - Open Dashboard → Devices → Pull feeds tab.
- Add the HTTPS URL and set JSON root key if your object is not named
temp(e.g.readings). - Use Test feed URL, then Save pull setup: probe keys auto-import.
- Rename labels on the same page or click Accept suggested names.
JSON root key
Pull parsing looks for { "<root>": { "0": { "f": …, "h": … }, … } }. The root defaults to temp. Flat push-style keys and typed sensors[] are for push ingest, not the default pull path.
SenML and Home Assistant REST
When the configured root is missing, ProbeHarbor auto-detects SenML JSON (RFC 8428 array) and HA REST sensor JSON (state + attributes). Paste the HTTPS URL as-is, no JSON root override needed. Map probe keys from SenML names (e.g. 0) or state for single-entity REST feeds. Try the public SenML example or HA REST example.
Multiple feeds
You can add several pull URLs (plan limits apply). Document which URL is production vs demo. Security: relay security. Fetch behavior: home page probe fetch.
Troubleshooting
Wrong root key or probe key typos hide cards even when the URL returns 200. See debugging stale readings.