MyQ Home Bridge 斷網後一直重開機?教你取出 AES 金鑰並在本機模擬雲端伺服器
Dumping an AES key from a MyQ garage opener to stop rebooting when offline
把 MyQ Home Bridge 放進沒有外網的 IoT 網路後,它仍會一直嘗試連線到 Chamberlain 的雲端;連線逾時時,裝置可能每隔 5–10 分鐘重開機,讓 HomeKit 暫時連不上。把相關網域指向會立刻拒絕連線的本機服務,可以減少這種重開機,但裝置仍會每 30 分鐘重新啟動一次。文章接著示範如何從裝置取出 TLS-PSK AES-128 金鑰,再用 Docker 在本機架設 MQTT 伺服器,讓 MyQ Home Bridge 以為自己連上雲端,並把兩個雲端網域改指向這臺伺服器。依文中的測試方式,伺服器收到連線後,裝置的綠燈會維持恆亮;觀察超過 30 分鐘仍在運作,就能確認沒有再次重開機。
AI 伴隨問答
針對這篇報導有疑問?可直接點選快捷問題或向 AI 追問背景脈絡與技術細節:
Otherwise known as Chamberlain / LiftMaster 819LMB / MYQ-G0303 MyQ Home Bridge

The Problem
When isolated on an IoT VLAN with no WAN/internet access, the device constantly attempts to phone home to Chamberlain's cloud endpoints (presumably MQTT servers):
connect.myqdevice.com:8883connect1.myqdevice.com:8883
If these domains are unresolved or sinkholed to a non-existent server / 0.0.0.0, connection attempts hang and time out. Eventually, the internal watchdog reboots the device or its Wi-Fi module, causing it to go unavailable/unresponsive in HomeKit every 5–10 minutes.
Naive/Semi-Solution
Provide the device DNS resolution for connect.myqdevice.com and connect1.myqdevice.com pointing to a local IP/service that will immediately refuse the connection (TCP RST). This is a half-baked solution: it stops the 5–10 minute crash loops, but still triggers a watchdog reboot every 30 minutes.
100% Fix: 30-Minute Watchdog & Local Cloud Spoofing
Unfortunately, there is a caveat to all of this. If the device doesn't successfully connect to the myQ cloud MQTT servers and receive a retained message (ping) back when subscribed to the appropriate topic, it reboots on a 30 minute timer. Meaning, every 30 minutes you have a small period of downtime where the homekit integration will be unresponsive.
To remediate this, you must dump the TLS-PSK AES-128 key on the device in order to setup your own MQTT server with the appropriate DNS. Basically, pretend you are the myQ MQTT server.
This is done by connecting to the Cortex-M4 CPU debug pads left conveniently by Chamberlain on the PCB.

To dump your device's TLS-PSK AES-128 key:
Requirements:
- Arduino (I used the Uno) + Arduino IDE
- 2 resistors between 220Ω to 1000Ω (I used a 560Ω)
- This protects you from accidentally frying your 819lmb board from the Arduino's 5V pins
- Jumper wires
- Tape
- Take off the top shell (two screws)
- Find the CPU 10 pin debug pad. Pin 1 is marked with an arrow. See picture

Connect Pin 2 (SWDIO) -> Resistor -> D8 on the Arduino
Connect Pin 4 (SWCLK) -> Resistor -> D9 on the Arduino
Connect GND on the board (I used the power connector ground) -> GND on the Arduino
Using the Arduino IDE, Compile/Upload the key dumper sketch: Arduino Script
Verify connections and power on the 819lmb
Open the Serial Monitor at 115200 baud. Output should look something like this:
===================================================== LiftMaster 819LMB Hardware Credentials Dumper ===================================================== [*] Armed and waiting for probe contact on test pads... Pins: D8 (SWDIO) -> Pad 2, D9 (SWCLK) -> Pad 4, GND -> GND ........ ----------------------------------------------------- [+] Contact detected! ARM CoreSight IDCODE: 0x2BA01477 [+] CPU Halted. PC=0x1F01A3AA, SP=0x107B90 [*] Scanning flash space (0x1F000000 - 0x1F070000) for NVM signatures... Scanning 0x1F000000... Scanning 0x1F010000... Scanning 0x1F020000... [+] Discovered NVM function at 0x1F02F7EC (scan took 128866 ms) [+] Target nvm_rd_myq_serial at: 0x1F02F7A8 [+] Target nvm_rd_myq_aes_key at: 0x1F02F84C [+] Target stack and CPU state restored. Bridge resumed. ===================================================== >>> EXTRACTION SUCCESSFUL! <<< Serial Number : <extracted_serial_number> AES-128 Key : <extracted_aes_key> ===================================================== Extraction complete. Probes may be safely disconnected.
Step 2: Run the Local Mosquitto Broker Container
Pull and run the Docker container with your extracted credentials
docker run -d -p 8883:8883 \
-e MYQ_SERIAL=<extracted_serial_number> \
-e MYQ_PSK=<extracted_aes_key> \
ghcr.io/kushagharahi/myq-homebridge-jailbreak:latest
Step 3: Redirect DNS
In your local DNS server, point both domains to the IP of the machine running the container:
connect.myqdevice.com→<CONTAINER_HOST_IP>connect1.myqdevice.com→<CONTAINER_HOST_IP>
Verification
- The green light should no longer be flashing, instead solid to indicate "cloud" connectivity
- The container logs should show something like
1794793990: New client connected from 10.42.0.1:32806 as <extracted_serial_number> (p4, c1, k360).
1794793990: Client <extracted_serial_number> negotiated SSLv3 cipher PSK-AES128-CBC-SHA
- Do a
GETonhttp://<device-local-ip>/jabout, you should see"internet_connected": "Yes",.- Do another after 30 minutes and ensure your
powered_timeis over 30 minutes, meaning no reboots have occurred.
- Do another after 30 minutes and ensure your