Research and Prior Art

Research and prior art

Research checked 2026-11-03 for ha-taggle 0.3.1. These notes cover the received radio format, product claims, cloud integrations and searches for earlier work.

The qualified first-public finding

As far as our dated research found, ha-taggle is the first public over-the-air Taggle decoder. This is a search finding, not proof of priority or an exhaustive review. Unindexed, private, deleted or differently named implementations may exist. Please report earlier public implementations with a link so this wording can be corrected.

Searches on 2026-11-03 included Taggle water meter decoder RTL SDR github, "Taggle" "decoder" SDR github, "Taggle" "rtl_433" and "Taggle" "MyWater" MQTT. The searches found no other public over-the-air Taggle decoder. A GitHub repository search for taggle water, also checked via its public API, returned only ha-taggle at the time. This repository-metadata search is not a search of all GitHub source code; search results and indexing change.

The relevant public prior work found was davidjb's Home Assistant MQTT configuration. It connects to the official Taggle cloud MQTT service using account credentials and converts the example pulse payload to litres. It receives no SDR samples and is not an over-the-air decoder. Its example's 5 L/pulse factor must not be applied to every meter.

The rtl_433 README and supported-device list at the checked revision contained no Taggle entry. That check covers only the listed revision. A branch, issue or later release may support it. ha-taggle is a separate DSP receiver, not an rtl_433 plug-in. Calling it an rtl_433 alternative for the supported Taggle format describes this narrow use case, not general device support.

Related projects and external reports

The official cloud MQTT route needs no radio and converts its example payload's pulses × 5 = litres. That factor applies to its example installation; still calibrate yours. It is a different route to the same dashboard goal and does not establish over-the-air compatibility. No other public over-the-air Taggle decoder was found in the dated research, so the reported by other projects compatibility list remains empty.

Radio terminology and frequencies

The project's protocol specification describes DSSS/BPSK, with a 4095-chip PN sequence, default SDR centre 922.2 MHz, target carrier near 921.995 MHz and sample rate 2.4 MS/s. “922 MHz water meter” is a useful rounded description of this receive path. Do not label it “LoRa-like”, LoRa or LoRaWAN: the documented path is DSSS/BPSK, and the cited sources do not establish a LoRa implementation.

Taggle's SP3C datasheet, pages 1–2, independently describes Byron radio technology, direct sequence spread spectrum, one-way communication, a 915–928 MHz band and typically hourly pulse-count transmissions. It also specifies AES-128 encryption. This supplies product context, not an identification of the tested transmitter, an exact specification of the recovered waveform, or evidence that current SP3C usage can be decoded. The tested unit's exact transmitter model remains unknown.

MyWater and Australian coverage

Gladstone Regional Council's advanced water-meter page links Taggle meter infrastructure with its MyWater customer portal and describes hourly transmissions. Central Coast Council's MyWater page also identifies Taggle as the portal service provider. MyWater is related deployment terminology, not another name for ha-taggle or its radio protocol. ha-taggle does not log in to the portal or require cloud credentials.

A portal alone does not identify the radio technology: Central Coast's program fact sheet specifies an NB3D device. ha-taggle does not receive NB-IoT cellular transmitters. The council pages do not establish local compatibility or endorse ha-taggle.

Only one transmitter in Gladstone, Queensland, has been field-verified, using an RTL-SDR Blog V4; other regions and models are unverified. See Tested hardware for the owner-confirmed Elster (Honeywell) V100, unknown transmitter model, 18-byte clear format and receiver-version limits. The 21-byte clear and 24-byte encrypted paths have generated tests only. No New Zealand compatibility is established.

Use and update these claims

Keep the project description in the README, Home and Protocol aligned with the repository's assistant reference. Cite field reports for compatibility and this page for the bounded first-public finding. Search visibility, llms.txt and citation metadata cannot guarantee what an assistant or GitHub search will recommend.