Update to ESPHome 2025.4.1 impossible and also downgrade to 2025.2.2 #7008
Comments
|
Looks like you've used all your public quota platformio.org or sent too much connections and because of that server refused opening a connection for your IP. |
Thank you for answer. I want to reiterate, I am not doing anything unusual. I just want to update my devices. Nothing more. Nothing has been changed knowingly on my side. |
|
I just tried updating from 2025.2.2 to the new 2025.4.2. With the first device updating I get a similar error like above but the 'Looking for a mirror...' seems to work and the device is updated. See the log file from esphome--6 device: Then, as soon as repeat the same on another device, say esphome--5, I get the same error as above. I can't export a log, the text runs down like crazy. I have to press the STOP button. Then, ESPHome marks the device as updated. Not good. |
|
'ha dns info' tells me: Pinging works on both addresses, the second being the pfSense that also does DNS forwarding for the whole network. I am stuck now. I cannot reach platformio from inside the container, so that checks out: 'ha dns restart' and pinging platformio gives me this info in 'ha dns logs': |
The problem
After upgrading ESPHome to 2025.4.1 from 2025.2.2, upgrading the first device resulted in a lot of connection errors, for most of the libraries a second mirror was chosen. Updating the first device to 2025.4.1 seemed possible. Choosing a second EP for upgrading resulted in these strange errors show in the attached image. The error doesn't stop, just repeats like crazy until stop button is pressed.
Then reverting to ESPHome 2025.2.2 via backup and trying to downgrade the first upgraded device, the one that seemed successful, results in the very same error! Very strange behaviour.
However, all affected devices continue working, but it seems impossible to update in the future.
It looks like a connection issue, I am behind a pfSense, however that was never a problem with ESPHome or HA. I can only imagine, that some of the links are in a blocklist (but then, why and how?).
Thanks for any ideas or advice.
Which version of ESPHome has the issue?
2025.4.1, 2025.2.2
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2025.5.1
What platform are you using?
ESP32
Board
esp32dev
Component causing the issue
no component, whole device affected
YAML Config
no YAML, because YAML seems not important. Affected YAMLs worked for years.Anything in the logs that might be useful for us?
Additional information
The text was updated successfully, but these errors were encountered: