I’m trying to troubleshoot a HK issue (HomeBridge not talking to HK after OS updates). I’ve pulled out my spare ATV, which is running tvOS 18.1, and powered it up. It’s on the network, but HK says its status is “No Response”.
Is 18.1 too old to work in my HK ecosystem?
It’s my turn to have the “Updating…” issue
It’s OS updating day, and whether it’s a coincidence or not, about half of my IoT devices are showing “Updating…” in Home. I’ve rebooted my router, no change. My active HK hub is an Ethernet ATV which was updated.
Looking at devices in HomeBridge, they are controllable via HB but not in Home. It appears that the affected devices are all HB and across multiple plugins.
Power cycling devices did not help, nor power cycling the ATV HK hub. Router rebooting has always fixed this in the past. I also rebooted the HB service, no change.
Ideas? I could try rebooting the HB server.
It’s OS updating day, and whether it’s a coincidence or not, about half of my IoT devices are showing “Updating…” in Home. I’ve rebooted my router, no change. My active HK hub is an Ethernet ATV which was updated.
Looking at devices in HomeBridge, they are controllable via HB but not in Home.
I could try power cycling to see if that helps? Not sure what else to try. Router rebooting has always fixed this in the past. I also rebooted the HB service, no change.
UPDATE: this is clearly a HomeBridge issue. Non-HB devices are fine.
I'm seeing a lot of this since updating to 2.x (currently on 2.0.2):
Encountered MDNS socket error on socket 'wg0' : Error: send Unknown system error -126 224.0.0.251:5353
at doSend (node:dgram:764:16)
at defaultTriggerAsyncIdScope (node:internal/async_hooks:472:18)
at afterDns (node:dgram:703:5)
at processTicksAndRejections (node:internal/process/task_queues:91:21)
A brief search shows that this was an issue way back in the 1.2.x days.
"Bonjour HAP" is the mDNS advertiser, if that's relevant.
Platform is Rpi 3 running debian bookworm.
Any thoughts?
Update: I read the docs (RTFM) and switched to Avahi mDNS, will monitor.
I’m currently riding with a Fox full face helmet, I’m looking for something more casual for everyday riding. I just picked up a Xnito (no LBS, had to Amazon), I love how light it is, but the rear cradle clamps down on the top of my spine, which hurts like hell. It looks like modern MIPS or NTA 8776 have this design in common.
Any recommendation for well rated helmets that don’t have a cradle that drops way down in back?
I have very high arches, Green Superfeet aren’t high enough. I have custom orthotics ordered, but it will be several weeks until they arrive. I’m hoping to find over the counter orthotics that have high arch support to fill the gap until the customs arrive.
Any ideas? There are dozens of similar orthotics on Amazon, no idea which actually support high arches.
I’ve been obsessively researching lightweight e-bikes for a few weeks, the Soltera 2.5 with a couple of mods (tires, shifter) looks like it a solid candidate. I’m in a coastal area with only one LBS, and they’re a Aventon dealer, which is a plus for me vs Velotric and Ride1up.
Went to visit the local shop today, asked about the 2.5, he wheeled out a 3 Adv and said he didn’t like the 2.5 and wouldn’t carry it. Ok. I guess we’re done there.
If the local dealer won’t sell the bike, have I lost the advantage of having a local Aventon dealer?
FWIW, I was very impressed with the light weight and appearance of quality of the 3 Adv. Although the screen is minuscule, so it wouldn’t do me much good. And I’m not interested in a single speed.
i've just updated one of my RPi systems from debian bookworm to trixie. I notice that I still have a raspi.sources file in /etc/apt/sources.list.d , which contains:
Types: deb
URIs: http://archive.raspberrypi.com/debian/
Suites: trixie
Components: main
Signed-By:
which causes apt update to cough up a hairball.
There doesn't appear to be anything current in http://archive.raspberrypi.com, is it correct to imply remove this file? is there a trixie-compliant config file, or is this simply obsolete?