I could spin up another Pi. Don’t have any online that I’m not using in a production setting. I have a host (oldbear) that I run several VM’s on. Here is that setup as well as the stack configuration for the HomeBridge docker container.
VM on Proxmox = HA (10.0.10.90)
Docker Container = HomeBridge (10.0.10.199)
From HW point of view , your setup is great .However I think this add another layer of complexity which goes beyond HA . I had a friend who faced same issues using VMs and we could not solve it but I hope you can .
@ALDIY I just received this in the error log. Not giving me much information.
Logger: homeassistant
Source: runner.py:98
First occurred: 7:57:18 PM (1 occurrences)
Last logged: 7:57:18 PM
Error doing job: Unclosed connection
Could this be vmware issue and best we look to vmware support ?
for the error look at this
Edit 
In the logger make it on debug , this way we can get a lot of info that might help
Well, I just spun up another container (Docker) with HA and was able to get HomeBridge connected instantly. So, it’s definitely an issue with Proxmox VM and the HomeBridge Docker container. Not sure where the problem exist. I’ll continue to play with it as I wanted to be able to utilize the full OS of HA.
You must make it work on VM . I think its a challenge but I have a felling you can do it
I’ll continue to prod and will report back.
Sorry for the slow response. It’s not letting me create new posts because I’m still the “new guy”.
I’m not sure how to run Homebridge within HA instead of using the separate container. But I’ll do some research and see if I can wrap my head around it.
Check the first paragraph and tell me what do you actually want to do . It could be the case that you do not need a separate homebridge host
Yea, I agree with aldiy’s last post. You probably don’t need a separate homebridge host. Have you tried running homebridge within HA?
I think its you mr moto2000 that suggested not to use a separate host in your first reply .
For me , its good to have him test what he wanted to do first because i think his hardware
is not utilized and for unix / linux guys that is a sin
He is also very good technically and I am sure he will be able to do it on VM if he wanted to
but today he is in the forum jail because its his first day .
Cheers
I was just saying that I agree with this…
Yes I know and I was giving you the credit for the solution .
I think you misunderstood what I meant , I dnt mean anything bad .
cheers
Oh my mistake, I did misunderstand! haha 
Homebridge within HA instead, Just remember to disable the safety mode on portainer. you will get a warning but thats fine.
@Tejasjpatel That’s actually the tutorial I was following the first go around. What I have verified now is that a VM (Portainer as the hypervisor) just does not work with the HomeBridge Docker install. It works two other ways of messing with it.
Today, I actually integrated Alexa to the HA install and that was a blast! (no, seriously, it was unique and many steps. Working the first time was a rush.)
I’ve been in development for 15-ish years and only about 5-6 months in with the entire home automation piece. It’s a whole new world and now my YouTube algorithm is definitely thrown off. I’ve watched entirely too many automation videos in the past two days.
Lastly - now that I’m out of jail, are there any other limits I should be worried about?
this method worked for me i have my nest products intergrated via home kit, did you remember to disable the saftey on portainer when you did this, as i had problems and couldn’t move forward till i realized it.
If i was you I would try again, its so worth it. i think i did it like 4 times before i i got it right.
As for the future, the beginning is always the hardest as you dont have the knowledge, keep at it, read, watch, and code.
Disable safety on Portainer? Either I missed this step or I’m not following correctly.
yes correct, you must have missed this step.
I missed this step and i couldn’t get it to work until this was done it would just load forever. Let me know how you get on.
Ahh, I see why I didn’t quite follow. I was not running Portainer from the add-on on the OS. I already had Portainer running on another host. Essentially I had a VM (call it 10.1.1.1) running on a physical host. Then I had Portainer running as a container on another host (call it 10.1.1.2). They could communicate with each other, but Portainer was not installed as an add-on within the HA install.
@Tejasjpatel I actually just found that Portainer has been removed from the repository (*believe it was due to code conflicts which caused Portainer not to start) as an add-on.
So, back to the way I had it installed, which appeared to work, just never setup.
FYI: I have been successful in running both HA and HB within two different containers (Docker) and gave up on the VM method. However, keeping the instance alive and will continue to play with it to see if I can get it to work.
