RDKEAPPRT-899 If QueryPowerState is standby ,after reboot QueryPowerState is shown ON

[suryag23]

No description provided.

[Copilot]

Pull request overview

This PR adjusts power-state restoration logic during/after reboot so that a device previously in STANDBY is not incorrectly treated as ON after reboot, and adds a session-scoped guard intended to avoid re-running restoration logic on UI reloads (e.g., language changes).

Changes:

• Removes logic that forcibly converted POWER_STATE_STANDBY to POWER_STATE_ON during reboot handling.
• Adds a sessionStorage flag (powerStateRestored) to skip power-state restoration on subsequent UI reloads within the same session.
• Updates _getPowerStatebeforeReboot() to short-circuit to current power state when the session flag is set.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (1)

accelerator-home-ui/src/App.js:993

• sessionStorage.powerStateRestored is set even when appApi.setPowerState(...) reports failure (res === false). In that case the power state was not actually restored, but subsequent UI reloads will skip restoration due to the flag, potentially leaving the device/UI in an incorrect state.

				sessionStorage.setItem('powerStateRestored', 'true');

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (1)

accelerator-home-ui/src/App.js:993

• powerStateRestored is set even when appApi.setPowerState(...) resolves false (it does not reject on failure). That can cause subsequent UI reloads in the same session to skip restoration even though the power state was never successfully applied.

						GLOBALS.powerState = res.currentState;
					});
					this.LOG("_PowerStateHandlingWhileReboot: powerstate after setting to new powerstate " + JSON.stringify(GLOBALS.powerState) + " and ");
				}
				sessionStorage.setItem('powerStateRestored', 'true');

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

Suppressed comments (1)

accelerator-home-ui/src/App.js:1043

• In the UI-reload short-circuit path, getPowerState() failure currently forces GLOBALS.powerState to POWER_STATE_ON, which is inconsistent with _getPowerStateWhileReboot() (defaults to STANDBY on error) and can incorrectly show ON when the device is actually in standby. Align the fallback state handling.

			}).catch(err => {
				this.LOG("_getPowerStatebeforeReboot: Error getting current power state: " + JSON.stringify(err));
				GLOBALS.powerState = PowerState.POWER_STATE_ON;
			});

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (1)

accelerator-home-ui/src/App.js:994

• The log line uses GLOBALS.powerState immediately after triggering appApi.getPowerState(), but the promise hasn’t resolved yet. This makes the log (and any debugging based on it) unreliable, and the call also lacks a .catch() here (unlike other getPowerState() usages in this file). Consider logging after the state is actually read, with an error path.

					appApi.getPowerState().then(res => {
						GLOBALS.powerState = res.currentState;
					});
					this.LOG("_PowerStateHandlingWhileReboot: powerstate after setting to new powerstate " + JSON.stringify(GLOBALS.powerState) + " and ");
					sessionStorage.setItem('powerStateRestored', 'true');

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (2)

accelerator-home-ui/src/App.js:987

• The comment says the restored-session flag is only set after a confirmed successful restore, but the code also sets powerStateRestored in the res === false branch. This is misleading and makes it harder to reason about the intended behavior (success-only vs. "handled once per UI session").

				// setPowerState resolves false when the call did not succeed, so only
				// mark the state as restored after a confirmed successful restore.

accelerator-home-ui/src/App.js:994

• appApi.getPowerState() is called after a successful setPowerState(), but the promise chain has no .catch(). If getPowerState() rejects, this becomes an unhandled rejection; also the subsequent log can print a stale GLOBALS.powerState value because it runs before the async update completes.

					appApi.getPowerState().then(res => {
						GLOBALS.powerState = res.currentState;
					});
					this.LOG("_PowerStateHandlingWhileReboot: powerstate after setting to new powerstate " + JSON.stringify(GLOBALS.powerState) + " and ");
					sessionStorage.setItem('powerStateRestored', 'true');

[yashaswini-rk]

Looks good

[suryag23]

getting the checks failed so trying to raise PR again