Record software support separately from the warranty

A support period answers a different question

Software support describes a documented commitment about a device's software, while a warranty sets out a separate promise and its terms. Do not label either one simply as lifespan. The Australian Hue Bridge 8719514342569 documentation gives a minimum 36-month support period from purchase through an authorised reseller. The archived Smart button documentation gives a minimum 60 months on that stated basis. Those are model-specific descriptions, not a tested service life or proof that a particular old device still has support remaining. Keep the exact wording and the relevant product identity beside every copied duration.

Hue AU Bridge 8719514342569 ? Hue AU Smart button 8719514342682 documentation ? ACCC warranties guidance ?

Record the trigger for the period

A number of months is incomplete without its starting event. Write down whether the source refers to purchase, manufacture, product launch, a fixed end date or another defined trigger. For the documented Hue examples, preserve the authorised-reseller purchase condition rather than substituting the day you happened to read the page. The archived Bridge and dimmer photographs show identifiable hardware forms, but neither proves purchase date or qualifying seller. A support comparison therefore needs both the manufacturer statement and your actual purchase evidence; a photograph of a familiar enclosure cannot fill either missing field.

Use an illustrative month difference carefully

The difference between the two documented minimum durations is 60 − 36 = 24 months. That arithmetic does not establish which product is better, because a button and a bridge perform different roles and the statements apply to their own exact models. Nor does it show that a particular used unit has 24 more months remaining. A useful comparison records model, statement, starting condition and confirmed purchase date, with any current support information saved separately. If the source gives an end date instead, preserve it directly rather than forcing every statement into the same month-count format.

Keep warranty and consumer guarantees beside it

ACCC guidance distinguishes warranties from consumer guarantees: a warranty is additional to those guarantees. Keep the actual warranty document and proof of purchase without assuming that a software-support duration is a warranty duration or a universal limit on other rights. This guide does not determine an individual remedy, product defect or legal entitlement. For a concrete issue, retain the model, seller, dates, fault description and relevant documents so the appropriate official guidance or dispute route can address the actual circumstances. Avoid replacing those details with a simplistic expiry label inferred from a marketing table.

Build a reviewable support file

Store a dated copy or link for the exact support statement, the hardware generation and purchase record, plus the official support contact route. The unpacked archive Bridge photo highlights documentation as a separate package item; its European adapter and historical state do not identify an Australian purchase. If later guidance changes, preserve the earlier statement and add the new version with its date rather than quietly rewriting history. Your shortlist can then distinguish a confirmed commitment, an unverified used-device history and an unresolved support question. That is more useful than treating connectivity as a guarantee of indefinite updates or treating an old photograph as current support evidence.

Open official model documentation ? Open official model documentation ? Open official model documentation ?