Record the tested model and firmware basis for the functions that matter to the buyer.
A supplier may keep the same product name while its software gains, changes or exposes functions differently. Identify which part of the proposal was verified on a sample and which part still depends on a current compatibility statement. Do not present a roadmap item as delivered.
Agree when firmware will be reviewed during installation and who approves an update affecting the acceptance test. Staff should not update every sample or customer device casually just to make a demonstration look current.
Retain a short change note with the project record. It should describe the relevant behaviour and the new test result rather than copy a long release history. This gives the service team something practical to use when a customer later asks why an automation no longer looks the same.
Before you order
- Record versions for critical verified functions.
- Separate current features from roadmap claims.
- Retest affected behaviour after an approved update.
A useful next step
Discuss the version assumptions and test scope with SmartAccess before procurement.
Related equipment
Selling smart-home products? Planning a store in Canada or the US?
Talk with SmartAccess about product selection, a demonstration range, installation partners and project delivery. Retailers, dealers, installers and local store operators are welcome.
Product supply, training, service area, cooperation terms and any fees are confirmed in discussion. No revenue or lead volume is promised.
Manufacturer references
Product information comes from the linked manufacturer references. Confirm the exact regional model, seller, current price, stock and installation conditions before purchase.
