u/richie510

I have noticed that a Unifi gateway I manage for a family member offered that IPv6 was now available on WAN1. I clicked on it and it just automatically enabled it without a popup. Their network is vanilla, so I imagine this will be a benign change. However, they have been complaining about some periodic slowness, and I'm wondering if the stuff I have been reading about Europeans suffering slow IPv4 when IPv6 is available is happening here.

Most things I read about IPv6 are Europeans complaining that too many things do not yet support IPv6, or others complaining that IPv6 is just adding complication to a network if you have anything more than a vanilla setup. However, most of the posts saying IPv6 is not worth the hassle are from 2020-2021. I'm not seeing much in this space in 2025-2026.

First, it is surprising that Quantum Fiber is enabling IPv6 and I'm not reading much about it. Second, I'm wondering if now is the time to get on the bus, or just hold tight. Any strong opinions out there?

IPv6 Popup in top left of Unifi Gateway Dashboard

Above is a screenshot of the IPv6 announcement. Note that the screenshot is for a different system that is using Comcast. The announcement is no longer available on the system with QF.

Yesterday I updated Scrypted and also updated Unifi OS. Then HKSV cameras all stopped working in Homekit (but I did not really notice until today, as Homekit is not my primary, or even secondary viewport). My reolink cameras still worked fine, so that is one data point. Debugging in scrypted showed nothing when trying to start a stream from HKSV cameras. Finally I just tried to re-add a camera and it added in just fine and started working again after the initial setup.

I'm not sure if this was due to the Scrypted update or Unifi OS (5.1.33) update. When I update Scrypted with docker it is pretty black box, so I have no idea what version I came from, but I'm now running v0.145.0.

Just posting here to give a heads up for anyone else who may have this same situation. Also would love to know which one caused this: Scrypted or Unifi?

Edit: A dead giveaway to this was that all my unifi cameras showed up as newly available Homekit devices in Home Assistant yesterday. I was bewildered by it, and just told HA to ignore them. Now it makes sense. I just wish I could remember which update triggered that response.

I have one US Plug Gen4 and two 1PM Gen 4 relays running 2.0 Beta 3 Zigbee. The update to 2.0 zigbee official is failing on all 3. It is failing when point it at the correct downloaded zip file, or try to update from the server across the web, or when letting Home Assistant do its thing.

Is this a known issue with going from Beta 3 Zigbee FW. Also, I have tried to flash the 2.0 Matter firmware with the same result.

My previous vehicle was a Subaru Ascent and I was dumbfounded when the stock tires were worn out after 26,000 miles (I was foolishly expecing 50k before wearing out). We have had our 24 EV9 Land since December 24, 2024 and the tires are worn down to 5/32 tread after only 13,000 miles. Granted, I have towed a 2000 lb teardrop camper maybe 700 of those miles, but still, this seems a bit excessive.

We are on a 2 year, 24k mile lease and I really didn't think I was going to have to put new tires on this thing before the lease was up. Dealership is quoting $1080 for new tires and the cheapest shop is showing $1050.

Has my alignement just been off the whole time and that just killed the tires? Anyone else have their tires wear out this fast? Does it drop to 5/32 fast, but maybe I have 4000 miles left before they are below 3/32?

On top of being worn out, the tech also commented that the tires are dry rotting. This just seemed like insult to injury detiling what absolute garbage the stock tires are to be dry rotted after 1.5 years.

Anyone in Denver put some decent tires on their EV9 and wanting to get rid of the stock tires with some tread that will get me to December 24, 2026?

I have a Verizon Business account with 10 lines. 6 are iPhones purchased at different times. 4 are Apple Watches. All 6 phones are showing as carrier locked, while all 4 watches are shown as not carrier locked.

At least 3 of the phones in question were purchased at full price from the Apple Store with no carrier affiliatoin as "carrier unlocked" phones. They were all purchased at least 8 months ago, some years ago.

