Hello,
Thank you for your reply. Unfortunately, the suggestions provided do not match the behaviour of the device, and this issue cannot be resolved by clearing browser cache or using Incognito mode.
I need to clarify the actual failure mode, because this is not a UI rendering problem — it is a firmware‑level boot failure affecting two separate Bridge Ultra units on two different networks.
Key Technical Details:
Both Bridge Ultra devices fail in the same way, within the same 24‑hour period, on completely separate networks.
This rules out local network issues or hardware failure.
The device does appear in DHCP and the local web UI loads, which means:
The OS has booted
The network stack is running
The web server is running
However, the backend services do not start, which is why:
The time‑zone dropdown is completely empty
The UI shows “Connection lost. Reconnecting…”
Zigbee does not initialise
The reset button does not function
The device cannot complete first‑time setup
This behaviour is consistent with a failed Zigbee/coordinator initialisation or a failed cloud token/firmware signature validation, not a browser issue.
One of the units was not deleted from eWeLink and shows identical symptoms, which confirms this is not related to account removal.
This is a firmware regression, not a user‑side issue.
The device is stuck in a half‑boot state where the frontend loads but the backend services never start. This is why the time‑zone list cannot populate — the service responsible for loading it never initialises.
Requested Action:
Please escalate this case to your engineering team.
They will immediately recognise this as a backend/firmware boot failure affecting the Bridge Ultra.
I am happy to provide:
System logs (once the backend is able to generate them)
Screenshots
Network traces
MAC addresses of both affected units
But at this stage, the device cannot complete setup, cannot reset, and cannot initialise Zigbee due to the backend service failing to start.
This is not a hardware defect and not a browser issue — it is a firmware‑level problem that requires engineering intervention.
Thank you,
Steve