NOTE: This page documents the most commonly asked questions. For additional help, please visit the Support page, or use the Forums to report issues.

General Questions

What is OpenGarage?

OpenGarage is an open-source, universal garage door opener. A web-connected opener like OpenGarage provides the following advantages:

  • Remote Access: you can access your OpenGarage anywhere and at any time, whether you are at home, at office, or traveling away. You can also check the status of the door so you never worry if you forgot the garage door open.
  • Intuitive User Interface (UI): no more messing with a physical button and no need to run to the garage to open the door. Instead, use mobile apps or a browser to toggle the garage door and view its status.
Who is OpenGarage for?

OpenGarage is for homeowners as well as business owners looking to add remote status and control to their garage door. It’s low-cost and easy to install. Our app lets you access multiple OpenGarage controllers.

Where can I find the user manual?

You can find the latest OpenGarage user manual from either the Support page, or the OpenGarage Github repository.

Installation and Usage

What’s included in the package?

The package includes one OpenGarage controller. The optional add-ons include Security+ 2.0 adapter for systems with a yellow antenna and yellow learn button as well as a USB power adapter (optional since you can use any USB power adapter you may have at home).

Does OpenGarage have built-in wireless?

Yes, this is included with the device.

How do I install OpenGarage?

For quick guide on the installation and setup of OpenGarage, please watch this video:

Shipping Questions

How fast can you ship?

Unless noted otherwise, we ship within 1-2 days after your order is placed. Once shipped, you will get a notification with tracking number.

What shipping options do you provide?

For Domestic orders within the United States, we offer Flat-Rate Shipping via USPS. The delivery time is typically 2-4 days across the country.

For International orders, we offer the following options:

  • First-Class — no tracking number, not insured, delivery time 2-6 weeks (varies by country).
  • Priority — trackable and insured, delivery time 2-3 weeks.
  • Express — trackable and insured, delivery time 1-2 weeks.

Note that we are not responsible for customs duty tax payment, which varies from country to country. Also, if you choose the First-Class option, the package is not trackable and we are not responsible for package loss. Sometimes the package can take a long time to clear customs at your destination country. Delivery time varies by country, but 3-4 weeks are typical, and 6-8 weeks are not unseen.

If you have urgent need, please contact us directly (through the Support page) for custom shipping need.

Technical Questions

How do I update OpenGarage firmware?

Compiled firmwares are all released on OpenGarage Github repository. They may be found here.
Before proceeding, note that once a new firmware is uploaded, the log will be erased, so keep a copy of the log if you need to retain it.

  • Use the web interface to update firmware (click the ‘Update’ button at the bottom of the homepage or on the Options page).
  • If the built-in web interface is not responding, perform a factory reset (i.e. pressing the button for 5 seconds or more), then follow the setup steps but leave the cloud token empty (to avoid any potential Blynk connection issues). Once the firmware is updated, go to the Options page and put in the Blynk token, make sure the Accessibility is set to ‘Direct IP + Cloud’.
  • If neither of the above work, you can use a USB cable to flash a new firmware (see instructions below).

After updating firmware, check the bottom of the homepage and make sure the firmware version is correct.

How do I reflash the firmware using a microUSB cable?

In the event that the controller cannot boot correctly (such that you can’t have access to over-the-air update), you can reflash the firmware via a microUSB cable.

Step 1: Driver. Depending on your operating system:

  • Windows: driver is not required, except Windows 7 64-bit and Windows XP (install CH340 Windows driver).
  • Mac OSX: install CH340 Mac driver, and reboot.
  • Linux: driver is not required, but you need to run all following commands as root or with ‘sudo’.

Step 2: Bootloading mode and serial port.
Let the device enter bootloading mode. To do so, get a microUSB cable, plug the smaller end to the device’s USB port, then press and hold the pushbutton while plugging the cable’s other end to your computer. The LED light should stay on constantly, and you should not hear any buzzer sound. If not, unplug the USB cable and redo this step.

Next, the device should appear as a serial port and you need to find out the serial port name:

  • Windows: the serial port name is COM? where ? is a number. You can find out the port name in the notification area, or in Device Manager — Serial Port.
  • Mac OSX: the serial port name is /dev/tty.wchusbserial? where ? is a number. You can find out the port name by running ls /dev/tty.wch* in Terminal (i.e. command line).
  • Linux: the serial port name is /dev/ttyUSB? where ? is a number. Run ls /dev/ttyUSB* in command line to find out.

Step 3: Reflash firmware.

Download the OpenGarage reflash package and unzip it. The package includes esptool, nodemcu firmware, and OpenGarage firmware. Open a Terminal (i.e. command line window), cd to the folder where you unzipped the package. Depending on your operating system, run the following command (assuming the device is in bootloading mode):

  • Windows: esptool.exe -cd ck -cb 230400 -cp COM? -ca 0x00000 -cf nodemcu.bin where COM? is the serial port name you found in Step 2 above.
  • Mac OSX: ./esptool_mac -cd ck -cb 230400 -cp /dev/tty.wchusbserial? -ca 0x00000 -cf nodemcu.bin where wchusbserial? is the serial port name you found in Step 2 above.
  • Linux: sudo ./esptool_lin32 -cd ck -cb 230400 -cp /dev/ttyUSB? -ca 0x00000 -cf nodemcu.bin where ttyUSB? is the serial port name. If you use Linux 64-bit, use sudo ./esptool_lin64 instead.

If you encounter any error, check if the device is in bootloading mode. Repeat Step 2 to enter bootloading mode before flashing.

Finally, once the nodemcu firmware is flashed, re-enter bootloading mode (Step 2) and run the above esptool flashing command again, except replacing nodemcu.bin at the end with og_1.0.4.bin. This completes the firmware reflashing.