Cart
0
Swell Sport · Practical guide
Changing sauna-control phones: prepare the account handover
Replace a sauna-control phone as an account handover, not a heater reset. First preserve the equipment identity and account details, then verify the new phone’s access and separately resolve access remaining on the old phone.
Separate replacement from loss or theft
For a planned replacement, keep the old phone available until the new arrangement has been checked. For a lost or stolen phone, treat access removal as the first unresolved task and pause remote use while the account owner obtains the manufacturer’s current security instructions. Do not assume that installing the app elsewhere removes the old session.
Prepare the account email, controller model, app generation, device identifier and proof of ownership. Keep passwords and recovery codes in private storage, not in the sauna maintenance folder shared with trades. Record the phone change there only as an event, without credentials.
Confirm the app generation before signing in
The Fenix manual describes connection to MyHarvia and identifies MyHarvia 2 in its settings. It also says the Harvia web portal uses the same login credentials as MyHarvia 2. Keep the existing account identity with your records; a shared login relationship is not a promise that every setting or licence transfers automatically to a replacement phone. [1]
Check the official app link provided for the installed controller. Avoid creating a duplicate account simply because the new phone has no saved login. If an existing account cannot be recovered, ask support how ownership and any licence should be handled before pairing again.
Use a migration record with explicit unknowns
Before: old phone available __; account email confirmed __; controller model __; app name and version __; existing device name __; licence evidence retained __. After: new phone login confirmed __; correct sauna identified __; displayed status compared locally __; old access revocation method confirmed __; unresolved items __.
Do not use a remote heat command as the first identity test. Begin with the equipment off and verify the named device and visible status. If new pairing is actually required, follow the current official instructions for the exact model, not a sequence copied from another controller.
Respect the setup conditions
The Fenix manual says setup and connection through MyHarvia should be performed with the sauna off and fully cooled. It directs the user to follow the application’s pairing instructions. A phone change is not a reason to work beside operating hot equipment. [2]
If you cannot sign in, use the official account-recovery route or ask Harvia support for help. Treat restored login and removal of the old phone’s access as separate tasks. Ask support which steps apply to your app version and what confirmation to retain; do not assume changing a password ends every existing session.
Close the security handover with support
Ask: “For this controller and app version, how do I revoke the old phone’s active access, confirm which account owns the sauna, and retain any valid licence? What evidence confirms revocation?” Retain the response and mark the handover incomplete until the method and outcome are known.
For example, a planned phone upgrade may restore login successfully while leaving the old phone signed in. Those are two separate results. The new login can be recorded as successful without pretending the access-removal task has passed. Keep remote operation paused if you cannot establish who can still issue commands.
Your practical checklist
- Record model, account email and app generation privately.
- Do not factory-reset the heater to solve a phone issue.
- Verify device identity before any control command.
- Pair only under the documented cool, off conditions.
- Obtain and verify the exact old-session removal procedure.
Will everything transfer automatically?
Check account ownership, device identity and licence state separately. Ask support about anything that has not carried over rather than resetting the controller.
Does deleting the old app prove access is revoked?
Do not use app deletion as your proof. Obtain the manufacturer’s account/session removal instructions and confirm the result before closing the handover.