Yesterday I spoke with Verizon support for an hour across 3 people. The first in what sounded like a contracted call center, then a first party Verizon rep in "fraud prevention" who then had to pass me to someone in billing, that again seemed to be a 3rd party call center. That last person guranteed that I would be contacted by Verizon within 24 hours and there would be a resoluion.

24 hours passed with no contact so I called back. The first person I spoke with (in what seems to again be a 3rd party contracted call center) suggested that I factory reset my phone to fix the carrier lock. I said that was nonsense, and ask to speak with a technical rep. Eventually after putting me on mute, not hold, she seemed to just like "hand the phone" to another guy. This guy went through some nonsense to finally claim that I had to call Apple support to fix the carrier lock because I bought the phone from Apple. I said that was nonsense and that he was just trying to get rid of me. So we called Apple support together and the Apple support person said that Apple has nothing to do with carrier locks, and that he cannot even look it up. The Verizon rep was ridiculous telling the Apple guy to just use the IMEI and check the lock. Eventually the verizon guy told the Apple guy to hang up. After sympathizing with me, the Apple guy, who was reasonable and professional, did hang up. After the Apple rep agreed with me, the guy was just dug in more that it was an Apple problem. I told him I wanted to speak with a supervisor. He put me on mute for like 20 min, then connected me with someone else. I thought I had finally gotten through to real Verizon support, but instead, the Verizon rep dumped me onto another Apple tech support person and then hung up.

I asked this Apple support person if they could try to connect me with a better channel with Verizon support and they tried. I was on the "apple on hold music" for a while, and then it switched to "verizon on hold music". I waited with this Verizon support music for about 30 minutes and then gave up. This was at the 2 hour and 30 minute mark for today's first phone call, 27 hours after I was told I would have a resolution.

After this I called Verizon support again, and got a similar song and dance for 23 minutes.

In all of the calls, they kept talking about the "fraud department" somehow being a gatekeeper of carrier locks. So I asked for the fraud department number. Their automated call system did not seem to have anything that could help me and eventually dialing zero caused it to hang up on me.

It seems like the 3rd party contracted support company is doing shady things to pad their numbers and are gatekeeping me from getting the help I need.

The number I called for support is 800 922 0204. Am I calling the wrong number? Is it possible to get in touch with someone from Verizon to resovle my situation and to report the frustrating behavior of their contracted support company?

I have a "Without Internet" VLAN that I have several items that do not need internet.

I have chrony running in HA in a VLAN with internet.

I have a firewall rule in my Unifi gateway allowing access to this HA Chrony app on port 123 on this IP address for the entire "Without Internet" VLAN.

With this setup my Reolink cameras can access the local NTP server and update the time. My 5 Shelly GEN3 and GEN4 devices cannot update the time with this configuration, but my GEN2 Shelly Dimmer can update the time.

The only way I can get the 5 GEN3/4 devices to update the time is to allow access to **all ports** on that IP address (HA/chrony) in the firewall rules.

Is there something I'm missing here?

I have 5 Lutron Aurora Z3-1BRL zigbee rotary light switches. They work fine (not amazing) in the hue hub ecosystem, but I'm trying to completly ditch my hue hub.

4 of my Lutron Aurora's have the latest firmware (Firmware: 0x00000c12), while one is still on an older firmware (Firmware: 0x00000c08).

The one switch with the older firmware works in ZHA in that I can trigger on zha_event utilizing the ieee and I can decipher a button click and rotary dial change, but the rotary info is pretty sketchy.

The switches with the new firmware show no events in zha_event. I have tried binding to the coordinator (Home Assistant Connect ZBT-2) and binding to groups but I cannot get anything into zha_event or anything to show up on the device within ZHA.

I also have a spare Home Assistant Connect ZBT-1 that I mess around with in Zigbee2MQTT. The documentation from z2m for this device says that it should register brightness and button clicks (Z3-1BRL documentation) but I'm only seeing it register "brightness_move_to_level" on the action, but no brightness is updating, and no button clicks register anything. I see this action in the "state" section of z2m app, and it does show that action and a 0-255 integer when I rotate the dial. Clicking the button will usually set the integer to 255 unless it is already 255, and then it **sometimes** changes the value to 0, and sometimes just keeps it at 255. (If I could get this integer into HA, I would be able to at least ditch the hue hub and keep the switches inservice.)

