JaccoR / hass-entso-e

Integration for Home Assistant to fetch day ahead energy prices from European countries via ENTSO-e Transparency Platform
Apache License 2.0
185 stars 31 forks source link

"message":"Invalid handler specified #56

Closed KHWW closed 1 month ago

KHWW commented 2 years ago

Hi, Maybe it's a typical amateur error..... But... I get the following message and it won't install the integration.

"message":"Invalid handler specified

Foutmelding

JaccoR commented 2 years ago

I can not reproduce this. Does this happen when you add the integration in your settings? Maybe try a hard refresh (ctrl+r).

KHWW commented 2 years ago

Yes, when I add the integration in settings, I tried the intergration with HACS and also with manual install..

I did the hard refresh, but is still not working...

Logger: homeassistant.config_entries Source: config_entries.py:809 First occurred: 20:33:46 (1 occurrences) Last logged: 20:33:46

Error occurred loading configuration flow for integration entsoe: cannot import name 'XMLParsedAsHTMLWarning' from 'bs4.builder' (/usr/local/lib/python3.10/site-packages/bs4/builder/init.py)

JaccoR commented 2 years ago

What name are you using? Are you using any special characters?

KHWW commented 2 years ago

The name of? Then I can check.

JaccoR commented 2 years ago

I meant the name you give the integration, but since you can not set it up you never gave it a name of course. This seems to have to do with the entsoe library i'm using to call for entso-e data. I can not do anything about this atm.

You could try running you HA a different python version, if that is not too much of a hassle. I am running python 3.9.

MrTheoW commented 2 years ago

I currently running the latest version of HAOS and am seeing the same error come by. Is there any chance this custom integration will be updated so it will work with Python 3.10? I think there will be a lot of people getting this error if they stick to the updates of Home Assistant...

MrTheoW commented 2 years ago

Funny thing is that according to the file location (/usr/local/lib/python3.10/site-packages/bs4/builder/init.py) you could assume I would be running python 3.10 but once I navigate to that location only python3.9 exists.

image

sfstar commented 2 years ago

Weird that it is not working for you. By latest version do you refer to the 2022.10.5 release? (This is the version I am running and the integration is working at my end). Could you perhaps try to remove the integration files and force redownload the latest release from hacs again?

MrTheoW commented 2 years ago

Bit late to react but didn't see the notification.

HAOS version: 2022.11.1

Removed the component from HACS and installed the latest version from HACS (0.1.3).

Still gives the same error.

image

image

MrTheoW commented 2 years ago

If I can help you with anything please tell me.

JaccoR commented 1 year ago

Did you already find a solution for this?

Mipilo commented 1 year ago

Hi there,

I have the same problem as MrTheoW. Versions: HA: 2022.12.7 HACS: 1.29.0 ENTSO-E: 0.3.0 Python: 3.10.7

If I can help solving this issue please let me know!

MrTheoW commented 1 year ago

Did you already find a solution for this?

No, Unfortunately I do not know how to change the Python version in HA OS so it remains on version 3.9. And to be honest, It actually scares me a bit to do a manual update just before the holidays. If anything goes wrong and I wont be able to fix it in time I think I might sleep on the couch during the year change. 😅

TFhdKi95ae8L commented 1 year ago

Same "Config flow could not be loaded: {"message":"Invalid handler specified"}" error here. Installed via Hacs, tried adding the integration and the error mentioned above appears. Any advice on what to try?

sga-noud commented 1 year ago

Running HA Core 2023.7.3 and getting this same error after downloading 0.3.0 from HACS and trying to add the integration. Still no Python 3.10 support?

Roeland54 commented 1 month ago

Probably fixed in v0.5.0-beta2. Please test and provide feedback.

Roeland54 commented 1 month ago

v0.5.0 is released. The discussed issues should be solved. Please feel free to open a new issue if you feel this is needed.