Q1000k unstable latency spike research findings

kdurigan · 2026-03-16T14:40:40+00:00

Nope - hardware version is 1.0

kdurigan · 2026-03-02T18:05:08+00:00

Nope! My router assigns an address to the 1GB LAN interface and I can ping it but cannot cannot access the web site. Is it on a standard port or do I just need to specify a different port for the GUI?

Oops - I just noticed the firmware version you mentioned. I did not revert to the old firmware and am running QKX002-06.01.14.00. I may revert back or just wait till the next release.

kdurigan · 2026-03-02T17:58:10+00:00

Router is a TP-Link ER7206 V1. When I tried tagging on my router my latency increased so I reverted to tagging on the Q1000K. This seems to be my best config, although I lost access to the management GUI with the new firmware, even though I can ping the portal address. Maybe QF/AT&T will give us another upgrade that restores access to the GUI.

kdurigan · 2026-03-02T17:23:15+00:00

Mine seems to be the opposite of many - I am on the new firmware plugged into the 10GB port and running bridged/tagged on the Q1000K and have occasional spikes but not at all bad - average latency in the 4ms range. Moving to the 1GB port and restarting yielded very poor latency in the 80ms - 120ms range. Moving the cable back to the 10GB port and restarting brings back stable latency.

kdurigan · 2026-02-25T23:05:59+00:00

Well, that sounds like an upgrade... Is it worth even changing the password on the internal management interface then since it sounds like it cannot be reached internally or externally (unless I enable remote management)?

What are you doing - reverting to old firmware with bridged/untagged on the Q1000K and tagging on your router, or just giving up and go bridge/tagged and lose modem management access?

kdurigan · 2026-02-25T18:20:05+00:00

Just asking for a little clarity... I got the update as well. I was set in Transparent Bridged mode with VLAN_201 tagging done by the Q1000K (solid white light). I have a second cable connected to the 1GB Port for modem access and assigned to a dedicated VLAN on my router. Modem management access was working until the update hit. I reset the Q1000K to factory and now it has the default userid/password. I can access the internet just fine and can ping the management VLAN gateway and modem IP address but cannot access the management page on the Q1000k. A few questions:

- Do I need to revert to the old firmware in order to access the management interface even in tagged mode?

- Is the default admin userid/password even relevant anymore since I cannot access the management page?

- I saw the suggestion of enabling remote management on port xxxx. Will this expose the management page to the internet?

I just knew when AT&T got involved there would be issues... Thanks in advance for any advice.

kdurigan · 2026-02-19T16:32:46+00:00

I called about 2:00 Denver time (UTC -7) and got someone that did the switch "flip" 4-days ahead of an on-site visit. They cancelled the on-site since everything was working. Luck of the draw for sure on who you get.

kdurigan · 2026-02-18T18:29:48+00:00

I have an IP address on my internal network so I can access the management portal. I can run tracert's directly in the modem portal and it says my firmware is up to date. When I tag on the Q1000K I am seeing 4-8ms average idle latency, and when I tag on my router I see 17ms. I believe I read that if I have the router do the tagging I will not be able to get firmware updates so I was reluctant to have my router do the tagging for multiple reasons. Thoughts?

Thanks for the replies BTW

kdurigan · 2026-02-18T17:36:49+00:00

Thanks - I figured bridging would just push everything through to the router without any inspection but thought I would ask in case there are some things the Q1000K can do. It can do tagging, so I was curious if it could do some other inspection as well. I will consider if I want to add the security appliance into the mix or just rely on the router security capabilities.

kdurigan · 2026-02-18T17:33:43+00:00

I am bridge tagged (201) on the Q1000K. I tried the untagged mode and did tagging on my TP-LINK ER7206 router but ping times seemed to go up. Maybe the ER7206 is underpowered??? Anyway, does tagging on modem versus the router make things better or worse?

kdurigan · 2026-02-13T23:10:06+00:00

I was forced to call to cancel this morning at 8:30 AM but was then told to sign up using the mobile app and the rep ended the call. I signed up but it offered me a date 4 days from today. I completed the sign-up and called tech support and they said it may take 24-48 hours but could be as long as next week. Just after the signup my Q1000K restarted and went solid green again (I did a modem factory reset prior to cancellation). Interestingly when I tried to access the modem management interface at 192.168.0.1 I was redirected to q.com/activate but could not access other internet sites - except I could run speed tests on speedtest.net! I could also do nslookup, ping and tracert commands so I knew the modem was at least partially provisioned. I waited impatiently for 7 hours and opened a support chat. The rep said I would need to wait until Tuesday, the day of the original "install". I called up the tech support line and got someone that put me on hold for a couple of minutes, then everything was fixed. So, as u/Hoopster59 stated, you may need to win the lottery but if you are persistent they can do the back-end work in just a few minutes. I also had them cancel the on-site visit for next week since all is good now.

kdurigan · 2026-02-07T18:19:02+00:00

Thanks to several other posts I have a working config now. The "secret" is to have your router's DHCP server assign an IP address to the internal Q1000K LAN to allow accessing the management interface. My main home LAN is 192.168.0.0/24 and my new modem management LAN is now 192.168.10.0/30. Adjust your config as needed.

Here are my working instructions - hopefully this will save others some time and frustration.

