homeassistant

12461 readers

18 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 2 years ago

MODERATORS

[email protected]

greatalbatross

Shelly devices not discovered (self.homeassistant)

submitted 2 weeks ago by peregus to c/homeassistant

11 comments fedilink hide all child comments

Hi all! I have a HA server in my LAN and all my IoT devices are in a separate VLAN. In this way to insert all the devices I have to configure them all manually using MQTT commands. Since I'm fed up about this method, I've added a second NIC to the HA VM (Proxmox) that is in the IoT VLAN. When I enter the terminal I see that HA has 2 IPs, one for each network and I thought that all the Shelly (they use the same MQTT broker that uses HA, they're not configured for cloud connection and ColoT is enabled) devices would appear in HA, but...they don't. How do you think that I can troubleshoot this problem?

you are viewing a single comment's thread
view the rest of the comments

[–] just_another_person 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

When you say "VLAN", are you saying this a tagged network? It sounds like you just have two physical networks here. What is handling the tagging?

[–] peregus 1 points 2 weeks ago (1 children)

It's a tagged network. The VLANs are setup in the OPNsense router and since HA is a VM, the VLAN is taken care by Proxmox that presents an untagged NIC to the VM.

[–] just_another_person 1 points 2 weeks ago

Well there's a lot of stuff happening all at once, and without a bigger picture, I can just give you some basic steps on how I would start debugging:

Make sure the new untagged interface is actually working as expected (check rx/tx, basic pings)
Try pinging the devices ONLY from that interface
Check the configuration of the devices if you can contact them and see what endpoint they think they are supposed to be talking to
If the are WiFi, make sure that wireless network can be pinged from this new interface (join a laptop and ping back and forth)
If all else fails, snoop that interface and see what IS traversing it