Esphome 2023.5.0 pyparsing version incompatible

[miGii]

The problem

When I compile (on 2023.5.0) any device's code I got following error in logs: ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. Successfully installed cachecontrol-0.12.11 certifi-2023.5.7 charset-normalizer-3.1.0 click-8.1.3 colorama-0.4.6 contextlib2-21.6.0 future-0.18.3 idf-component-manager-1.2.2 idna-3.4 lockfile-0.12.2 msgpack-1.0.5 packaging-23.1 pyparsing-2.3.1 pyyaml-6.0 requests-2.30.0 requests-file-1.5.1 requests-toolbelt-1.0.0 schema-0.7.5 six-1.16.0 tqdm-4.65.0 urllib3-2.0.2 esphome 2023.5.0 requires pyparsing>=3.0, but you have pyparsing 2.3.1 which is incompatible.

Despite this, the code compiles and installs correctly.

Which version of ESPHome has the issue?

2023.5.0

What type of installation are you using?

Home Assistant Add-on

Which version of Home Assistant has the issue?

2023.5.3

What platform are you using?

ESP32

Board

No response

Component causing the issue

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[selfmade01]

I have had same Problem. (with ESP32-S2) i get that the first time when i updated my esphome version to 2023.5.0 after that i updated HA-Version too to 2023.5.3

when I compiled the same esphome code the second time, the error was gone (after I updated my HA) I'm not sure if that actually fixed the problem. It's possible that if I compile another ESP32-S2 I'll get the error again.

[PaleoW]

This seems to happen when using the ESP-IDF platform instead or Arduino.

Installing ESP-IDF's Python dependencies
Collecting pyparsing<2.4.0,>=2.0.3
  Using cached pyparsing-2.3.1-py2.py3-none-any.whl (61 kB)
Installing collected packages: pyparsing
  Attempting uninstall: pyparsing
    Found existing installation: pyparsing 3.0.9
    Uninstalling pyparsing-3.0.9:
      Successfully uninstalled pyparsing-3.0.9
Successfully installed pyparsing-2.3.1
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
esphome 2023.5.0 requires pyparsing>=3.0, but you have pyparsing 2.3.1 which is incompatible.

[ssieb]

Yes, it is specific to IDF:

Installing ESP-IDF's Python dependencies
Collecting pyparsing<2.4.0,>=2.0.3

[tplas]

I am seeing same issue in the log, and only occurs when updating device that uses ESP-IDF. Which is required (or highly recommended) for Bluetooth Proxy ESPHome devices.

I saw it on my first update of a BT Proxy device, & haven't done any more since. That one is an M5Stack AtomU device. I have not updated my other BT Proxy devices-- one more M5Stack AtomU, and two GL-S10 devices from GL-iNet.

