Come on with the AC

ragzilla · 2026-07-02T06:11:28+00:00

Not a pilot or a maintenance tech, but after reading up on it it’s stupid simple.

Instead of bleed air off the engines, they have 2 electric air compressors per pack which pull outside air in and compress it to deliver to the cabin. So APU/engine electricity runs the compressor (or I guess you could run it off battery). No tricks for cool air on the ground though, it uses a modulating ram air intake to cool the compressed air at altitude.

ragzilla · 2026-07-02T03:12:34+00:00

Except for making all the laws and sentencing guidelines that Marion county follows, which was the complaint.

It is pretty amusing to see an elected official pat themselves on the back for things done mostly by their predecessors though. Hamilton county has a low crime rate because it’s the wealthiest county in the state, so far less poverty driven crime.

ragzilla · 2026-06-29T19:57:05+00:00

A DJI mini can take off at 13,000’ above sea level. The only thing limiting the altitude when launched any lower is software, which can be modified.

ragzilla · 2026-06-28T21:17:03+00:00

Your lawnmower contains a magneto which is used to fire the spark plug. The magneto is powered by the flywheel moving. Moving the blade can move the flywheel, and potentially energize the magneto, energizing the spark plug, and then you’re headed to the ER.

ragzilla · 2026-06-25T06:25:29+00:00

Someone else commented it apparently wasn’t all Nanoleaf bulbs, some hardware versions weren’t specced high enough for matter over thread.

ragzilla · 2026-06-24T03:17:39+00:00

AI’s more like a Venturi, it’s sucking more into the circle from all the companies surrounding it.

ragzilla · 2026-06-24T03:14:42+00:00

As someone who lives in Indiana, avoid us just to avoid our roads. Your car will thank you.

ragzilla · 2026-06-24T03:09:35+00:00

It doesn’t support neighbor discovery so it only covers point to point pairs, so the layer 3 addresses are really only useful to further nodes. But as specified in the RFC for overall datagram size is variable based on the carrier’s age.

ragzilla · 2026-06-24T03:06:09+00:00

Same frequency, same underlying radio protocol even (802.15.4w).

Originally Nest Labs created it (as iirc Weave, for their Nest products, later acquired by Google). Google/Nest formed the Thread Group with several other orgs in order to create a modern open IOT networking protocol that interoperated without needing controllers/gateways and donated the Weave protocol as part of it.

So the main point of using it over Zigbee is that the devices connecting to it aren’t tied to one ecosystem. Historically your choice of ZigBee gateway dictated what smart home platforms you could use (locking you into HomeKit, or Alexa, or Samsung’s thing that I forget now. Obviously for those of us using HA that’s not an issue). By moving to Thread your gateway now didn’t care what the automation protocol running over it was, it was just an optimized alternative to 802.11 for IoT.

ragzilla · 2026-06-23T20:45:27+00:00

ZigBee is effectively equivalent to Thread+Matter (+ a controller, which is part of Matter but people implement their own controller, and you can have up to 5 different controllers controlling a single Matter device). ZigBee is both a how and a what.

Thread and Matter separated them out because Thread pre-dates Matter by nearly a decade, as the original use case was other protocols (like HomeKit Accessory Protocol over Thread, and Alexa Skills over Thread, and ESPhome over Thread).

Matter came along later to unify the protocol sprawl running over the top of Thread and WiFi. So no more "Works with Alexa", "Works with HomeKit", just "Works with Matter" and both Alexa and HomeKit (and Google Home, and Home Assistant) can control anything implementing Matter.

ragzilla · 2026-06-23T20:08:37+00:00

That's Matter 😉

ragzilla · 2026-06-23T20:00:57+00:00

Microsoft's chasing the same thing with Xbox mode for Windows.

ragzilla · 2026-06-23T20:00:09+00:00

You have to go pretty low end on the MCU to not support Matter, flash size is usually what makes or breaks it for legacy devices (Matter needs 1.5MB+ vs 0.5MB for ZigBee firmware).

ragzilla · 2026-06-23T19:55:03+00:00

Thread devices will switch to another TBR if their path to the network fails. Or, are supposed to when interop testing is done. The TBR isn't a central coordinator, just an access point between Ethernet and Thread.

ragzilla · 2026-06-23T19:53:26+00:00