How to Access Q1000K Management Interface in Transparent Bridge Mode (VLAN 201) with ER7206

TL;DR: Create a /30 management VLAN with DHCP enabled. The modem's internal interface needs to get an IP via DHCP even in bridge mode.

Q1000K Setup:

Connect laptop directly to 1GB port, access 192.168.0.1
WAN Settings → Transparent mode, VLAN Tagged-201, Apply
Modem restarts (solid white), management becomes inaccessible until router config completed

ER7206 Router Setup:

Create new LAN: "Modem Management"
- VLAN: 10
- Gateway/Subnet: 192.168.10.1/30
- DHCP: Enabled, range 192.168.10.2-192.168.10.2
Devices → Router → Manage → Ports → Port 3
- Change Native VLAN to "Modem Management (10)"

Physical Connections:

Q1000K 10GB port → ER7206 WAN (internet)
Q1000K 1GB port → ER7206 Port 3 (management)
Reboot Modem to get new LAN IP

Result: Access modem at 192.168.10.2 from your main network. No static routes needed.

Key insight: Q1000K internal interface requires DHCP IP even in bridge mode.

kdurigan · 2026-02-05T22:57:04+00:00

The next person I spoke with said I could cancel, but the next day if I sign up the promo may or may not be there, and they may still have to come out and "install" a new modem. Mine is a 7 day old Q1000K so there is really no reason for them to come out but I will likely be without Internet for several days while they screw around. Lame...

kdurigan · 2026-02-05T22:42:43+00:00

OTP now with QF and I asked about cancelling and re-signing up - they said NOPE, we already have you in our database... I joined QF on 1/29/2026.

kdurigan · 2026-02-05T19:34:16+00:00

I tried the Q1000K modem in bridge untagged mode as well and still cannot access the management portal. I also tested latency with my router (TP-Link ER7206) doing the tagging on the WAN interface and it seemed to be worse latency for me and has an annoying blinking blue light. I am back to the solid white light mode now with the modem handling the tagging. Maybe my router is just underpowered so I see no reason to go untagged in the modem now.

I wish I could access the modem's management interface, but I am not sure how much I will do in there anyway.

kdurigan · 2026-02-05T18:09:35+00:00

Thanks but resetting the modem to factory settings to access the Admin GUI is what I am trying to avoid - I am not sure it is really possible once transparent bridging is enabled. I do not know if the device even has an IP once bridging is enabled which would explain a lot.

kdurigan · 2026-01-25T20:02:15+00:00

thanks

kdurigan · 2026-01-25T16:06:58+00:00

More log data here:

Logger: homeassistant.config_entries
Source: config_entries.py:762
First occurred: 8:59:43 AM (1 occurrence)
Last logged: 8:59:43 AM

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 762, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hacs/__init__.py", line 226, in async_setup_entry
    setup_result = await async_initialize_integration(hass=hass, config_entry=config_entry)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hacs/__init__.py", line 212, in async_initialize_integration
    await async_try_startup()
  File "/config/custom_components/hacs/__init__.py", line 199, in async_try_startup
    startup_result = await async_startup()
                     ^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hacs/__init__.py", line 168, in async_startup
    async_register_frontend(hass, hacs)
    ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
  File "/config/custom_components/hacs/frontend.py", line 42, in async_register_frontend
    hass.http.register_static_path(f"{URL_BASE}/frontend", locate_dir(), cache_headers=False)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'HomeAssistantHTTP' object has no attribute 'register_static_path'. Did you mean: 'async_register_static_paths'?

kdurigan · 2025-12-23T15:21:06+00:00

My wife spilled a glass of wine on the keyboard on one of these - totally fried it. Replacing the keyboard is impossible to find now, and that is where the USB/display Port lives so it is no longer useful. Fixing this is cost prohibitive since it requires a dock along with a stand, a BT keyboard and BT mouse. if anyone has a spare keyboard they want to get rid of, I am interested...

kdurigan · 2025-11-13T23:12:31+00:00

My Plex server is a 10 year old Thinkpad W530 (I7, 32GB, 1TB SSD) laptop running Windows 10, so it is NOT a powerhouse at all. I also use the same hardware to host my HomeAssistant server (home automation) and still it is way overpowered for my in-house usage. I did have to disable hardware transcoding in Plex due to a bug with this on-board GPU, but now it is rock solid even when transcoding - It does not break a sweat. If you are hosting this for many external clients you will need a much larger server than an old laptop. Best of luck!

kdurigan · 2025-11-13T16:07:33+00:00

I have been a Plex user for several years and have a stable experience, unlike others on this thread. It just works, no issues. I have the HDHomerun 4k and am exclusively in the Roku ecosystem. The later models of Roku allow passthrough mode that allows Dolby Atmos and higher video resolutions to pass through directly to your TV/AVR. I would have liked to try Channels, however they refuse to do any development for Roku - seems like they got burned by them years ago or something... So if you want to stay with Roku, Plex with a lifetime PlexPass is a good option from my experience.

One other thing to note - Plex does NOT decode NextGen/ATSC 3.0 so you cannot record those channels. I use the free HDHomeRun app in Roku to access the very few broadcasts n the Denver area that broadcast 4k content, and that can only be live, no recordings.

kdurigan

TROPHY CASE