[LAN] client enabled and found 0 device(s).

<!-- PLEASE READ BEFORE POSTING A NEW ISSUE
   → Please use this template as well as you can.
   → Things that may seem unimportant are often helpful in finding the cause of the issue.
-->

### What issue do you have? Please be as thorough and explicit as possible.

My plugin randomly stopped working over the past couple of days. I thought it was a network issue but even after wired in to the ethernet, it still persists. I updated everything, reinstalled, changed password on Govee and still no luck. Any help would be much appreciated!


### Details of your setup.
 - Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
     - **(1) Homebridge**

 - Which version of Homebridge/HOOBS do you have?
    - **Homebridge: v1.9.0 | Homebridge UI: v4.71.2**
 - Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
     - **Raspberry Pi, Node v18.20.7**

 - Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
    - **v. 10.16.0**

 - Which Govee devices do you have that are causing issues? Please include product models if applicable.

     - **H6008 bulbs**

### Please paste any relevant logs below.
```
[08/03/2025, 15:09:05] [Govee] [LAN] client enabled and found 0 device(s).
[08/03/2025, 15:09:09] [Govee] [HTTP] could not use existing access token as connect EHOSTUNREACH 3.221.120.92:443 at Function.AxiosError.from (file:///var/lib/homebridge/node_modules/@homebridge-plugins/homebridge-govee/node_modules/axios/lib/core/AxiosError.js:92:14).
[08/03/2025, 15:09:12] [Govee] [HTTP] disabling client as connect EHOSTUNREACH 34.224.43.119:443 at Function.AxiosError.from (file:///var/lib/homebridge/node_modules/@homebridge-plugins/homebridge-govee/node_modules/axios/lib/core/AxiosError.js:92:14).
[08/03/2025, 15:09:12] [Govee] [AWS] disabling client as requires HTTP client.
[08/03/2025, 15:09:12] [Govee] [BLE] disabling client as required hardware/packages not available.
[08/03/2025, 15:09:12] [Govee] ***** Disabling plugin [v10.13.0]. *****
[08/03/2025, 15:09:12] [Govee] ***** No devices found to initialise. *****
```

Other network checks since something seemed to be failing from the calls side..
```
# Checking if DNS resolution works for the first Govee server IP
# This command tries to find the domain name associated with the IP address
$ nslookup 34.227.45.117
117.45.227.34.in-addr.arpa name = ec2-34-227-45-117.compute-1.amazonaws.com.
Authoritative answers can be found from:
# Result: DNS works! This IP resolves to an Amazon AWS EC2 instance

# Checking if DNS resolution works for the second Govee server IP
$ nslookup 52.72.93.44
44.93.72.52.in-addr.arpa name = ec2-52-72-93-44.compute-1.amazonaws.com.
Authoritative answers can be found from:
# Result: DNS works! This IP also resolves to an Amazon AWS EC2 instance

# Testing network connectivity to the first Govee server
# The ping command sends 4 ICMP packets to test if the server is reachable
$ ping -c 4 34.227.45.117
PING 34.227.45.117 (34.227.45.117) 56(84) bytes of data.
From 192.168.XX.XX icmp_seq=1 Destination Host Unreachable
From 192.168.XX.XX icmp_seq=2 Destination Host Unreachable
From 192.168.XX.XX icmp_seq=3 Destination Host Unreachable
From 192.168.XX.XX icmp_seq=4 Destination Host Unreachable

--- 34.227.45.117 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 136ms
pipe 4
# Result: Connection failed! "Destination Host Unreachable" means the local network 
# can't find a route to reach this server - likely a routing or firewall issue

# Testing network connectivity to the second Govee server
$ ping -c 4 52.72.93.44
PING 52.72.93.44 (52.72.93.44) 56(84) bytes of data.
From 192.168.XX.XX icmp_seq=1 Destination Host Unreachable
From 192.168.XX.XX icmp_seq=2 Destination Host Unreachable
From 192.168.XX.XX icmp_seq=3 Destination Host Unreachable
From 192.168.XX.XX icmp_seq=4 Destination Host Unreachable

--- 52.72.93.44 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 146ms
pipe 4
# Result: Connection failed! Same issue with the second server
# This confirms a network routing problem rather than a server-specific issue
```