What is up with all these breaking changes?

Configuration
81

I can guarantee that at some point between then and Xmas your comprehension of the ENC analogy will be complete.

82

you give it till xmas, i think it will become more apparent long before that.
But that discussion is for another time and place

1 Like
83

BACK ON TOPIC

One observation that has occurred to me is that maybe bundling components with the core product and putting both things on the same release schedule is part of the problem. If instead one were to nail down an API with a fixed roadmap between the two, then the core could be released and upgraded independently from the components. In this way, if I just had a component which needed a new version, I could download just the component without going through all of the other breaking changes brought along with everything else. HA projects like IOBroker work with this model and upgrading is a breeze.

5 Likes
84

Luma, i would ask in the dev discord channels to see if this is not where they are trying to head to.

85

You can use LDAP for authentication but there is authorization system to restrict user access. Everyone is a full admin.

People forget there are 3 parts to AAA authentication.

  1. Authentication - Who you are.
  2. Authorization - What you can do.
  3. Accounting - What you did.

Any system is incomplete without all 3 parts.

2 Likes
86

Itā€™s a tradeoff right? You either update each week/month and have one component break (5% of your configuration) or you update once a year and have dozens of components break (50% of your configuration).

The latter will be much more effort.

87

Yeah I always wondered about that. Itā€™s odd that it all goes into one codebase when individual components are large enough to be versioned themselves.

88

Itā€™s funny, as much as I hate breaking changes, Iā€™m always disappointed when thereā€™s a release without any. I think ā€œaww man, all I have to do is click update?ā€ XD

89

Before version 1.0, the software is still unfinished and thus breaking changes are expected. If you donā€™t want breaking changes in your system donā€™t update, or donā€™t use home assistant.

My personal solution to this is that I do not update unless I want a new feature that was recently added. When I update, I check the logs to see if there are any breaking changes. If there are, I fix them. If I fail to fix them (due to some development issue that needs to be fixed in the codebase) I just downgrade my version to the old one. Iā€™ve been doing this since v0.5x something and it has worked for me so far :slight_smile:

1 Like
90

You can do thatā€¦ Just add it as a custom component. I do this all the time when I donā€™t feel like dealing with changes. Had to do it with harmony recently.

2 Likes
91

I can`t live with or without itā€¦

What i don`t like is that component information is not updated. Deprecated options are still listedā€¦

92

Please provide examples (so they can be corrected).

Part of the Pull Request process includes updating the documentation. So if youā€™ve found examples of documentation that has not been updated, it needs to be corrected. BTW, anyone with a GitHub account can update the documentation.

1 Like
93

I just downgrade my version to the old one.

Can you tell me how you downgrade please?

Iā€™m having issues that have appeared since 0.87, and would like to go back to it to see if 0.88 was causing the issue.

Thanks

94

Depends on how you installed homeassistant.
For me (now), i just replace the version number in a config file, do ā€œdocker-compose up -dā€ and wait.

If you installed it with a venv, you could do pip install homeassistant==0.87.2 (After you activated the vevn)

If you are using anything else, i have no idea how to downgrade

95

thanks, Iā€™m using Hassio - Iā€™ve found this method:

https://blog.dustinrue.com/2017/12/downgrading-hassio/

Iā€™ve not tried it get as i donā€™t have the SSH addon:

OK got SSH addon installed and I get this:

# curl -d '{"version": "0.87.1"}' http://hassio/homeassistant/update
/bin/ash: curl: not found

sigh

EDIT: turns out that I needed to do ha update --version=0.87.1 from SSH, the whole curl thing was a red herring! :smiley:

1 Like
96

Trust me, we donā€™t forget them. We have very basic authorization, at least owner has different permission than rest. Full authorization function is under development. The reason behind the Context is to enabling audit.

1 Like
97

Just as a FYI, your ability to do this is going to become a lot more difficultā€¦

98

Glad you made it :slight_smile:

@DavidFW1960 sounds mysterious. Do i understand correctly there are plans to change behaviour of custom versions of official components?

Iā€™m not using any (i did, but this was a bad ideaā€¦) but i am curious

99

You can read about the changes here:

100

It depends on how you installed home assistant into your system. I am using using the docker container so I just change which image to run in a docker-compose file. I donā€™t know how to do this with hass.io if that is what you are running on your system.