The mobile app rejects the username or password even after a password change, while the Arduino temperature-monitoring project uses four sensors. Treat this first as an account or app sign-in problem, not a sensor fault: sensor readings do not validate credentials. Use the checks below to locate whether the failure follows the account, the phone, or the app configuration before changing the project.
Check whether the same account works on a computer
Sign in from a computer using the same service or application account and the exact username entered on the phone. Do not assume that the Arduino project’s name, a device name, or an email address is the login identifier; use the identifier required by that app.
| Result | Meaning and next check |
|---|---|
| Computer sign-in also fails | Investigate the account credentials, account status, or service-side authentication before troubleshooting the phone. Use the app or service’s official password-recovery flow once, then test again. |
| Computer sign-in succeeds | The account credentials work. Continue with the phone’s app version, stored sign-in state, and selected service or workspace. |
Repeatedly changing the password without testing another sign-in path can leave multiple saved credentials out of date. Record which account identifier was accepted on the computer, then use that same identifier on the phone.
Check whether this phone has signed in before
Determine whether this specific smartphone previously accessed the application. A phone that has never signed in points toward a first-login, account-selection, or app-configuration problem. A phone that worked before points toward a changed password, stale saved credentials, an app update, or a changed service connection.
- First-time phone: Confirm that the installed app is the correct app for the service hosting the project, and that it is configured for the intended account or workspace.
- Previously working phone: Re-enter the current credentials rather than relying on autofill. Remove an obsolete saved password from the phone’s password manager if it keeps replacing the new one.
Do not delete the project or alter sensor wiring to address a login rejection. Those actions do not repair authentication and can introduce a separate commissioning problem.
Update the app and retest the credential entry
Check the phone’s app store for an update to the application. An old mobile client can behave differently from a current desktop sign-in, so retest after updating. Before submitting credentials, check the keyboard’s capitalization, layout, and automatic space insertion; passwords are commonly case-sensitive.
- Close the app and reopen it after the update.
- Enter the same account identifier that worked on the computer, if desktop access succeeded.
- Type the current password manually once; verify capitalization and remove any leading or trailing space.
- Submit the login and note the exact message and whether it appears immediately or after a delay.
If the app still reports incorrect credentials while the computer accepts them, stop cycling through password resets. Continue by checking the phone’s saved app state and the destination selected inside the app.
Confirm the app is pointed at the intended account or service
Some mobile applications separate account sign-in from selecting a project, workspace, server, or organization. The exact labels depend on the app. Confirm that the phone is using the same service and account context as the computer; a valid password for one account or service will not authenticate to a different one.
If the app offers an account or environment selector, compare the displayed selection with the working computer session. Also confirm the phone has network access and can reach the intended service. A connectivity failure often produces a connection or timeout message rather than a credential rejection, but app error wording can be imprecise. Record the exact message rather than treating every sign-in failure as a bad password.
Restore access without disturbing the sensor project
When computer sign-in works but the phone still fails, keep the project unchanged and isolate the mobile client. Confirm the app update, use the correct account identifier, enter the current password manually, and verify the selected service or workspace. If the app provides an official sign-out or account-switch action, use it and sign in again. Avoid clearing app data or reinstalling until project or connection settings are backed up; those actions may remove local configuration without fixing a server-side or account-selection issue.
After a successful sign-in, open the four-sensor project and verify that the expected temperature values appear and update. A successful login alone does not prove the monitoring path is healthy. If sign-in succeeds but the project or values are missing, troubleshoot project permissions, service selection, and data connectivity as a separate problem.
FAQ
What happens if the password change still does not let me sign in?
Test the same account on a computer and use the identical account identifier on the phone. If desktop sign-in works, update the app and replace any stale password saved by autofill before resetting the password again.
What happens if I can sign in on a computer but not on my phone?
The credentials work, so check the mobile app version, saved credentials, account selection, and configured service or workspace. Do not change sensor wiring or delete the project to fix an app login rejection.
What happens if the phone has never connected to this application?
Verify that it has the correct application and the intended account or workspace selected. Then enter the working account identifier and current password manually and check the exact error shown.
What happens if login succeeds but the four temperatures are missing?
Authentication is working; check that the phone opened the intended project and account context, then investigate project access and data connectivity separately. Preserve the project configuration while diagnosing the monitoring path.
Stop repeated password changes if the computer accepts the account but the updated phone app still rejects it, or if the app shows an account or service error you cannot resolve. Contact the application provider’s official support channel with the app name, phone platform, exact error text, app version, and results of the computer sign-in test.