Regarding the Halo-Level disconnect issue, this happens alot with Sonos systems too, and the standard support response sequence is:
(i) assign static IPs, (ii) look to make sure no other devices got assigned the same IPs, (iii) don’t reboot the Level, reboot the Halo, (iv) don’t reboot the Level or Halo but reboot the Wi-Fi access point, (v) create a divided network (software or hardware) to see if it still happens with *just* the Halo and the Level on their own net, (vi) hardwire the Ethernet ports on both products, then (xx) all the other Wi-FI & networking boogiemen including network exenders and meshes (Sky Q known lossage, Eero (fails) vs. Orbi (works), and a whole rabbit-hole of stuff).
If you can do (v) easily, either yourself or by borrowing some spare old networking equipment, that might cut a whole bunch of the yes/no tree from your dealings with B&O “support”. While it is theoretically possible that the Level’s wake-on-LAN design is flawed, it seems very unlikely because there would be *many* many many complaints. The Sonos gear I tend loses a zone or two once or twice a year, and even Apple Homepods disappear off the network occasionally, usually due to a catastrophic wireless interference issue — plus some edge-case recovery bugs in the products of course. But every 2 or 3 days? You can probably find and fix it yourself. Don’t give up, and maybe start a fresh thread here once you have your nope-that-wasn’t-it-either’s all in a row?