HA no longer functions in “custom_components”

Third party integrations
1

I have been using the Cover integration for years: “home-assistant-custom-components-cover-rf-time-based.”

By copy all files in custom_components/cover_rf_time_based to your /custom_components/cover_rf_time_based/ directory.

I haven’t updated my HA in quite some time. Now, after the update, HA tells me:

The automation “Roller shutter - Position sync” (automation.rollladen_position_sync) has an unknown action: cover_rf_time_based.set_known_action.

In my case, this action/function sets the position.

What has changed in HA that it no longer merges? And is there a solution?

2

That repository was archived 2 years ago. You need to find another working solution. This is the first one I found from a quick search GitHub - duhow/hass-cover-time-based: Add a cover (time-based) to Home Assistant using switch or lights. there are others.

1 Like
3

I know. But it was working perfectly until a few days ago.

That’s why I’m asking whether anything has changed in HA with regard to integrations/functions.

4

And… You updated a few days ago?

Has anything changed is not at all a fair question I can guarantee the answer is yes if you haven’t updated in a while.

Will you find it. Probably not.

5

yes, that right. I was on 2925.08.xx

1 Like
6

Then you changed it and yes software updates. This is the same problem you decided to stop updates for rearing a worse version

Look I don’t mean t sound heartless. But software changes. And asking if ‘anything changed’ since with no frame of reference isn’t really a fair question. The answer will always be yes. (btw the reason I’m poking, you may not realize, most folks don’t. that question asked that way really pisses off most field support agents. It’s unanswerable… But they are usually too nice to call the user on ia d they redirect the question…) Frame a question with what worked before what stopped, and logs denoting what it’s throwing if it doesn’t work.

In your case you ‘customed’ a component for a reason. Totally valid. But it’s not guaranteed to work forever and you take in the risk of maintaining it now.

7

Hello Don_Maverick

Yes, most likely something changed years ago it it just caught up to you now.
IE the software you were using was archived, abandoned, and deprecated.
If you run a version of the OS from years ago, it might still work. Guessing, the python version is a likely candidate, or one of the calls in the custom software.

Interesting, I have not heard of that one.