new stable version 0.20.22j is broken

[mazzy89]

I've updated this morning to the new stable version 0.20.22j released. Unfortunately it is broken

Logger: homeassistant.setup
Source: setup.py:338 
First occurred: 9:59:07 AM (1 occurrences) 
Last logged: 9:59:07 AM

Unable to prepare setup for platform ramses_cc.sensor: Platform not found (cannot import name 'UnitOfTime' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)).

[DJBenson]

I have a different error - my config was working prior to this update;

Invalid config for [ramses_cc]: expected bool for dictionary value @ data['ramses_cc']['advanced_features']['message_events']. Got 'RP.* 04:'. (See /config/configuration.yaml, line 60).

[mazzy89]

which hassio version?

[DJBenson]

2023.1.1 - updated this morning (GMT).

[mazzy89]

interesting. I have updated to 2023.1.1 too and I do not have anymore that error. Further I do not see your error as well.

[DJBenson]

If I comment out the offending line the config checks out - but what changed is the question - that line has been in since I installed the package and I don't fully understand the implications of removing it.

[lloyda]

@DJBenson What version did you upgrade from?

[DJBenson]

@lloyda I can't say specifically but the last release - I follow the beta channel and update every time there is a new release.

[DJBenson]

Removing the package entirely, commenting out the above and reinstalling worked. Just not sure what the absence of that config line means to my install.

[lloyda]

@DJBenson It looks to me like the release today has been built on stable channel (0.20.22f)- if you were on latest beta (0.22.3) I think there are a number of changes that will not have been included in the release.

[DJBenson]

@lloyda yeah you're right - I have beta versions turned on in my install and did not spot that the latest fix was on the 0.20 codebase when I was on 0.22. I'm going to revert to the previous beta with my fixes from #56 until the repository catches up.

[lloyda]

@mazzy89

interesting. I have updated to 2023.1.1 too and I do not have anymore that error. Further I do not see your error as well.

Have you fixed your error? In which case you could close this issue.

[mazzy89]

yes I have fixed but please put in the release note that you need to have 2023.1 otherwise it won't work.

[mazzy89]

Release notes wired https://github.com/zxdavb/ramses_cc/releases/tag/0.21.40
going to close this. thanks all