Yes, well, I’ve been following ESPHome and in general HA for plenty of years. This is my 5th HA installation. I never really had an use case for ESPHome because I mostly used Tasmota for smart plugs / lights / led, and those few times I had to use an arduino/ESP device I wrote the code myself.
But this bluetooth proxy really bothers me And i wish to fix this, and it’s been months I try and pause, get back at it and stop …
the device should be adoptable by your ESPHome dashboard. How that works I can’t say, but after a short readup, it should be automagically
Yes, I read and understood the same. Even a couple of YT videos I watched showed that “the device just shows up”.
You can always flash the BT proxy, to stay with your example, again via the ESPHome dashboard.
Yes of course, I can get the FW from github and do it manually. But the thing is, it bothers me very
the screenshot you’ve setup ESPHome as Add-on under HA-OS
Correct. Specifically, this is a VM (under vSphere) with HA OS and the ESPHome addon, and this is the latest HA deployment and the “final” one.
Then I have another instance of HA which I am still using because I set it up on a RPI 4 last year when I moved to the current flat and was testing the PoE with the new switch and wasn’t able to power on the whole datacenter.
Both of the instances are on vLan 2.
Previously I had other HA deployments, but it was before ESPHome was mainstream, and I did not have vLans, only a few Subnets.
disable “Use ping for status”. Restart the Add-on
I’ve done it plenty of times. Really, I’m not joking. Ping ON, Ping OFF; reboot; re-flash the proxies…
I believe if I have to keep investigating the issue, the next step is setup a HA in the vLan 3 where the IoTs are and exclude that this is a mDSN issue. This is partially excluded already because I have already a couple of IoTs in that vLan: The HUE bridge, the Broadlink RM Pro […], all of them work just fine. Meaning that they are discoverable by HA thanks to PIMD.
Thanks a lot for taking the time to answer my question