[WIP] **_{_{}} Restore exception handling in Pi reachability check**

[Copilot]

Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.

Original issue description:

Restore exception handling in Pi reachability check

The call to is_pi_reachable used to catch requests/urllib failures and return False when the Raspberry Pi is offline. The except clause was removed, so any network error now propagates and crashes the client during startup instead of falling back to the offline screen. Reintroduce the error handling so transient connection errors don’t terminate the application.

Useful? React with 👍 / 👎.

Originally posted by @chatgpt-codex-connector[bot] in #38 (comment)

Original prompt

---

This section details on the original issue you should resolve

<issue_title> Restore exception handling in Pi reachability check</issue_title>
<issue_description> Restore exception handling in Pi reachability check

The call to is_pi_reachable used to catch requests/urllib failures and return False when the Raspberry Pi is offline. The except clause was removed, so any network error now propagates and crashes the client during startup instead of falling back to the offline screen. Reintroduce the error handling so transient connection errors don’t terminate the application.

Useful? React with 👍 / 👎.

Originally posted by @chatgpt-codex-connector[bot] in #38 (comment)
</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes #89

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.