search

codingcyclist / ha_strava

Pipe your Activity Data from Strava directly into Home Assistant
MIT License
76 stars 29 forks source link

ha_strava gives error after upgrade to Home Assistant 2022.3.1 #44

Open jan-gerard opened 2 years ago

jan-gerard commented 2 years ago

I get the following errors after upgrading to Home Assistant 2022.3.1: 2022-03-06 00:15:25 ERROR (SyncWorker_4) [homeassistant.util.package] Unable to install package aiohttp==3.6.1: ERROR: Cannot install aiohttp==3.6.1 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 2022-03-06 00:15:33 ERROR (SyncWorker_1) [homeassistant.util.package] Unable to install package aiohttp==3.6.1: ERROR: Cannot install aiohttp==3.6.1 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 2022-03-06 00:15:42 ERROR (SyncWorker_6) [homeassistant.util.package] Unable to install package aiohttp==3.6.1: ERROR: Cannot install aiohttp==3.6.1 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 2022-03-06 00:15:42 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration ha_strava: Requirements for ha_strava not found: ['aiohttp==3.6.1']. Maybe (prabably) because of this, HA_strava is not working anymore. Might there be other integrations that require a different version of aiohttp? And haw could I identify them, if that is the problem?

thoemmi commented 2 years ago

In manifest.json you have to remove aiohttp from the requirements (and change voluptuous to greater or equal):

---  "requirements": ["aiohttp==3.6.1", "voluptuous==0.11.7"],
+++  "requirements": ["voluptuous>=0.11.7"],
woolf0007 commented 2 years ago

After in HACS install, I cant see Strava in the integration. Can you copy here the good manifest.json with the good version and requirements...?! Thx

thoemmi commented 2 years ago

My manifest.json looks like this:

{
  "domain": "ha_strava",
  "name": "Strava Home Assistant",
  "config_flow": true,
  "documentation": "https://github.com/codingcyclist/ha_strava",
  "requirements": ["voluptuous>=0.11.7"],
  "dependencies": [],
  "codeowners": ["@codingcyclist"],
  "version": "0.1.1"
}

To get _hastrava from this repository running, you also have to apply some more changes, see PR #36

jan-gerard commented 2 years ago

To get _hastrava from this repository running, you also have to apply some more changes, see PR #36

Sorry, it's not clear to me what other changes I should carry out. The link points to a core HA file, I think, which is not accessible on my HASS OS installation. I can only get to files in the /config directory.

woolf0007 commented 2 years ago

My manifest.json looks like this:

{
  "domain": "ha_strava",
  "name": "Strava Home Assistant",
  "config_flow": true,
  "documentation": "https://github.com/codingcyclist/ha_strava",
  "requirements": ["voluptuous>=0.11.7"],
  "dependencies": [],
  "codeowners": ["@codingcyclist"],
  "version": "0.1.1"
}

To get _hastrava from this repository running, you also have to apply some more changes, see PR #36

Thank you, but as you said, the following problem: "configuration process cannot be loaded" for me it is not clear, what should i do... I have more error, I gave up: "Your Home Assistant Instance does not seem to have a public URL. The Strava Home Assistant integration requires a public URL"

thoemmi commented 2 years ago

The link points to a core HA file, I think,

@jan-gerard No, the patched files are part of the custom _hastrava component.

thoemmi commented 2 years ago

I have more error, I gave up: "Your Home Assistant Instance does not seem to have a public URL. The Strava Home Assistant integration requires a public URL"

The readme says explicitly:

First, set up remote access to your Home Assistant Installation

To use the Strava Home Assitant integration, your Home Assistant Instance must be accessible from an External URL (i.e. Remote Access). Without remote access, the integration won't be able to pull data from Strava. To learn how to set up Remote Access for Home Assistant, please visit the Official Documentation

woolf0007 commented 2 years ago

I solved it, it was very boring to move from error to error. I had 3 days of searching for it. thx guys..

Fleshi1981 commented 2 years ago

Thanks for the fix :)

hudsonbrendon commented 2 years ago

@thoemmi I made all the changes you mentioned and the information is coming like this, do you know what it is about? image

thoemmi commented 2 years ago

@hudsonbrendon Sorry, but I don't know 🤷‍♂️

maobuz commented 2 years ago

Please help me, i have this error when i put the link for the repository on hacs
Repository structure for 0.1.1 is not compliant image

System Health

