You can review this topic here. I posted the issue, described what I tried, put a theory out there, researched, and a dev looked at it. (Side note, I'm not using Wi-Fi anymore)
I think it would be helpful to the community, habitat support, and engineers if system logs were available to tail or download—less guessing and more solving problems.
Network connectivity is a core feature of the product meaning it's required work for the product to work. I am very grateful that @gopher.ny is looking at this. This case seems better suited for a support ticket vs. the community (because of all the back and forth).
If this were an integration issue, I think the community input would be constructive because there are a lot of logs surrounding integration. 
Please don't take offense to any of this. I'm used to having terminal and log access. I am currently dependent on people with access to these tools, and the only tool we have as a community is guessing, pulling levers, etc... Each time I pull a lever, it takes hours to days to find out if it works; even then, it's guessing it did.
