Apple has hidden Thread radios in new iPads, MacBooks, and iMacs

AppleInsider

Apple seems to be on the cusp of incorporating Thread in many of its new products without having officially listing it in the product specs yet.

New iPad Air

In 2020, Apple released its first Thread-enabled device, the HomePod mini, and similarly has been introduced in both the HomePod 2 and new Apple TV models.

However, it appears that Apple may soon expand its list of Thread-compatible devices. There are inactive Thread radios in most of its newly launched iPads, MacBooks, and iMacs.

According to The Verge, Apple's put Thread radios in the following models:

• iPad Pro 13-inch (M4) (Wi-Fi + Cellular)


• iPad Pro 11-inch (M4) (Wi-Fi + Cellular)


• iPad Pro 11-inch (M4) (Wi-Fi)


• iPad Air 11-inch (M2) (Wi-Fi + Cellular)


• iPad Air 13-inch (M2) Wi-Fi


• MacBook Air 15-inch (M3)


• MacBook Pro 14-inch (M3)


• MacBook Pro 14-inch (M3 Pro or M3 Max)


• MacBook Pro 16-inch (M3 Pro or M3 Max)


• iMac (M3, two ports)


• iMac (M3, four ports)

Interestingly enough, Apple doesn't actually list Thread on any of the above-mentioned devices' capabilities list, and there is presently no compatibility. However, FCC reports indicate that Apple has tested the Thread radios in its devices for compliance.

As The Verge points out, its a good possibility that Apple may be adding Thread to its devices as a means of future-proofing, as Tri-band chips -- chips that bundle Wi-Fi, Bluetooth, and Thread are becoming more popular.

Thread is an IP-based smart home connectivity standard. Thread-enabled devices create a mesh network that interconnects all the different devices together. With a mesh network, they can all connect and expand their reach further than any single device could on its own.

Additionally, Thread is faster and more reliable than Bluetooth and does not require a hub like competing wireless standards Zigbee and Z-wave. The inclusion of Thread on a device like an iPad or MacBook would enable the devices to work as smart home hubs and improve connection speeds for peripherals.



Read on AppleInsider

hmurchison

All vendors should be required to divulge radios and other communication capable products in their product whether they be dormant or not.   We are placing a lot of trust in purchasing hardware and leaving such items off of specification sheets is a red flag to me. 

Xed

hmurchison said:

All vendors should be required to divulge radios and other communication capable products in their product whether they be dormant or not.   We are placing a lot of trust in purchasing hardware and leaving such items off of specification sheets is a red flag to me. 

1) Are you talking about security?

2) Didn't Apple used to include WiFi or BT chips that included FM in them, but without any of the required antennas or SW attached to make usable? If so, should they also disclose those, even if they're nonfunctional? Couldn't this cause some consumer confusion?

PS: I'm not opposed to increased transparency, but I do wonder if there might be a downside here.

Stiltskin

