ollo69 / ha-smartthinq-sensors

HomeAssistant custom integration for SmartThinQ LG devices configurable with Lovelace User Interface.
Apache License 2.0
1.03k stars 149 forks source link

Not working on 2024.4.0b0 #725

Closed TheFes closed 1 month ago

TheFes commented 3 months ago

Describe the bug Integration is not working and this message appears in the log

Logger: homeassistant.setup
Source: setup.py:273
First occurred: 19:40:01 (1 occurrences)
Last logged: 19:40:01

Setup failed for custom integration 'smartthinq_sensors': Requirements for smartthinq_sensors not found: ['pycountry<23.0.0,>=22.1.10'].

Expected behavior If applicable, a clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Environment details:

Output of HA logs Paste the relavant output of the HA log here.

Logger: homeassistant.setup
Source: setup.py:273
First occurred: 19:40:01 (1 occurrences)
Last logged: 19:40:01

Setup failed for custom integration 'smartthinq_sensors': Requirements for smartthinq_sensors not found: ['pycountry<23.0.0,>=22.1.10'].

Additional context Add any other context about the problem here.

ollo69 commented 3 months ago

Thanks for information, I suppose that some integration install other version. Do you have web radio installed? Anyway I will change requirement to be less restrictive

TheFes commented 3 months ago

Do you mean Radio Browser? I have that one installed.

I asked about pycountry in the beta channel on the HA Discord, the response was:

It’s pinned to the newer than 23 because there is a mistake in the older versions that brings in the whole setuptools stack

nickrout commented 3 months ago

Just to say "me too" - precisely the same issue. (Sorry if me too is frowned on)

luisiam commented 3 months ago

Thanks for information, I suppose that some integration install other version. Do you have web radio installed? Anyway I will change requirement to be less restrictive

I don't have that installed but I also have this issue.

pcartwright81 commented 3 months ago

This seems the same as issue 693 so I posed it last week there. I edited manifest.json at the location \\homeassistant.local\config\homeassistant\custom_components\smartthinq_sensors to say pycountry>23.0.0 and it seems to be working now.

nickrout commented 3 months ago

@pcartwright81 suggestion seems to work for me (thanks for that), but I don't feel confident enough about python modules to create a PR.

nickrout commented 3 months ago

Home assistant seems to have constrained pycountry to >23.12.11 two weeks ago.

https://github.com/home-assistant/core/commit/f3984a9d3ee94b92fd5a1a8902532d436ca52353

This custom integration constrains pycountry to pycountry<23.0.0,>=22.1.10

You can't be >23.12.11 and <23.0.0. I suspect that is the problem.

cloudbr34k84 commented 3 months ago

Just noticed this as well when I upgraded to 2024.4.0b0

sunny-ww commented 3 months ago

This seems the same as issue 693 so I posed it last week there. I edited manifest.json at the location \homeassistant.local\config\homeassistant\custom_components\smartthinq_sensors to say pycountry>23.0.0 and it seems to be working now.

the solution also worked perfectly for me

pjannink commented 3 months ago

Noticed too after installing 2024.4.0b0 on my testconfig.. Not using Webradio. I edited manifest.json as advised above but changing the line to "requirements": ["pycountry<23.0.0,>=22.1.10", "xmltodict>=0.13.0", "charset_normalizer>=3.2.0"], did not solve the issue. Please advise!

Update: issue fixed with line "requirements": ["pycountry>23.0.0", "xmltodict>=0.13.0", "charset_normalizer>=3.2.0"],

Awaiting your final fix for the production release of 2024.4 :-). Cheers!

smarthomeaf commented 3 months ago

Same issue on a clean 2024.4B0. Meaning nothing else installed other than smarthinq. Still works great on my 2024.3

def1149 commented 3 months ago

Confirmed: Issue fixed with line "requirements": ["pycountry>23.0.0", "xmltodict>=0.13.0", "charset_normalizer>=3.2.0"],

cloudbr34k84 commented 3 months ago

updated and fixed, and appears to be working again.

nelsonpita commented 3 months ago

This seems the same as issue 693 so I posed it last week there. I edited manifest.json at the location \homeassistant.local\config\homeassistant\custom_components\smartthinq_sensors to say pycountry>23.0.0 and it seems to be working now.

nelsonpita commented 3 months ago

Change to "requirements": ["pycountry>23.0.0,>=22.1.10", "xmltodict>=0.13.0", "charset_normalizer>=3.2.0"], , restart HA and now it is working.

nickrout commented 3 months ago

pycountry>23.0.0,>=22.1.10

Pointless. If it satisfies >23.0.0 it also satisfies >=22.1.10. The latter is unneeded

kimwowboom commented 3 months ago

The following integrations and platforms could not be set up:

smartthinq_sensors

Config-flow kon niet geladen worden: 500 Internal Server Error Server got itself in trouble

gershte commented 3 months ago

Still not loading

Logger: homeassistant.setup Source: setup.py:273 First occurred: 4:35:00 PM (1 occurrences) Last logged: 4:35:00 PM

Setup failed for custom integration 'smartthinq_sensors': Requirements for smartthinq_sensors not found: ['pycountry<23.0.0,>=22.1.10'].

ollo69 commented 3 months ago

@All,

issue should be fixed with last release v0.39.0, please report here if you still have problem.

kimwowboom commented 3 months ago

@ALL,

issue should be fixed with last release v0.39.0, please report here if you still have problem.

Update is not mentioned/pushed as update in HA/HACS store? It needs to be updated manually?

ollo69 commented 3 months ago

If you don't wait to wait the HACS auto refresh you need to force repository update selecting HACS integration

image

kimwowboom commented 3 months ago

Cool. That worked! Love you.

gershte commented 3 months ago

@ALL,

issue should be fixed with last release v0.39.0, please report here if you still have problem.

Confirmed. Problem solved. Thank you!

NukeThemTillTheyGlow commented 2 months ago

Update applied and works, thanks!

kfiducia commented 2 months ago

thanks for the quick patch on this!

ollo69 commented 1 month ago

Close this because fixed with last release