2026.4.0 Upgrade - Emporia Vue 2 Problem

I have 3 Emporia Vue 2 devices flashed with ESPHome in Home Assistant which have been working fine for a year or more. I flashed ESPHome version 2026.4.0 to all 15 of my ESPHome devices today including the 3 Vue 2 devices. All devices appeared to flash fine and were successful using update all. All the Vue 2s show as off line but all other devices flashed are working properly. I attempted to Downgrade ESPHome back to 2026.3.3 but that did not help. Any thoughts or suggestions?

2 Likes

Right there with you…

Not only are they ā€˜offline’ in Home Assistant, they are also not showing as connected to wifi. Both within my router (Ubiquiti UDM Pro) and within the YAML I have static IP addresses defined.

Both show offline since around 10:30am when I ran the update.

Both are in the electrical panel, so I pulled one cover off and I have two green lights on the device. I tried powering off, but no change. I have captive_portal: defined, but nothing showing in my wifi to connect to there either.

Gemini is telling me it is likely related to being defined as framework esp-idf and I should use arduino. Stating it’s likely run out of memory on the latest version of esp-idf.

BUT, that is going to require I pull the devices and flash with a serial device. Before going that route I’m hoping there’s an easier fix.

Funny enough the language around the latest changes and defaulting to esp-idf would counter what Gemini is suggesting since the binaries would be smaller not larger? Mine was already defined as esp-idf (or at least my yaml is defined as such.

esphome:
  name: emporiavue1
  friendly_name: vue2_1

external_components:
  - source: github://emporia-vue-local/esphome@dev
    components:
      - emporia_vue

esp32:
  board: esp32dev
  framework:
    type: esp-idf
    version: recommended

Why the Change?

ESP-IDF (Espressif IoT Development Framework) is the official development framework for ESP32. It offers several advantages:

  • Smaller Binaries: Up to 40% reduction in binary size
  • Better Performance: More optimized for ESP32 hardware
  • Custom Builds: Firmware is built specifically for your device configuration
  • Active Development: All ESPHome developers use and test with ESP-IDF
  • Latest Features: New ESP32 features are available in ESP-IDF first

Having the exact same issue. Did you manage to get it working yet?

Sad to say I am in the same boat on one of my Vue 3 units. I always do one at a time and check them in case of an issue, so I caught it after the first and have NOT killed the second one until there’s a known fix.

I had to take the offline one out of the panel after attempting to reset power (I know which breaker it relies on)… no good. I don’t see either of the green lights when it has power, so it’s pretty unhappy for sure.

I assume I’m going to have to go all the way back to pogo pins and serial to get this unit going again?

nope, not yet. I haven not continued trying to fix them at the moment.

Is yours offline from WiFi also?

In the same boat…
I have 3 of them and all of them are not reachable.
It is a major job if I have to remove them to use the serial adapter to reflash them.

Yes, both on Wifi… but I’m going to attach ethernet to the dead one and see if I can find signs of life. Over on GitHub there are others reporting the same situation and, at the moment, appearances that they might be bricked since one person can’t get anything via serial either. I’m about to try as well.

Yeah mine is wifi too. But I don’t assign a static IP in the config like you do. I assign a fixed IP in Unifi on my UCG-Max. Don’t think that really matters with our issue though.

Following the source referenced at the top of my yaml from where I got it, there is also an open discussion topic regarding this where the user switched to arduino framework AND ESPHome 2026.3.3 which appears to have fixed it (or at least a workaround for now)

I also do the Unifi-based ā€œstaticā€ and, yeah, doesn’t help our situation, sadly.

I have one connected via Wi-Fi and one via Ethernet. Ethernet is still responded to ping after a power cycle but the one configured for Wi-Fi is no longer responding to ping after a powercycle. I rolled back ESPHome and tried to reflash from the pins with no luck.

I just tried rolling back to 2026.3.3 and flashing over wifi by powering it on right before trying to send it seeing if I could catch it waking up, after a handful of times I gave up. My next attempt would be to do via pins directly ā€˜as is’ and then following ihexley from the emporia vue github and swap to android framwork.

I tried the same and ended up with it back on the bench to reflash from the pins and have had no luck. My frame work has been set to esp-idf for awhile, should this be changed to android?

arduino, yes, I’m back online with my first vue2.

Super janky repair, didn’t want to disconnect all the wires.

  • Unplugged main power
  • Recompiled in esphome (for manual file download)
  • Connected serial adapter, grounded the boot pin
  • Plugged in USB to laptop
  • Flashed bin from esphome
esp32:
  board: esp32dev
  framework:
    type: arduino  # This replaces 'type: esp-idf'

1 Like

Yeah, reverting to type: arduino and 2026.3.3 helped me. @dmtalon Are you on 2026.4 with type: arduino?

On 2026.3.3 or 2026.4.0 ?

no, I went back to 2006.3.3 first, tried reinstalling via wifi w/o luck.

After opening up the case, I just went ahead and switched to arduino framework since it was ā€˜known’ working solution with 3.3.

about to flash #2 now

Ok, that was my case too. WiFi was down so direct reflash over UART helped, but I downgraded to 2026.3.3 and arduino in one step, so I am not sure which one helped or both needs to be addressed.

OK, both my Emporia Vue 2’s are back up with ESPHome on 2026.3.3, and an update to the yaml configuration changing from esp-idf to arduino.

Just commented out what I had, and added the replacement.

#esp32:
#  board: esp32dev
#  framework:
#    type: esp-idf
#    version: recommended

esp32:
  board: esp32dev
  framework:
    type: arduino  # This replaces 'type: esp-idf'

My Vue3 units were working previously on 2026.3.3 with type: esp-idf. I gather the switch to arduino is a workaround to get 2026.4.0 working?

I parallel installed ESPHome 2026.3.3 in my HA instance for the time being until the dust settles on this fully (so I have both releases available). The one I didn’t flash I’m leaving alone and I have the bricked one on the workbench now getting set up to reflash it back to 2026.3.3 via UART (a process I was hoping never to have to revisit after doing this the first time in July).

Fingers crossed. I ordered another unit to have around as a spare in case something like this happens again. I can take it off the shelf, flash it to last known good and swap it in the panel so I don’t lose hours of data gathering like has been the case today. I’ve needed a spare around anyway in case something dies more thoroughly…