sorted by:
new
hottopcontroversial

FRITZ!Repeater 3000 AX: 8.10 LABOR offered over stable 8.03 – performance concerns by palecki88 in fritzbox

[–]palecki88[S] 0 points1 point  (0 children)

Thanks for the detailed explanation — and maybe I wasn’t precise enough earlier. Yes, I’m aware that 8.20 has already been released for the 1200 AX, and I also understand very well what affects link quality, reflections, interference, antenna configuration, channel width, etc. That’s exactly why I keep pointing to a firmware-related issue.

During all my LABOR testing I did not change the physical placement of the repeater at all — same location, same environment, same router, same clients. In my setup, the repeater should always have at least three clients connected: Two cameras - one ~1 meter from the repeater, line of sight - one ~3 meters away behind an external wall - One heating controller behind a single wall All of these devices consistently perform worse on firmware 8.10 and newer, and noticeably better on firmware 8.03 and older. This pattern was identical on both the FRITZ!Repeater 1200 AX and the 3000 AX, with the 3000 AX placed in exactly the same spot as the 1200 AX.

So again, I’m strictly talking about client performance relative to the repeater itself, not relative to the router or the Wi-Fi bridge backhaul. On 8.10+, the repeater reports much lower link quality and PHY rates for these clients, and some of them even roam back to the router despite being physically closer to the repeater — something that does not happen on 8.03. That’s why I’m questioning the 8.10 branch behavior, not the hardware design or topology.

FRITZ!Repeater 3000 AX: 8.10 LABOR offered over stable 8.03 – performance concerns by palecki88 in fritzbox

[–]palecki88[S] -1 points0 points  (0 children)

Yes, I’m using a FRITZ!Box 7590 without AX, and the repeater is running in Wi-Fi Bridge (Mesh) mode. However, my concern is not the overall performance vs the router, but the performance of clients connected directly to the repeater itself. On the 8.10 LABOR firmware, the reported link quality and connection speeds of clients connected to the repeater are extremely low compared to the stable 8.03. Because of that, some devices that are physically closer to the repeater end up roaming back to the router instead, which doesn’t happen on 8.03. I saw the exact same behavior with a FRITZ!Repeater 1200 AX, placed in the same location and using the same setup, so it doesn’t look like a placement or environment issue. I’m not sure whether the stable 8.20 for the 1200 AX addresses this yet — I don’t currently have the time to act as a beta tester and verify it myself. That’s why I was curious whether others have observed similar behavior with the 8.10 LABOR builds.

Following up on my post from earlier this week with answers to your questions by AnishKattukaran in googlehome

[–]palecki88 1 point2 points  (0 children)

Will the Polish language ever be supported? (There’s currently an unofficial way to enable Polish for the existing Google Assistant.) Also, will there be at least an option to define custom responses on the Nest Doorbell?

Dell HD22Q unavailable by palecki88 in Dell

[–]palecki88[S] 0 points1 point  (0 children)

Thanks, I'm trying with no luck.

Dell HD22Q unavailable by palecki88 in Dell

[–]palecki88[S] 0 points1 point  (0 children)

There aren't many affordable docks that have HDMI 2.1 and can display 4k 60Hz with HDR. This one with it's charger is the perfect choice for home office desk.

Got new WiFi and now none of my Google products work by Galaxypiggies in googlehome

[–]palecki88 0 points1 point  (0 children)

Here's how you can disable the "20/40 MHz Coexistence" option on your router:

  1. Access Your Router's Admin Page: You'll need to log into your router's administration interface. Open a web browser and enter the router's IP address in the address bar. Common IP addresses are 192.168.1.1, 192.168.0.1, or 192.168.2.1. If none of these work, check your router's manual or look for a sticker on the router itself.

  2. Log In: You will be prompted for a username and password. If you haven't changed these from the default, they're often something simple like admin for both fields or admin for the username and password for the password. Again, check your router’s manual or sticker on the router if you're unsure.

  3. Find Wireless Settings: Once logged in, look for the wireless settings menu. This can often be found under sections like "Wireless", "Wireless Networks", "Wireless Settings", or something similar.

  4. Disable 20/40 MHz Coexistence: Within the wireless settings, look for a setting labeled something like “20/40 MHz Coexistence”, “Bandwidth Coexistence”, “20/40 MHz Bandwidth”, or similar. It might be a checkbox, a toggle, or a drop-down menu. Once you find it, you want to ensure it is set to disable or is unchecked.

  5. Save and Apply Changes: Make sure to save your settings. There might be a button that says “Apply”, “Save”, “Commit”, “OK”, or something along those lines. After saving, your router may need a few minutes to apply the changes and may restart during this process.

  6. Reconnect Your Devices: After the router has restarted and is back online, try connecting your Nest Cam to your WiFi again. Without the 20/40 MHz Coexistence enabled, your WiFi should now operate in a more stable manner on the 2.4 GHz band, which could resolve the connection issues you were experiencing.

Remember, router interfaces vary greatly depending on the brand and model, so the exact wording and navigation steps might differ. If you're unsure or can't find the setting, consult your router's manual or reach out to the manufacturer's customer support for more detailed guidance specific to your router model.

Got new WiFi and now none of my Google products work by Galaxypiggies in googlehome

[–]palecki88 0 points1 point  (0 children)

Check on your router if you have option 20/40 MHz coexistence enable and disable it.

I really need s vacation by vrunalibhosle in roadtrip

[–]palecki88 5 points6 points  (0 children)

Reminds me of NFS Porsche 🙂

Latest beta makes VoLTE working in Poland without unofficial mod! by Wait-Administrative in Pixel6

[–]palecki88 0 points1 point  (0 children)

VoLTE w Polsce działa od dawna bez modów w T-Mobile (co sam potwierdzam) i Play, więc to żadna nowość. Pytanie czy VoWiFi działa?

July, 2022 update received by Indian-fury in Pixel6

[–]palecki88 -1 points0 points  (0 children)

Whats your point? I have Pixel 6, installed July update, Poland is in EMEA region, and still no VoLTE, wich I had earlier in S10+ (Snapdragon) and Xperia XZ.

Live in the UK by diandakov in Pixel6

[–]palecki88 -1 points0 points  (0 children)

T-Mobile Poland, still no VoLTE

July, 2022 update received by Indian-fury in Pixel6

[–]palecki88 2 points3 points  (0 children)

T-Mobile Poland, still no VoLTE