homeassistant-elasticsearch
homeassistant-elasticsearch copied to clipboard
Trouble migrating to the new setup process
Hi, Good job with this component! I use it in a container to embed Elastic stack in a Homeassistant project with Raspberry Pi. The docker-compose looks like the following:
homeassistant:
container_name: homeassistant
image: "ghcr.io/home-assistant/raspberrypi4-homeassistant:stable"
volumes:
- /home/pi/config:/config
- /etc/localtime:/etc/localtime:ro
restart: unless-stopped
privileged: true
network_mode: host
devices:
- /dev/i2c-1:/dev/i2c-1
I just use the container, copying the custom_components folder to config. My concern is that you mentioned that UI would be the only way to install it in the future. Please reconsider not deprecating the manual installation method.
Hey @josemotta, thanks for the feedback. I don't have any plans to remove the manual configuration method anytime soon, but I may decide not to add new config settings to that method if it adds significant complexity.
It wouldn't surprise me if Home Assistant eventually removed support for manual configuration at some point in the future, so I was trying to get ahead of that by sunsetting manual config here.
I'll leave this issue open in case we get more clarity on the future of manual configuration within the ecosystem one way or another