version core-2022.3.5
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.9.9
os_name Linux
os_version 5.10.92-v8
arch aarch64
timezone Europe/Rome
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4632 Installed Version | 1.23.0 Stage | running Available Repositories | 1011 Downloaded Repositories | 26
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 7.4 -- | -- update_channel | stable supervisor_version | supervisor-2022.03.4 docker_version | 20.10.9 disk_total | 228.5 GB disk_used | 10.6 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Duck DNS (1.14.0), Let's Encrypt (4.12.0), Samba share (9.5.1), Terminal & SSH (9.3.0), Mosquitto broker (6.0.1), Zigbee2mqtt (1.24.0-1), Home Assistant Google Drive Backup (0.105.2), File editor (5.3.3), RPC Shutdown (2.2), FTP (4.5.0)
Lovelace dashboards | 1 -- | -- resources | 13 views | 5 mode | storage
woolf0007 commented 2 years ago

Please help me, i have this error when i put the link for the repository on hacs Repository structure for 0.1.1 is not compliant image

System Health

version core-2022.3.5 installation_type Home Assistant OS dev false hassio true docker true user root virtualenv false python_version 3.9.9 os_name Linux os_version 5.10.92-v8 arch aarch64 timezone Europe/Rome Home Assistant Community Store Home Assistant Cloud Home Assistant Supervisor Lovelace

Use this: madmic1314/ha_strava

maobuz commented 2 years ago

madmic1314/ha_strava Thanks, but i have same problem as the user : @thoemmi

image

any idea ?

maobuz commented 2 years ago

@thoemmi @woolf0007 Fixed after last restart! image

bjornsivertsen commented 2 years ago

Would anyone be willing to branch this repo and implement the fixes?

I have implemented the manifest and hass.const.HTTP_* changes manually as you others, but it would be great to have a space where pull requests actually gets merged. So fixes are automatically applied through HACS.

Current reliability of the integration is on the lower end and the issue that @maobuz is experiencing happens pretty often unprovoked.

Perhaps you are up for the task @thoemmi ?

Or even better @codingcyclist could you allow others to merge?

thoemmi commented 2 years ago

Perhaps you are up for the task @thoemmi ?

I've already thought about it, but then decided against it. I don't want to be asked for support :wink:

However, @madmic1314 said in #37 , that he's going to maintain a fork with fixes applied: https://github.com/madmic1314/ha_strava

maobuz commented 2 years ago

Qualcuno sarebbe disposto a ramificare questo repository e implementare le correzioni?

Ho implementato manualmente le modifiche manifest e hass.const.HTTP_* come voi altri, ma sarebbe fantastico avere uno spazio in cui le richieste pull vengano effettivamente unite. Quindi le correzioni vengono applicate automaticamente tramite HACS.

L'attuale affidabilità dell'integrazione è nella fascia più bassa e il problema che @maobuz sta riscontrando accade abbastanza spesso non provocato.

Forse sei pronto per il compito @thoemmi ?

O ancora meglio @codingcyclist potresti consentire ad altri di unire?

another time after reboot ... IS BACK THIS PROBLEM.. :((( image

maobuz commented 2 years ago

NEWS? :(

madmic1314 commented 2 years ago

Perhaps you are up for the task @thoemmi ?

I've already thought about it, but then decided against it. I don't want to be asked for support 😉

However, @madmic1314 said in #37 , that he's going to maintain a fork with fixes applied: https://github.com/madmic1314/ha_strava

I've forked this, but for the life of me couldn't get HACS to work properly. The files were identical to this repo, but HACS wouldn't see it. I asked for help in the HACS discord and was told it was an issue my end, but no real help. Couldn't figure it out - been busy with other stuff, will try and pick up in a few days and see if a fresh start will work.

madmic1314 commented 2 years ago

Ok, the issue with HACS was with my HA instance having the old Strava integration still in the db. Before using my fork you must remove this one fully, HA integration + all sensors, then HACS integration, HACS repo. Reboot and then add mine: https://github.com/madmic1314/ha_strava

In the end I needed to edit the HACS db - but I'll not go into that here as it's a bit drastic!

maobuz commented 2 years ago

https://github.com/madmic1314/ha_strava image do not work :(

madmic1314 commented 2 years ago

I've released an update that should fix this - please test and if still an issue can you update this issue under my fork please? https://github.com/madmic1314/ha_strava/issues/3