-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HA Strava fails to startup with HA 2022.5 #45
Comments
Yep. This is because there is a breaking change of the time_changed event being removed. Unfortunately the fix is beyond my limited skills https://developers.home-assistant.io/blog/2022/04/20/saying-goodbye-to-event_time_changed/ |
thanks for the update and for taking the time to comment...beyond mine too |
Same for me. I also had to change the manifest file to use voluptuous 0.13.1 to get to this error otherwise it threw a voluptuous error instead. |
I’ve got it working again for me by hashing out the offending line. I do get a camera error on a HA restart, but as I do not use the camera, it’s not an issue for me. The line is I. The init_py file
|
@BertrumUK you superstar...I did look through a couple of files for the EVENT_TIME_CHANGED but didn't check this one...now hashed out and working perfectly again..I also don't use images |
Hashing out line 20 in camera.py clears the error on a restart
|
i am wondering if this strava is so cumbersome, i set up the connection between strava and fitbit and fitbit is basic integration in HA... What do you think? |
Does any level of information get lost in transit? |
I opened a PR (#46) to remove these two constants from both files. |
I have a working forked version of this here: https://github.com/craibo/ha_strava |
HA Strava was all working fine on 2022.4.7....testing on 2022.5 and getting the following error on start
Setup failed for custom integration ha_strava: Unable to import component: cannot import name 'EVENT_TIME_CHANGED' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)
Any idea what might be causing the issue...have had a look about and cant see anyone else reporting
The text was updated successfully, but these errors were encountered: