Ethan Murphy 🥉

If yours is an app based monitor on home Wi‑Fi make the network a little more boring at night :) Lock 2.4 GHz to 20 MHz on channel 1, 6, or 11. Use non DFS 5 GHz channels like 36 to 48. Turn off band steering and auto channel hops until morning. Also check that your router is not scheduled to reboot overnight and that any mesh nodes are not in the same room as the parent unit. Boring is good. If it is a non Wi‑Fi handheld type and give it distance from the router and any cordless phone base and keep eco features off while you sleep, and try a re‑pair after a full power cycle of both units. Small changes go a long way here.

If it drags, I use a hard stop: gotta run to class, catch you later. Or I've got a study session, good seeing you. Start walking as you say it and it ends clean.

I'm with you on the no go zones and the clean mapping pass with lights on. That combo keeps the robot from drifting into cable nests, and starting from the dock each time keeps everything lined up. For the stubborn cable clusters, your pick of a magnetic boundary strip is perfect because it makes a simple physical do not cross line in front of power strips and slack piles without needing to tweak the map every time cords shift. I had the same mess around my TV console and the strip stopped my bot from nosing under the stand while the extra buffer in the map took care of small drift.