Fairly recent development, as it was not always the case, but lately I’m having to power cycle my X1C to get a good wifi connection. Without doing that, the camera connection does not engage, and the uploading of models to the printer can struggle. Doing a power cycle fixes these problems for roughly about 24 hours.
Anyone else experiencing this? From what I’ve read, the X1C is meant to be left on 24/7, so I’m wondering whether a recent update may have messed with it.
Have you instead tried power cycling the other devices needed to establish a connection with your printer: WAP, router, PC, …
Reporting back: I have a wifi mesh network, and after faffing around with the X1C, I think it may lack the “roaming” capability, or whatever the 802.11 standard is called that allows it to pick the optimal access point in the mesh. So, I gave it a simpler connection, and it seems to be working now without the problems it had prior.
I recently had something similar happen where on 1 job I was able to monitor the video with the Handy app no problem, sent the next job and left the house only to find that I can no longer access the printer remotely. My home Internet is TMobile, so I rarely bother having my phone connect to WiFi at home since both connections are using the same cellular provider, so both jobs were being accessed over my phone’s own cellular modem. Once I was sure the print job would be done based on timing and an assumed successful print, I remotely power cycled the printer via the TP-LINK Kasa outlet it is connected to. Once it rebooted I had remote access again.
I can confirm that mesh roaming is the issue. I just got my xcc and it had problems with wireless mesh roaming right out of the box. Most routers have settings to disable roaming altogether or to force some clients to 1 node. It instantly fixed the problem for me, and I was about to get less than serene.
802.11 does not have a mechanism for the controller/AP side of the equation to enforce client assignment. Specs dictate this is a client side function. Some brands have implemented workarounds to the standard (because, why bother having a standard…) but these methods are not full proof. The only way I can think of to get to a similar end with in 802.11 would be to have a specific AP broadcast a BSSID for the device in question but that is not keeping with a mesh network topology, nor an exposed configuration on most consumer solutions.
My eero network has less than desirable configuration and reporting. Luckily issues with my X1C connecting have been relatively inconsequential and rare - and all APs are at an acceptable distance to its physical location so it does not matter which it choses.
That’s what I have also. I have the eero 6+, and I’m not very happy with it. It can only handle about six access points in a network before it starts exhibiting problems. That might not sound as though it would be a problem, but it is because their signal range isn’t very good.
If I could be sure of something better, I’d be inclined to switch over to it. For a while it seemed as though people enjoyed the Ubiquity Dream Machine Pro for managing wifi in their homes. Since it’s a mostly tech-savvy crowd here, if anyone has any product recommendations based on their own experience and satisfaction, please do post. I’d be interested to hear.
Yeah, I swapped to eero when migrating my traditional home security system to Ring. At the time my Orbi RBR50 was falling on its face dealing with 100+ clients after having too much fun installing tp-link Kasa outlets, switches, and bulbs. Since the Ring Alarm Pro contains an eero 6 base station, I added 2 eero 6+s to use the Ring cell backup for the entire mesh and switch ring cameras to edge local storage.
Performance with all eeros hardwired has been fine covering 4500 sq ft. My biggest complaints are around the Apple-esque lack of configuration control and complete lack of reporting in their security stack. They provide pretty dashboards on how much they scanned and blocked, but won’t tell you what was blocked.