I did not see the iPad Air 13-inch (M2) (Wi-Fi + Cellular listed. I hope it has the same Thread hardware or I would return it. 

williamlondon

hmurchison said:

All vendors should be required to divulge radios and other communication capable products in their product whether they be dormant or not.   We are placing a lot of trust in purchasing hardware and leaving such items off of specification sheets is a red flag to me. 

It's a conspiracy, put your tinfoil hats on, they're trying to scramble our brains with these hidden antennae. oh ffs.

netrox

That is great news.

Thread is a protocol and we need that to help with improved networking resilience.

Thread requires a low power radio and it needs Matter to automatically adjust networks that are required for users. It is designed for little data to be transmitted and should not be used for mice, keyboard, or anything like that (that's where Bluetooth comes in) but to transmit for devices to ack and send their statuses. It's ideal for home automation and computing networks than data transmission which is where Thread/Matter will notify those devices to use when handshaking for high speed communication.

For example, if home security video is being transmitted, it will never happen in Thread but in WiFi. What would happen is that the Thread enabled device provide Matter the status and the Matter then sends the Thread device (home security camera) with WiFi information which is necessary for high data bandwidth communication and the camera then kicks in WiFi connection and sends video. WiFi itself consumes a lot of power and that's why you don't see many battery-operated WiFi devices.

Thread devices work much better as battery operated and often works as router if it requires constant power (like plugin or complex device requiring high processing resources).

The more thread devices we have, the more robust the network will be.

However, I am not sure if any of those Thread will be "routers" - Apple TV and HomePod are the only ones with the routers.

dewme

netrox said:

That is great news.

Thread is a protocol and we need that to help with improved networking resilience.

Thread requires a low power radio and it needs Matter to automatically adjust networks that are required for users. It is designed for little data to be transmitted and should not be used for mice, keyboard, or anything like that (that's where Bluetooth comes in) but to transmit for devices to ack and send their statuses. It's ideal for home automation and computing networks than data transmission which is where Thread/Matter will notify those devices to use when handshaking for high speed communication.

For example, if home security video is being transmitted, it will never happen in Thread but in WiFi. What would happen is that the Thread enabled device provide Matter the status and the Matter then sends the Thread device (home security camera) with WiFi information which is necessary for high data bandwidth communication and the camera then kicks in WiFi connection and sends video. WiFi itself consumes a lot of power and that's why you don't see many battery-operated WiFi devices.

Thread devices work much better as battery operated and often works as router if it requires constant power (like plugin or complex device requiring high processing resources).

The more thread devices we have, the more robust the network will be.

However, I am not sure if any of those Thread will be "routers" - Apple TV and HomePod are the only ones with the routers.

I completely agree with your take on this. As you said, adding additional nodes will obviously bolster the mesh, but I too wonder what roles are envisioned for the mentioned Apple client devices that have native support for Thread networking using the low powered radios instead of WiFi. Perhaps Apple is envisioning some sort of “Wake on Thread” to allow these devices to turn off their WiFi radio when sleeping, or a Thread based peer-to-peer connection between Apple devices to reduce power draw, if in fact the comm chips/subassembly for each radio are powered separately. We’ll see.

williamlondon

dewme said:

netrox said:

That is great news.

Thread is a protocol and we need that to help with improved networking resilience.

Thread requires a low power radio and it needs Matter to automatically adjust networks that are required for users. It is designed for little data to be transmitted and should not be used for mice, keyboard, or anything like that (that's where Bluetooth comes in) but to transmit for devices to ack and send their statuses. It's ideal for home automation and computing networks than data transmission which is where Thread/Matter will notify those devices to use when handshaking for high speed communication.

For example, if home security video is being transmitted, it will never happen in Thread but in WiFi. What would happen is that the Thread enabled device provide Matter the status and the Matter then sends the Thread device (home security camera) with WiFi information which is necessary for high data bandwidth communication and the camera then kicks in WiFi connection and sends video. WiFi itself consumes a lot of power and that's why you don't see many battery-operated WiFi devices.

Thread devices work much better as battery operated and often works as router if it requires constant power (like plugin or complex device requiring high processing resources).

The more thread devices we have, the more robust the network will be.

However, I am not sure if any of those Thread will be "routers" - Apple TV and HomePod are the only ones with the routers.

I completely agree with your take on this. As you said, adding additional nodes will obviously bolster the mesh, but I too wonder what roles are envisioned for the mentioned Apple client devices that have native support for Thread networking using the low powered radios instead of WiFi. Perhaps Apple is envisioning some sort of “Wake on Thread” to allow these devices to turn off their WiFi radio when sleeping, or a Thread based peer-to-peer connection between Apple devices to reduce power draw, if in fact the comm chips/subassembly for each radio are powered separately. We’ll see.

Is it possible they're keeping those antennae under wraps for now until all supported devices have them, then they can turn on some functionality and all their devices will support it? Could that be a reason, just surmising what might be the reasons they aren't utilising them now.

jcc

hmurchison said:

All vendors should be required to divulge radios and other communication capable products in their product whether they be dormant or not.   We are placing a lot of trust in purchasing hardware and leaving such items off of specification sheets is a red flag to me. 

Why are you complaining about a company giving you extra dormant features? I bet you’re one of those people that once Apple announces some new cool feature, will complain about why they didn’t support down to your device?