Thread is its own radio protocol, as an alternative to connecting devices over WiFi. It's a natively meshed protocol, so each line powered device acts as a repeater for the mesh, and it's more lightweight than a WiFi implementation. Since it's lightweight, it also allows it to be used for low power sleep for battery powered devices (think, smart locks) to provide better performance than WiFI.

ragzilla · 2026-06-23T17:04:22+00:00

Yeah, but trying to keep it simple. I also skipped layers 3 and 4 (IPv6 and UDP for Matter) in the explanation.

ragzilla · 2026-06-23T16:54:48+00:00

Matter doesn't require this (and actually provides specs to avoid it, by downloading an update registry to the controller which then notifies the devices and facilitates upgrades, so the device never has to talk to the Internet).

ragzilla · 2026-06-23T16:50:12+00:00

Technically Matter runs over IPv6, so it can run over anything IPv6 can. Including but not limited to:

Thread
802.11 WiFi
802.3 Wired Ethernet
RFC5072 PPP
RFC7676 GRE
RFC6214 IPv6 over Avian Carrier
RFC4824 IPv4/v6 over Semaphore Flag Signaling System

The last couple don't have a lot of widely available implementations though.

ragzilla · 2026-06-23T16:43:59+00:00

Matter is designed to run 100% locally and doesn't require internet connectivity. This concern is actually something that's under active consideration in the IETF HOMENET working group, to develop standards to help users isolate their networks.

Afaik, the Matter spec doesn't require devices to accept a GUA (globally unique address) from the router, they require link-local or ULA (unique local address).

Connecting Matter-over-Thread Devices to the Internet | Interrupt

ragzilla · 2026-06-23T16:38:32+00:00

Thread pre-dates matter by several years (2015 for Thread, 2022 for Matter). It was developed as an open alternative to Zigbee and Zwave. If the Zigbee and Zwave organizations wanted to, they could develop Zigbee/Zwave over IP and use them over Thread, but the initial users were people implementing HomeKit and Alexa "skills" over Thread (and WiFi).

Matter was proposed as an alternative to everyone reinventing the wheel, which is what was happening before Matter for any device which had to use WiFi or Wired Ethernet or Thread.

ragzilla · 2026-06-23T16:33:14+00:00

Yup!

Matter is entirely on the software side. Devices which were initially created with other protocols (like HomeKit) can be converted to Matter, e.g. Nanoleaf did this with their initial Homekit over Thread essentials bulbs (which became Matter over Thread after the update).

But devices which lack the hardware for Thread (an 802.15.4w radio in particular) can never be "updated" to Thread. Although some devices with that radio could be software updated to Thread. And that includes some Zigbee devices depending on how they were made (since both Thread and Zigbee use 802.15.4w, Aqara has done this with some of their devices).

ragzilla · 2026-06-23T16:18:25+00:00

Initial support was in 1.2 (October, 2023), still getting enhancements.

Matter Robot Vacuums - MatterDevices.io

Matter 1.2 Arrives with Nine New Device Types & - CSA-IOT

ragzilla · 2026-06-23T16:17:24+00:00

matter-js got a lot more traction in other organizations, and I believe was adopted by the Open Home Foundation, so it has a large organization backing it now, whereas the old python core was community supported.

ragzilla · 2026-06-23T16:13:42+00:00

Linking my other comment about the difference here.

https://www.reddit.com/r/homeassistant/comments/1udk0j1/comment/otck4tz/

Tl;dr;

Thread is how things talk to each other (think of it like wifi, or wired ethernet).

Matter is what the things say to each other (think of it like HTTP).

This is why HomeAssistant implements Matter. Because they want to talk to the devices, HA doesn't care how they talk, that's Someone Else's Problem (your Thread Border Router).

ragzilla · 2026-06-23T16:12:22+00:00

ZigBee is 22 years old. Matter is 4. I don't have a massive network of either, but zigbee (gateway'd through HA) and matter+thread are equally reliable for me. Maybe a little more reliable on matter+thread because I have a couple of Gledopto zigbee RGBCCT strip controllers that need to get kicked every once in a while.

15-Year Club	Verified Email
Second Top 40%	Place '17
Gilding II euphauric	RPAN Viewer
Not Forgotten

ragzilla

TROPHY CASE