Those command line tools can make long-term maintenance easier: you can check your git log for things you've added, do find-and-replace operations on your configuration, archive old setups as you retire devices or take them off line, etc. Having configuration as a file means you can use a bunch of tools - rsync, git versioning, diff, grep, sed, bulk rename, etc - that you simply cannot if it is stored in a database that's only meant to be accessed through the UI. I appreciate that these help UI users but it's made things harder for config-based, advanced users.Įdit: also, it's not clear to me as a user whether that hidden directory should be backed up or committed to source control. I know there's some great features coming out of them but recently I've had to restart several times and manually edit registries because I wanted to rename something and there were conflicts. storage directory has seriously complicated my configuration and usability within HA. I don't mean to harp on the UI-only configs yet again, but the. Saying that, I really like to have my configuration on configuration files so I can change them to exactly I want or backup the files, share it, etc. Remember that most of us use HA because we don't support cloud control over our things, we like to control our things.
#FORD IDS 108 RELEASE NOTES MANUAL#
Removing manual control via configurations files from poweruser to make it easier for 'non-tech' people is never a good idea. And, this has no impact who prefer the UI interface. What happens when HA is offline and I want to make a change? What if something caused by the SmartThings integration is causing an issue? Might not be the case now but I think that the ability to manage everything via terminal/config is the best approach. To add onto what -Smokin- was saying, easier troubleshooting and deployment. I'm having a small pity party about not being able to do everything in my IDE anymore, but I'll get over it. I'm sure people who use Unix on a regular basis are just more comfortable with configuration files rather than a black box UI This is why I use yaml mode for Lovelace still. I like being able to manually set/see everything. Config or front-end, not both, not even a little. Then you get to the front-end where you have to make a hard choice. The configuration is getting more and more fragmented. Manual setup through configuration.yaml is not available at this time. The SmartThings component is configured exclusively through the front-end. With the 0.87.0 release, the top comment on the Reddit post says: