Unit keeps resetting

Konnected Garage Door Opener
1

I got a white GDO for my dad and was very impressed with it so I decided to get one for myself. Just got mine this afternoon.

I wanted to check to see if the firmware on the unit was the latest version (my dad’s was 1.2.0 vs 1.2.1 on the web).

Oddly enough the unit keeps resetting as soon as I connected it to my computer (Using chrome) [the port keeps disappearing and reappearing], the serial driver is installed from when I did my dad’s about a month ago.

I tried a different cable and different port on the computer. I launched the console and the log is below. It is attached to a good power source (UPS). I don’t have another power brick that does 1W@12A. Anything else I can try before I RMA it?

[D][binary_sensor:036]: 'garage_door_range_sensor': Sending state OFF
[D][cover:170]: 'Garage Door' - Publishing:
[D][cover:178]:   State: CLOSED
[D][cover:186]:   Current Operation: IDLE
[D][esp32.preferences:114]: Saving 1 preferences to flash...
[D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[D][esp-idf:000]: W (45081) wifi:
[D][esp-idf:000]: Haven't to connect to a suitable AP now!
[D][esp-idf:000]: 

[W][wifi_esp32:926]: esp_wifi_sta_get_ap_info failed: ESP_ERR_WIFI_NOT_CONNECT
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x1658
load:0x403c9700,len:0xbd4
load:0x403cc700,len:0x3034
entry 0x403c9954
I (24) boot: ESP-IDF 4.4.6 2nd stage bootloader
I (25) boot: compile time 14:19:56
I (25) boot: Multicore bootloader
I (27) boot: chip revision: v0.1
I (30) boot.esp32s3: Boot SPI Speed : 80MHz
I (35) boot.esp32s3: SPI Mode       : DIO
I (40) boot.esp32s3: SPI Flash Size : 4MB
I (45) boot: Enabling RNG early entropy source...
I (50) boot: Partition Table:
I (54) boot: ## Label            Usage          Type ST Offset   Length
I (61) boot:  0 otadata          OTA data         01 00 00009000 00002000
I (68) boot:  1 phy_init         RF data          01 01 0000b000 00001000
I (76) boot:  2 app0             OTA app          00 10 00010000 001c0000
I (83) boot:  3 app1             OTA app          00 11 001d0000 001c0000
I (91) boot:  4 nvs              WiFi data        01 02 00390000 0006d000
I (98) boot: End of partition table
I (103) esp_image: segment 0: paddr=00010020 vaddr=3c100020 size=373c8h (226248) map
I (152) esp_image: segment 1: paddr=000473f0 vaddr=3fc991d0 size=04370h ( 17264) load
I (155) esp_image: segment 2: paddr=0004b768 vaddr=40374000 size=048b0h ( 18608) load
I (161) esp_image: segment 3: paddr=00050020 vaddr=42000020 size=f3920h (997664) map
I (345) esp_image: segment 4: paddr=00143948 vaddr=403788b0 size=1091ch ( 67868) load
I (368) boot: Loaded app from partition at offset 0x10000
I (368) boot: Disabling RNG early entropy source...
I (380) cpu_start: Multicore app
I (380) cpu_start: Pro cpu up.
I (380) cpu_start: Starting app cpu, entry point is 0x403762d4
I (0) cpu_start: App cpu up.
I (398) cpu_start: Pro cpu start user code
I (398) cpu_start: cpu freq: 160000000
I (398) cpu_start: Application information:
I (401) cpu_start: Project name:     konnected
I (406) cpu_start: App version:      2024.4.1
I (411) cpu_start: Compile time:     Apr 25 2024 14:18:51
I (417) cpu_start: ELF file SHA256:  69962676fdf6ff20...
I (423) cpu_start: ESP-IDF:          4.4.6
I (428) cpu_start: Min chip rev:     v0.0
I (432) cpu_start: Max chip rev:     v0.99 
I (437) cpu_start: Chip rev:         v0.1
I (442) heap_init: Initializing. RAM available for dynamic allocation:
I (449) heap_init: At 3FCA52E8 len 00044428 (273 KiB): D/IRAM
I (455) heap_init: At 3FCE9710 len 00005724 (21 KiB): STACK/DIRAM
I (462) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM
I (468) heap_init: At 600FE000 len 00002000 (8 KiB): RTCRAM
I (475) spi_flash: detected chip: gd
I (479) spi_flash: flash io: dio
W (483) spi_flash: Detected size(8192k) larger than the size in the binary image header(4096k). Using the size in the binary image header.
I (497) sleep: Configure to isolate all GPIO pins in sleep state
I (503) sleep: Enable automatic switching of GPIO sleep configuration
I (510) coexist: coexist rom version e7ae62f
I (515) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
Terminal disconnected: NetworkError: The device has been lost.
2

I don’t see anything that indicates a problem here. Are you just trying to re-flash it before you set it up? You really shouldn’t need to. The firmware update can be done over-the-air now via the Konnected app after you get it connected to WiFi.

Sometimes the USB port can disconnect like this if the device doesn’t have enough power. Make sure you have the power adapter plugged in while it’s connected to the computer by USB. Or, use a powered USB hub.

3

I was just checking the firmware version, was not going to reflash it just for fun.

The disconnection is what I was referring to. It is plugged into a UPS into a wall outlet using the provided AC adapter.

4

Not sure why it would disconnect like that. It could be a hardware issue but unlikely because we flashed it using the same USB port just weeks ago (see the build date there of April 24) and clearly it was successful because otherwise it wouldn’t be in your hands right now.

It could be an issue with the computer, chrome, USB cable… hard to know.

Try connecting via command-line instead of via the browser to rule that out?

The “App version” shown here is actually the ESPhome version that it’s built on, not the project version. The project version will be shown in the Konnected app or Home Assistant when it’s discovered. The current version for GDO White is 1.2.1.

Again, I don’t see anything that screams problem.

5

The way the port kept disappearing I was thinking hardware resets or not enough power resets. I’ll install it in the garage and see if it’s discoverable and if it stays online. Thank you for checking.