The one unit I did update displayed the warning message, then continued with compile / install, and seems to be operational after it rebooted. (But I'm not going to update any more, esp. the GL-S10 units, until I hear about resolution.)

[twister36]

same issue for me when trying to push the latest version of ESPHome to my devices

[liamlain]

i got the error when updating:

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. esphome 2023.5.1 requires pyparsing>=3.0, but you have pyparsing 2.3.1 which is incompatible.

[Pyromane]

rocessing esp32-bluetooth-proxy-455014 (board: esp32dev; framework: espidf; platform: platformio/espressif32@5.3.0)
--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
 - framework-espidf @ 3.40404.0 (4.4.4) 
 - tool-cmake @ 3.16.4 
 - tool-ninja @ 1.7.1 
 - toolchain-esp32ulp @ 2.35.0-20220830 
 - toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5

.....

  Attempting uninstall: pyparsing
    Found existing installation: pyparsing 3.0.9
    Uninstalling pyparsing-3.0.9:
      Successfully uninstalled pyparsing-3.0.9
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
esphome 2023.5.1 requires pyparsing>=3.0, but you have pyparsing 2.3.1 which is incompatible.
Successfully installed cachecontrol-0.12.11 certifi-2023.5.7 charset-normalizer-3.1.0 click-8.1.3 colorama-0.4.6 contextlib2-21.6.0 future-0.18.3 idf-component-manager-1.2.2 idna-3.4 lockfile-0.12.2 msgpack-1.0.5 packaging-23.1 pyparsing-2.3.1 pyyaml-6.0 requests-2.30.0 requests-file-1.5.1 requests-toolbelt-1.0.0 schema-0.7.5 six-1.16.0 tqdm-4.65.0 urllib3-2.0.2

[janprive]

Same here with my bluetooth proxy!

[TRusselo]

Same here for updating my bt proxy

[TaylorTWBrown]

Same issue. Using ESP-IDF framework with the bluetooth-proxy functionality. Running ESPHome 2023.5.2

[Tamsy]

Exactly the same here with ESP-IDF:

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
esphome 2023.5.2 requires pyparsing>=3.0, but you have pyparsing 2.3.1 which is incompatible.

[KosieKramer]

I had the same issue, but after cleaning the build files, the build worked without error.

[KosieKramer]

Nope... seems the error is back this morning after ESPHome update to 2023.5.3

[lysiong]

same here as well whichever there is an ESPHome update on ESPHome 2023.5.0, 2023.5.1, 2023.5.2, 2023.5.3 I'm using ESP32 240MHz, 320KB RAM, 4MB Flash

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. esphome 2023.5.3 requires pyparsing>=3.0, but you have pyparsing 2.3.1 which is incompatible.

But if reinstall the ESPHome firmware for 2nd time, the error will disappear.

[tplas]

I'm afraid if you just run re-install, it doesn't do full compile (just sends already-compiled firmware to the device), so it doesn't go thru the compilation dependency checks.

I also tried the suggestion to Clean Build Files before recompile (when I updated to 2023.5.3), but still got same warning during the build.

But once again, even though it issued that warning, the compile process proceeded to completion, and successfully sent the new firmware to the device, and the device appears fully operational. So am not sure of impact of this warning message.

Nevertheless, I'm still not updating my other BT Proxy devices until we learn what this is all about.

[Meli73]

still get this Error, too. But seams to run, anyway

[rleongcs]

Same here even with 2023.5.3.

[KosieKramer]

Error is still present in 2023.5.4.

[sippeeey]

Same here with 2023.5.4 by Update my M5 Stack atom-bluetooth-proxy.

[DAveShillito]

Just to add another voice here. I too am seeing the issue, 2023.5.4. Updating a BT proxy using Wemos D1 Mini ESP32.

[IamMattM]

Same here for me with ESPHOME v 2023.5.4

[micky-bamboleo]

Same here (atom bt proxy, ESPHome 2023.5.4)

[distante]

Same ESP32 with BT proxy, ESPHome 2023.5.4

[brunopiras]

Same ESP32 BLE, ESPHome 2023.5.4

[Tamsy]

Unfortunately with esp32dev, BT proxy, esp-idf, ESPHome 2023.5.5 still:

  Attempting uninstall: pyparsing
    Found existing installation: pyparsing 3.0.9
    Uninstalling pyparsing-3.0.9:
      Successfully uninstalled pyparsing-3.0.9
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
Successfully installed cachecontrol-0.12.11 certifi-2023.5.7 charset-normalizer-3.1.0 click-8.1.3 colorama-0.4.6 contextlib2-21.6.0 future-0.18.3 idf-component-manager-1.2.3 idna-3.4 lockfile-0.12.2 msgpack-1.0.5 packaging-23.1 pyparsing-2.3.1 pyyaml-6.0 requests-2.31.0 requests-file-1.5.1 requests-toolbelt-1.0.0 schema-0.7.5 six-1.16.0 tqdm-4.65.0 urllib3-1.26.16
esphome 2023.5.5 requires pyparsing>=3.0, but you have pyparsing 2.3.1 which is incompatible.

[natodd]

Same here. Just installed the latest and still getting it. ESP32 BLE, ESPHome 2023.5.5

[horve000]

Same problem here.

[emilianogetino]

Same problem here.

[napalmz]

Same here, sadly.

[tplas]

Wow, the issue seems to have been resolved with my devices.

I have installed Home Assistant Core 2023.5.4 and ESPHome 2023.5.5

I have four ESP32 BT Proxy devices with ESP-IDF framework, in two different hardware types: GL-S10 from GLiNet, and AtomU from M5Stack.

None of them issued the warning message during most recent build; they had completely clean install when I updated them for newest version (2023.5.5) of ESPHome.

I notice that the release notes for ESPHome 2023.5.5 mention "not breaking yaml parsing". So hopefully this was it?

[adekloet]

On 30-05-2023 16:45, Tim Plas wrote:

Wow, the issue seems to have been resolved with my devices.

I have installed Home Assistant Core 2023.5.4 and ESPHome 2023.5.5

I have four ESP32 BT Proxy devices with ESP-IDF framework, in two different hardware types: GL-S10 from GLiNet, and AtomU from M5Stack.

None of them issued the warning message during most recent build; they had completely clean install when I updated them for newest version (2023.5.5) of ESPHome.

I notice that the release notes for ESPHome 2023.5.5 mention "not breaking yaml parsing". So hopefully this was it?

-- Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. You are receiving this because you are subscribed to this thread.Message ID: @.***>

Links:

[1] https://github.com/esphome/issues/issues/4517#issuecomment-1568566512 [2] https://github.com/notifications/unsubscribe-auth/AOLE72GPUG7CQF2MOOAN7FTXIYBZTANCNFSM6AAAAAAYE6ASW4

I still see the error on esphome 5.5 on HASSOS RPI4

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. esphome 2023.5.5 requires pyparsing>=3.0, but you have pyparsing 2.3.1 which is incompatible. Successfully installed cachecontrol-0.12.11 certifi-2023.5.7 charset-normalizer-3.1.0 click-8.1.3 colorama-0.4.6 contextlib2-21.6.0 future-0.18.3 idf-component-manager-1.2.3 idna-3.4 lockfile-0.12.2 msgpack-1.0.5 packaging-23.1 pyparsing-2.3.1 pyyaml-6.0 requests-2.31.0 requests-file-1.5.1 requests-toolbelt-1.0.0 schema-0.7.5 six-1.16.0 tqdm-4.65.0 urllib3-1.26.16 Reading CMake configuration...

[scoulondre]

Same here, esp-idf requires pyparsing<2.4.0,>=2.0.3 and esphome requires pyparsing>=3.0 We are stuck with this conflict

[adekloet]

Oke what I did is get esphome 5.5 installed. Clean the build files for the device your upgrading and then install. I had no error after that. The "clean build files" removes all previous cached files and does a full new download/cmake/compile/link and it seemed to work. Give it a try. -------- Original message --------From: Stephane Coulondre @.> Date: 05/06/2023 21:14 (GMT+01:00) To: esphome/issues @.> Cc: Alex de Kloet @.>, Manual @.> Subject: Re: [esphome/issues] Esphome 2023.5.0 pyparsing version incompatible (Issue #4517) Same here, esp-idf requires pyparsing<2.4.0,>=2.0.3 and esphome requires pyparsing>=3.0 We are stuck with this conflict

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

[scoulondre]

Finally, cleaning everything, including all caches (under Debian: .esphome, ~/.platformio, venv), then installing again everything still shows the pyparsing problem, but it does not stop the process anymore.

[tplas]

Mine are all clean now.

I am running HA Core 2023.5.4, ESPHome 2023.5.5, HA OS 10.2, and HA Supervisor 2023.04.1

I performed "Clean build files" --but only for one of the devices; does that operation clear them for all when you do that?

I then performed Install for each of my ESP-IDF ESPHome devices -- All are BT Proxy devices: two are GL-S10 units from GLiNet, and two are AtomU units from M5Stack. All of them compiled cleanly with no errors (other than usual pin-usage warning on the GL-S10's).

All four of my devices compiled and installed / uploaded just fine, and all are running fine.

[smartmatic]

Same here, installed my first M5 Atom Lite as ESP Bluetooth Proxy and get this error in the logs. My system is: HA 2023.6.2 ESPHome 2023.5.5

[BluThunder2k]

Same here on ESPHome 5.x and 6.0. Affects my bluetooth proxies as well.

[HaraldGithub]

I've had the same problem with one of my M5Stack Bluetooth proxy: But find a solution: KLICK "Clean Build Files" in ESPhome-main-menue for each devices. After that the problem doesn't occur any longer during the update process.

[crzykidd]

KLICK "Clean Build Files" in ESPhome-main-menue for each devices.

This solved it for me as well. Thanks for the share!

[KitHubek]

newest update to 2023.6.4 and error still exsist (cleaned built files before update)

INFO ESPHome 2023.6.4
INFO Reading configuration /config/esphome/esp32-bluetooth-proxy.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing esp32-bluetooth-proxy (board: esp32dev; framework: espidf; platform: platformio/espressif32@5.3.0)
--------------------------------------------------------------------------------
Library Manager: Installing esphome/noise-c @ 0.1.4
INFO Installing esphome/noise-c @ 0.1.4
Unpacking  [####################################]  100%
Library Manager: noise-c@0.1.4 has been installed!
INFO noise-c@0.1.4 has been installed!
Library Manager: Resolving dependencies...
INFO Resolving dependencies...
Library Manager: Installing esphome/libsodium @ 1.10018.1
INFO Installing esphome/libsodium @ 1.10018.1
Unpacking  [####################################]  100%
Library Manager: libsodium@1.10018.1 has been installed!
INFO libsodium@1.10018.1 has been installed!
Library Manager: Installing esphome/Improv @ 1.2.3
INFO Installing esphome/Improv @ 1.2.3
Unpacking  [####################################]  100%
Library Manager: Improv@1.2.3 has been installed!
INFO Improv@1.2.3 has been installed!
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
 - framework-espidf @ 3.40404.0 (4.4.4) 
 - tool-cmake @ 3.16.4 
 - tool-ninja @ 1.7.1 
 - toolchain-esp32ulp @ 2.35.0-20220830 
 - toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5
Installing ESP-IDF's Python dependencies
Collecting future>=0.15.2
  Downloading future-0.18.3.tar.gz (840 kB)
Collecting pyparsing<2.4.0,>=2.0.3
  Downloading pyparsing-2.3.1-py2.py3-none-any.whl (61 kB)
Collecting idf-component-manager~=1.0
  Downloading idf_component_manager-1.3.1-py2.py3-none-any.whl (134 kB)
Collecting tqdm<5
  Downloading tqdm-4.65.0-py3-none-any.whl (77 kB)
Collecting schema
  Downloading schema-0.7.5-py2.py3-none-any.whl (17 kB)
Collecting six
  Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting requests<3
  Downloading requests-2.31.0-py3-none-any.whl (62 kB)
Collecting pyyaml>5.2
  Downloading PyYAML-6.0-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (661 kB)
Collecting cachecontrol[filecache]>0.12.6
  Downloading cachecontrol-0.13.1-py3-none-any.whl (22 kB)
Collecting click
  Downloading click-8.1.3-py3-none-any.whl (96 kB)
Collecting packaging
  Downloading packaging-23.1-py3-none-any.whl (48 kB)
Collecting urllib3<2
  Downloading urllib3-1.26.16-py2.py3-none-any.whl (143 kB)
Collecting contextlib2>0.6.0
  Downloading contextlib2-21.6.0-py2.py3-none-any.whl (13 kB)
Collecting colorama
  Downloading colorama-0.4.6-py2.py3-none-any.whl (25 kB)
Collecting requests-toolbelt
  Downloading requests_toolbelt-1.0.0-py2.py3-none-any.whl (54 kB)
Collecting requests-file
  Downloading requests_file-1.5.1-py2.py3-none-any.whl (3.7 kB)
Collecting msgpack>=0.5.2
  Downloading msgpack-1.0.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (322 kB)
Collecting filelock>=3.8.0
  Downloading filelock-3.12.2-py3-none-any.whl (10 kB)
Collecting idna<4,>=2.5
  Downloading idna-3.4-py3-none-any.whl (61 kB)
Collecting charset-normalizer<4,>=2
  Downloading charset_normalizer-3.1.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (199 kB)
Collecting certifi>=2017.4.17
  Downloading certifi-2023.5.7-py3-none-any.whl (156 kB)
Building wheels for collected packages: future
  Building wheel for future (setup.py): started
  Building wheel for future (setup.py): finished with status 'done'
  Created wheel for future: filename=future-0.18.3-py3-none-any.whl size=492025 sha256=5d871d979d67ccf7d03f58922967ee065776894472db8ff567c4257307d427c7
  Stored in directory: /tmp/pip-ephem-wheel-cache-it23e93s/wheels/bf/5d/6a/2e53874f7ec4e2bede522385439531fafec8fafe005b5c3d1b
Successfully built future
Installing collected packages: urllib3, idna, charset-normalizer, certifi, requests, msgpack, six, filelock, contextlib2, cachecontrol, tqdm, schema, requests-toolbelt, requests-file, pyyaml, packaging, colorama, click, pyparsing, idf-component-manager, future
  Attempting uninstall: urllib3
    Found existing installation: urllib3 1.26.16
    Uninstalling urllib3-1.26.16:
      Successfully uninstalled urllib3-1.26.16
  Attempting uninstall: idna
    Found existing installation: idna 3.4
    Uninstalling idna-3.4:
      Successfully uninstalled idna-3.4
  Attempting uninstall: charset-normalizer
    Found existing installation: charset-normalizer 3.1.0
    Uninstalling charset-normalizer-3.1.0:
      Successfully uninstalled charset-normalizer-3.1.0
  Attempting uninstall: certifi
    Found existing installation: certifi 2023.5.7
    Uninstalling certifi-2023.5.7:
      Successfully uninstalled certifi-2023.5.7
  Attempting uninstall: requests
    Found existing installation: requests 2.31.0
    Uninstalling requests-2.31.0:
      Successfully uninstalled requests-2.31.0
  Attempting uninstall: six
    Found existing installation: six 1.16.0
    Not uninstalling six at /usr/lib/python3/dist-packages, outside environment /usr
    Can't uninstall 'six'. No files were found to uninstall.
  Attempting uninstall: pyyaml
    Found existing installation: PyYAML 6.0
    Uninstalling PyYAML-6.0:
      Successfully uninstalled PyYAML-6.0
  Attempting uninstall: packaging
    Found existing installation: packaging 23.1
    Uninstalling packaging-23.1:
      Successfully uninstalled packaging-23.1
  Attempting uninstall: colorama
    Found existing installation: colorama 0.4.6
    Uninstalling colorama-0.4.6:
      Successfully uninstalled colorama-0.4.6
  Attempting uninstall: click
    Found existing installation: click 8.1.3
    Uninstalling click-8.1.3:
      Successfully uninstalled click-8.1.3
  Attempting uninstall: pyparsing
    Found existing installation: pyparsing 3.1.0
    Uninstalling pyparsing-3.1.0:
      Successfully uninstalled pyparsing-3.1.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
esphome 2023.6.4 requires pyparsing>=3.0, but you have pyparsing 2.3.1 which is incompatible.
Successfully installed cachecontrol-0.13.1 certifi-2023.5.7 charset-normalizer-3.1.0 click-8.1.3 colorama-0.4.6 contextlib2-21.6.0 filelock-3.12.2 future-0.18.3 idf-component-manager-1.3.1 idna-3.4 msgpack-1.0.5 packaging-23.1 pyparsing-2.3.1 pyyaml-6.0 requests-2.31.0 requests-file-1.5.1 requests-toolbelt-1.0.0 schema-0.7.5 six-1.16.0 tqdm-4.65.0 urllib3-1.26.16
Reading CMake configuration...
Generating assembly for certificate bundle...
Dependency Graph
|-- noise-c @ 0.1.4
|-- Improv @ 1.2.3
Compiling /data/esp32-bluetooth-proxy/.pioenvs/esp32-bluetooth-proxy/src/esphome/components/api/api_connection.o

[HaraldGithub]

Same here. I reinstalled my proxy and now, I've no error on this proxies. But know, I've this error on the other one, so I'll reinstall this also. I think it's a bug on ESPHome-side, since HA is updated to python 3.11 with 2023.4.0-Update.

[rleongcs]

Same here when updating to 2023.6.4 even with clean build. Earlier versions with clean build could not see the error already.

[lysiong]

I notice that it only happen on framework esp-idf, but on framework arduino working fine. I mean the compiler.

[HaraldGithub]

@lysiong How could I select between this different compilers?

[regystro]

@lysiong How could I select between this different compilers?

https://esphome.io/search.html?q=esp-idf

[rleongcs]

@lysiong How could I select between this different compilers?

@HaraldGithub You can change the compilers under "type". Having said that, we need esp-idf for bluetooth proxy. 😞

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

[lysiong]

@lysiong How could I select between this different compilers?

when you set the ESP32 as below, framework type set to arduino

esp32:
  board: esp32dev
  framework:
    type: arduino

[lysiong]

@rleongcs actually got different between arduino & esp-idf? previously I did use arduino, then later found up esp-idf also can compile.

[rleongcs]

@rleongcs actually got different between arduino & esp-idf? previously I did use arduino, then later found up esp-idf also can compile.

I believed there are but not totally sure the differences. I was also not aware before till I am using bluetooth proxy function. The bluetooth proxy documention says it needs to use esp-idf.

[nepozs]

I do not now why #4670 is closed, as it is new problem for me, and I'm upgrading ESPHome every month (or even every release). More interesting I've uninstalled ESPHome and installed addon again, but error persist…

Successfully installed cachecontrol-0.13.1 certifi-2023.5.7 charset-normalizer-3.2.0 click-8.1.5 colorama-0.4.6 contextlib2-21.6.0 filelock-3.12.2 future-0.18.3 idf-component-manager-1.3.2 idna-3.4 msgpack-1.0.5 packaging-23.1 pyparsing-2.3.1 pyyaml-6.0 requests-2.31.0 requests-file-1.5.1 requests-toolbelt-1.0.0 schema-0.7.5 six-1.16.0 tqdm-4.65.0 urllib3-1.26.16
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
esphome 2023.6.5 requires click==8.1.3, but you have click 8.1.5 which is incompatible.
esphome 2023.6.5 requires pyparsing>=3.0, but you have pyparsing 2.3.1 which is incompatible.
Reading CMake configuration...
Generating assembly for certificate bundle...
No dependencies

Compilation was possible only after fresh install, BUT really imposiible after upgrade from 2023.6.4 to 2023.6.5