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

CONF_WEBHOOK_ID, EVENT_COMPONENT_LOADED, EVENT_CORE_CONFIG_UPDATE, EVENT_HOMEASSISTANT_START, #EVENT_TIME_CHANGED,

@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

) from hashlib import md5 #from homeassistant.const import EVENT_TIME_CHANGED

i commented a line 28 in init.py, line 20 in camera.py and works for me.

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?

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.
Once accepted, everything will work fine again. 👍

I have a working forked version of this here: https://github.com/craibo/ha_strava