Reporting Compatibility

Reporting compatibility

So far ha-taggle is confirmed on one transmitter. Every report, including "it didn't work", helps others decide whether to buy hardware.

Where to report

Open an issue on GitHub. You need a free GitHub account. GitHub explains how to create an issue. Pull requests that update the "reported working" list are welcome too.

What to include

Working or stuck? Report your result. The useful minimum is your ha-taggle version, installation method, council or utility, USB receiver model and what you saw: usage received, ID heard without usage, or nothing heard. Frame length and signal details are optional; unknown is fine. Follow the sharing checklist before posting.

Copy this template into your issue and fill in what you know:

**Council / utility:** e.g. Example Regional Council, QLD
**Suburb or town (optional, general area only):**
**Result:** Working / ID heard but no usage / Nothing heard
**Installation style:** clip-on / separate tag / integrated / not sure
**Label text (ID removed):** e.g. "taggle", barcode, no model number
**Frame length:** 18 / 21 / 24 bytes / unknown
**SNR (snr_median_db):** typical value, e.g. 10–14 dB
**Dongle:** e.g. RTL-SDR Blog V4
**Antenna and placement:** e.g. stock dipole, 8 cm arms, window 15 m from meter
**Frequency and gain:** e.g. 922200000, 40
**ha-taggle version and install type:** e.g. 0.3.0 add-on
**Water-use check:** matched / inconclusive / not tried
**Photo (optional):** transmitter with ID, serial numbers and barcodes covered

Tip

Frame length: unknown is fine. Report it only if explicitly shown in a privately inspected decoded summary. Release 0.3.0’s normal log and scan do not print byte length. counts for a configured ID establish a supported clear format, but do not distinguish 18 from 21 bytes. Missing counts for an unconfigured scan ID establish neither format nor encryption. Do not enable broad logging or upload private JSONL or scan output to fill this field. See supported formats.

What NOT to include

Warning

• ❌ Your real transmitter ID, or anyone else's
• ❌ Barcodes (they often encode the ID or serial)
• ❌ Your street address
• ❌ Your config.json, add-on options, state.json, neighbourhood.salt or JSONL logs
• ❌ MQTT usernames, passwords or IP addresses
• ❌ Radio recordings (.cu8 files)
• ❌ Scan output listing other people's IDs

When quoting a log line, replace the ID with 123456.

How to blur a photo

1. Open the photo in your phone's built-in editor, or a free editor on a computer.
2. Use the markup / draw tool and pick a thick, fully opaque pen or box.
3. Cover the ID, every barcode, and any serial numbers, completely.
4. Zoom in and check. Nothing should be readable.
5. Save as a new copy and share that.

Caution

Use a solid box, not a light blur or pixelation. Weak blurs can sometimes be reversed. Some phone editors also keep the original inside the edited file. Saving a screenshot of the edited photo is a simple way to make sure only the covered version is shared.

Further reading

• ha-taggle issues
• GitHub Docs: creating an issue
• Tested hardware
• Is my area covered?
• Contributing