On current firmware it's a plain, production-ready operation — no special mode, jumper, or factory tooling.
You stage the new address, arm the change, and commit it (a two-phase, magic-armed sequence so an address can't
change by accident); the module reboots at its new address. Do it one module at a time, with the others
disconnected, so there's no address clash. Your library exposes it directly (e.g. prepareAddressChange() /
commitAddressChange(), or a fleet-provisioning helper).
30 de julio de 2026
por
Administrator
en FAQ