this post was submitted on 12 Nov 2023
10 points (91.7% liked)

homeassistant

12051 readers
46 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago
MODERATORS
GreatAlbatross
10
HA autodiscovery (lemmy.world)
submitted 1 year ago by 1111@lemmy.world to c/homeassistant@lemmy.world
6 comments fedilink hide all child comments
 

Hey guys,

I'm having some trouble getting back into home assistant. I was running fine on an RPi with HA in docker, but during some tinkering on another project broke the whole thing and it was easier to start from scratch.

Since last time though, I've installed a mesh WiFi system (TP link Deco). These are running in Access Point Mode. My new HA is up and running again, but hasn't auto discovered anything. I recall being surprised last time by the amount of things it found and how easily. I think there are some network settings preventing proper auto discovery, can anyone give me any tips?

Thanks in advance!

you are viewing a single comment's thread
view the rest of the comments
[–] 1111@lemmy.world 1 points 1 year ago (1 children)

Thanks for the advice. Is there a certain YAML file or something I should be looking at to check this? I installed via portainer and haven't seen any of the configs this time around

[–] AlternateRoute@lemmy.ca 2 points 1 year ago (1 children)

I highly suggest using the "stacks" feature in portainer as it lets you use standard docker compose YAML files to do the config but still lets you have the ease of use of the stop start, pull, CLI UI etc. The default way of using portainer often obfuscates important settings.

[–] 1111@lemmy.world 1 points 1 year ago

Nice one, I'm going to check this out!