Mess after update

Hello people i need your help. I’ve been working with home assitant for some time now and I’ve already automated quite a few things .
I do a lot of automation work through an RFXCom 433mhz transmitter and receiver.
Now I performed an update of Home assitant yesterday. To my great shock, I can no longer connect to all previously working components that were connected via the rfxcom. Does anyone know what the latest update means. I can’t imagine that a working installation is supposed to be messed up by an update.
I’ve added a picture of a small part of my connected rfxcom components.
should something else be set up i am doing something wrong.

HEEEEEEEEEEELLLLLLLPPP

0.113: Automations & Scripts, and even more performance!

Since 0.113 you need to move all rfxtrx devices to the rfxtrx domain.

To clarify: at this moment in time you have the rolluik_voordeur under the “cover” domain and this should go under “rfxtrx”

Look for an example: 0.113: Automations & Scripts, and even more performance!

hi frank thanks for your reply. now that I have adjusted this I see again but cannot operate them yet. and I do not recognize which is which. can I put something in the configuration file for this to make it easier to recognize?
I just don’t understand why they don’t do it now?
11

it looks like this now but can no longer serve them ?

The recognition part is a bit user unfriendly. Naming should be set in the UI, but the migration from yaml to UI has been somewhat underestimated. An attempt is made to re-introduce the “name” property for migration, hopefully this lands in 0.114 (cannot land in 0.113 patch because it re-introduces yaml keys).

W.r.t. them not working, you are looking at the devices. These are new, the should have entities under them. Are you missing these? Could you click on a device and check (and post a screenshot what you are looking at)?

See also following link, someone else is also reporting issues with covers. More info would be helpful to see whether this is a configuration or integration issue.

Hi rob, thanks for your help. I have it all back on track. I must honestly say that I think it is really strange that so many smart people get together to do an update after which a number of things no longer work. Very annoying

I’m not quite following. Do you have things that no longer work?
If you think there is an issue with the integration you should submit an issue on Github.

May I ask, if it did? :slight_smile:

You can see the status of the pull request as being closed, so no it didn’t. Unless someone puts in an effort here I don’t think this will be done.

There is however in the pipeline to add configuration through UI. That way you still have to rename, but you could add devices one by one and not having the burden of finding out which device is what. That will however not land in 0.114

1 Like