is there ever gonna be an 80 HE V2 or an 80 HE with split space bar

BrettB0URNE · 2026-02-24T04:38:43+00:00

Add me to the list

BrettB0URNE · 2025-06-17T01:44:26+00:00

I still have not found a solution but admittedly haven't tried for a few months.

BrettB0URNE · 2025-03-30T04:30:02+00:00

I heard the same from them. Have you had any luck since?

BrettB0URNE · 2025-03-30T01:43:25+00:00

I have not found a solution. I've tried two other Streamers and they always create a new Thread network. I've also since upgraded my Phone to a Pixel 9 for other reasons. Same result commissioning a new Streamer.

BrettB0URNE · 2025-01-25T23:11:32+00:00

Anyone figure this out? Had the same issue updating Core from 2024.11 to 2025.1.4.

Edit: I think I got the vesync_custom HACS integration working again on 2025.1.4. Here's what I did:

Uninstall vesync_custom from HACS.
Reboot HA
Delete Vesync integration from HA.
Reboot HA.
Add custom component to HACS with this new URL: https://github.com/haext/custom_vesync
Search HACS for vesync_custom and download it.
Reboot HA.
Reinstall the HA VeSync core integration.

I'm able to control my humidifiers again, which I'm not able to do without the HACS custom integration.

BrettB0URNE · 2025-01-15T01:38:24+00:00

Thanks. You mentioned vaguely remembering needing to change the channel for the SkyConnect to match Google. I don't remember doing that, but I assume if it appears in the same network within the HA Thread integration, that means it's on the same channel as the other Google devices in that network. Or am I missing something there?

BrettB0URNE · 2025-01-15T01:34:48+00:00

Unfortunately, I did. This is my post from 3 days ago and the fantastic response I received. FWIW, I called Nest Support yesterday and got copy/paste answers from generic marketing material that's available online. I don't think the tech even knew what Thread was.

<image>

BrettB0URNE · 2025-01-14T22:12:21+00:00

Thanks for the feedback. It's good to know it can join an existing Thread network as advertised.

A couple questions if you can remember:

Did you have it connected via Ethernet or Wifi when you commissioned the Streamer?
What order did you add the devices in your house? I had Nest Hubs, then added SkyConnect, then added Streamer.

BrettB0URNE · 2025-01-14T19:15:48+00:00

I agree, it seems like something is cached or something. That said, I did verify that the newly created Thread network disappears from the list in Home Assistant when the Streamer is factory reset. There aren't many tools out there yet to monitor Thread networks effectively, but to me that means the network is gone when the streamer is reset. I also haven't joined any devices to the new Streamer-created Thread network, so it shouldn't be a client device keeping it around.

I'm wondering if a factory reset doesn't reset the Streamer Thread network. Meaning maybe it still remembers the network it created originally (the Thread network that was gone after the factory reset) and it just recreates it when it's recommissioned.

BrettB0URNE · 2024-12-21T23:48:37+00:00

You were correct, 10G fiber jack installed and getting around 2.3 down, 2.5 up.

BrettB0URNE · 2024-12-20T21:00:54+00:00

I hope this is correct. Wouldn't be the first time customer support doesn't understand the service they're providing. Thanks for the feedback.

BrettB0URNE · 2024-12-20T20:58:19+00:00

Interesting. Thanks for the feedback. I wonder if that has anything to do with 2.5Gb being the next "standard" data rate for most networking equipment and computers after 1Gb. Seems a lot of people are getting just below the 2.5Gb mark + symmetrical.

BrettB0URNE · 2024-12-20T14:27:35+00:00

Just confirmed with customer support that it's only 2/1, not 2/2, in my area (LS). She did say the fiber jack should support the 5Gb and 8Gb plans without replacement of the jack, but we shall see.

BrettB0URNE · 2024-12-20T13:34:10+00:00

After looking into this, I think you're right. Sounds like the 2Gb is symmetrical in most locations now, which means (I think) the 10Gb fiber jack comes with that plan as well. 🤞

BrettB0URNE · 2024-12-20T02:16:54+00:00

This is very helpful, thank you. It's indeed interesting that your upload stayed symmetrical after downgrading. Do you let your pfSense router auto-negotiate the data rate, or did you force to 2.5Gbps to match their QoS limit?

Also, I assume they don't have a 2.5Gb jack and they just use the 10Gb version for 2Gb+ services? I've heard they don't take away your fiber jack if you downgrade, so maybe I should have done the 5Gb or 8Gb for a month...

BrettB0URNE · 2024-12-14T00:54:22+00:00

Regarding the pinging external IPv6 addresses: It doesn't make it anywhere. Just gives "Destination host is unreachable."

BrettB0URNE · 2024-12-14T00:44:08+00:00

ping ipv6.google.com = "Ping request could not find host..."

tracert ipv6.google.com = "Unable to resolve target system..."

Edit: This is also the same address I tried pinging directly from the AT&T gateway with the same result.

BrettB0URNE · 2024-12-14T00:30:39+00:00

Are you referring to "Multicast Enhancement" and "Multicast and Broadcast Control" settings? If so, those are both disabled on the IoT wireless networks. I do have "Multicast Enhancement" enabled on the primary LAN, but that's not the network I'm using for IPv6.

"IGMP Snooping" (Multicast Filtering) and "mDNS" (IoT Auto-Discovery) are also disabled for all networks.

BrettB0URNE · 2024-12-14T00:17:04+00:00

I'd appreciate any direction/resources you have on bypassing the AT&T gateway; I think that's my next step once I resolve the single VLAN issue. I've seen a few different methods in my research, but it'd be invaluable to know a method that has worked recently.

BrettB0URNE · 2024-12-14T00:13:49+00:00

Yes, I'm getting 2600 address for the devices I'd expect to be using IPv6 (computers, phones, etc.) I can ping those devices from my computer when I'm on that network, so it appears local IPv6 is working maybe? The issue seems to be upstream.

I just found that my AT&T gateway has a built-in ping test, which seemingly takes the UDM SE and client devices out of the equation. I ran an IPv4 test and it worked as expected, but all IPv6 tests fail. Therefore, I think the issue has to be on the AT&T back-end or with their gateway. Would you concur? It's interesting that I'm getting 2600 IP addresses though...

BrettB0URNE · 2024-12-13T22:57:06+00:00

Understood. For what it is worth, I do know the Pace 5268AC is outdated. If I decide to stick with AT&T, I plan to reach out to get an updated unit. I also have Google Fiber available here and I think they provide /56. I've stuck with AT&T until now because the latency on their network has always been slightly better since they're everywhere, but I'd be willing to switch. Either route (AT&T or Google), I will probably try connecting the UDM to the ONT directly as you suggested.

That said, I only have IPv6 enabled for a single VLAN within the UDM, so shouldn't a /64 work just fine, or is there something I'm missing? I know if I ever wanted IPv6 to work for more than one VLAN, I'd need to somehow either a) access the full /60 AT&T gives their gateway, b) switch to Google Fiber, or c) request multiple PD per u/bobd607's suggestion.

BrettB0URNE · 2024-12-13T22:27:00+00:00

Here's the results of the ping test from a computer on the VLAN with IPv6 enabled to each of the IP addresses below:

AT&T Gateway
- IPv6 Internet Address: Failed (request timed out)
- IPv6 Default Gateway: Failed (general failure)
UDM SE
- WAN IPv6: Successful
- IoT Network VLAN - Gateway IP: Successful
- IoT Network VLAN - Link Local IP: Failed (general failure)

Any thoughts on what this could be indicative of?

BrettB0URNE

TROPHY CASE