So I'm not sure what to say, but somehow HomeKit has started working. Here we go...
I got back into touch with apple and they took more logs. I haven't heard back from them since then.
While I was desperately waiting to hear back from apple, I used an ip scan tool on my Mac by "IP scan Pro." I have everything on my network labeled on this tool and I noticed that the MyQ Homebridge was not showing. So at this point the garage doors were showing "No Response" in HomeKit but they were showing up fine in the MyQ app (same issue as before). I don't get how it's not showing on my local network on my local IP address range.
At this point I was certain this was a chamberlain issue because the device is basically falling asleep on the network and not visible. I called chamberlain, told them what was going on and the had no history of me calling in before somehow. I have no idea how not, but I told them what was going on and they acted completely different. I had not called them for 2 months and they said about 2 months ago their team had totally changed their focus and support for HomeKit, and that they need to now make sure HomeKit works for their users. Looks like I must had called just before that when they didn't care. Anyways, because of no history of calling in, they had to walk me through ground zero of reseting the home bridge and repairing everything. Reseting everything was the same procedure, but the one thing different this time around was connecting the MyQ homebridge to wifi. This time around, I added the home bridge to wifi before doing anything in the app. With the new iOS version I had (iOS 13.2.3) they had me go to settings app > wifi > and then the home bridge appeared there. It also said "setup this accessory." So I did that, went back to the app, and this time the actual process connecting the MyQ homebridge to HomeKit worked. SIDE NOTE: They didn't say much about the MyQ homebridge not being visible on my network other than that was out of their realm and that I needed to start here with them before escalating it further to their quality assurance team which may have the tools to diagnose an issue like that.
For a few weeks everything was good! Then I noticed "No Response" again. But then it fixed itself. But then it did it again later and didn't work. At this point I wanted to try to do 2 more things. I originally had it located in the garage where I do get good wifi but the original MyQ non HomeKit bridge was there because I had it connected to ethernet. However on this new MyQ homebridge it unfortunately does not have ethernet and because of the cheap wifi card chamberlain used in the MyQ homebridge, when looking at my access point statistics, the signal for the device was very low. I also removed the MyQ homebridge from static DHCP from my router. In other words, I had an assigned IP address to it before which I do not have anymore. At this point this seemed to have done the trick. Another 3 weeks with no issues. SIDE NOTE: MyQ app must ping the device and HomeKit does not, or at least it is done differently between the two and does not work when HomeKit does it. Because this would be my only assumption on why HomeKit says "no response" and MyQ app is fine when the MyQ homebridge could not be found on my network.
Great. Now here we go again, however the MyQ homebridge is visible on the network but shows "No Response" in HomeKit. I looked into the MyQ app and "Home Data" was somehow turned off. It must have been app updates and they did something different with it which cause home data to turn off. I turned it back on. HomeKit showed "no response" still. I was too lazy to go unplug the MyQ homebridge and plug it back in so I checked a few hours later and saw it successfully show up in HomeKit.
Seriously what a pain. Apple may have done some fine tuning adding IoT devices to wifi and maybe their HomeKit app. Chamberlain may have fixed their app, since HomeKit home data was turned off after updating the app. And/or the issue was solved by moving the MyQ homebridge closer to one of my wireless access points.
It may have been one thing or all 3. Please let me if any of this helps and what may have solved the issue for you.
-Anthony