I'm wondering if most people are just still on the older firmware and not experiencing this problem, or if most people have just given up on this very awkward experience.

Further, I just cannot for the life of me figure out why i'm getting **something** in z2m, but I cannot get **anything** in ZHA. I think it is related to binding, but I just cannot get anything to bind in ZHA regarding this device, and there just appears to be no absolute feedback in ZHA to confirm if something is bound or not (I have had poor experiences with binding in ZHA across the board).

Does anyone have some advice for binding this device with ZHA? Does anyone have advice on how to get the state information from z2m into HA so I can operate on it like I do with zha_event on the older firmware? Does anyone know of a way to downgrade the firmware on this thing? Does anyone have a trick for this that I'm not even thinking of? Most of the posts on this device are from 2018-2022, long before the newer firmware, and they just are not helpful for me.

These things were expensive and I would like to not turn them into e-waste, but maybe they just are e-waste and I jut need to walk away from this mess.

Here is an example of the output i'm seeing on the new firmware in z2m: The "action_level" value ranges from 0-255, and getting that with a timestamp would likely be enough to work with.

{

"battery": 100,

"linkquality": 92,

"update": {

"installed_version": 3090,

"latest_release_notes": null,

"latest_source": "https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images/Hue/Superman_v3_08_ProdKey_3080.ota",

"latest_version": 3080,

"state": "idle"

},

"action": "brightness_move_to_level",

"action_group": 43947,

"action_level": 66,

"action_transition_time": 0.02,

"brightness": null

}

I have a QNAP TS-464 with 2x WD RED 256GB NVME in RAID 1 and 3x WD RED 8TB in RAID 5.

I found a box of my old external HDDs that were just waiting to be recycled and I decided to see if any of them were fucntional. I was a little surprised to find that one of my WD Elements external HDDs was functional so I shucked it. Inside is a 2TB WD Green (WD20EARS-00MVWB0). This HDD was powered on and used for a mac mini media server for some years in like 2010-2016, then sat in a box for about 10 years.

I put this WD Green in the 4th slot on my TS-464 and it passed the long SMART test as well as a "Scan for Bad Blocks".

I plan to use this drive for time machine backups on 2 macs and maybe a few static backups of things.

Is this drive even worth trying? Are there any settings that I can setup on the NAS that would be more favorable to this type of drive? The WD Reds are NAS drives with RAID, so they are doing what they are supposed to do, but the green is a different cheaper animal and I'm worried that the standard NAS behaviour will just kill it quicker than it needs to.

In a different economy I would have just bought another 8TB WD Red, but that ship has sailed and I'm trying to do better with what I have.

I know about this thread: https://community.inovelli.com/t/zigbee-motion-switch-project-linus-bug-enhancement-thread/20438/284

As well as I have found the manual for this device: https://help.inovelli.com/en/articles/8807172-blue-series-mmwave-presence-dimmer-switch-manual

How can I review what the latest firmware version is? Does anyone have any idea when the zha quirk will be officially implemented?

I am running the custom quirk via the directions here: https://help.inovelli.com/en/articles/13019007-blue-series-mmwave-presence-dimmer-switch-zha-custom-quirk-install

A specific concern that brought me here to post is that i'm seeing very high values on the kWh summation delivered values. I have this switch connected to 3 LED light bulbs that draw a max of 40W total. In one hour I often see a summation delivered of 1.2kWh (which is not possible). Further, I see the voltage reported by this device to be around 60V when lights are turned off, and around 120V when the lights are powered on. Maybe this is a firmware issue, or maybe there is something wrong with the quirk, or the way I installed the quirk.

All of this to say that this device generally works well, but it is very hard to find information about the state of this device. It feels like it is just waiting for someone to finish the software and then post some official "state of the device," but that never comes.