Possibly. I have been unable to even connect my new LG fridge to the Internet.
.
But basically I was referring to end 2022 when the IKEA Dirigera hub seemed to be a leading Matter contender. ST delivered, with some setbacks but Ikea did not. Might be wrong but I don’t remember much from LG at that time.
Timeline for Matter development may refresh your memory 
tagging @Automated_House
I hope so! Would be good to see them go the Aqara route with both Thread and Zigbee support.
A first look at IKEA’s new home smart products 2026
I’m SO curious about the IKEA button with wheel and how they’ll expose the wheel to Matter.
It’s clearly a dimmer switch, so they probably support Matter bindings, although they use TouchLink for their own lights so maybe they don’t need bindings.
And if they use the “Generic Switch" approach (buttons with events), Matter has no events for wheels, and we’ve seen in the past how other manufacturers only exposed the main switch events (pressed) but not the wheel / dial.
Who knows, maybe in Matter they’ll also require custom drivers for the whole functionality 
.
I would trust IKEA to implement Matter binding because they are building an entire Matter ecosystem. If I remember correctly, dealing with ACLs is quite complicated.
The Matter binding concept is cross-manufacturer. In theory, at least, products from different brands can be combined. However, widespread adoption has so far been hindered by the major Matter platforms. They would first need to enable their Matter controllers to make corresponding entries in the devices’ access permissions. ACLs regulate who is allowed to communicate with whom in an encrypted Matter Fabric. The guy from Eve Systems explained it to me and he said that you can make serious mistakes when manipulating ACLs
With an own ecosystem of controllers and devices, this becomes much simpler.
We’ll see…
Aeotec plans to discontinue (selling the) V3 at the end of 2026
new Switchbot AI hub
Specs-wise, the AI Hub is a big upgrade over the Hub 3, featuring dual-band Wi-Fi, extended Bluetooth, and 32GB of built-in storage (expandable to 1TB). It can manage up to eight 2K cameras, stream locally via RTSP, and display footage on a monitor. The hub can support more than 100 SwitchBot devices and bridges up to 30 products into a Matter ecosystem. It’s powered by a 6T AI chip.
Firmware update for Tapo H110: Matter 1.3
Source: Reddit
I’ll update my H110 hubs later today and report back.
Edit: Matter bridged water leak sensors!
Hope it’ll report the battery level…
Checked the CSA Compliance Document and it doesn’t support battery… Looks like the Matter sensor driver is the culprit…
There’s no profile for Matter leak sensors without battery:
local function match_profile(driver, device, battery_supported)
local profile_name = ""
if device:supports_capability(capabilities.waterSensor) then
profile_name = profile_name .. "-leak"
end
if battery_supported == battery_support.BATTERY_PERCENTAGE then
profile_name = profile_name .. "-battery"
elseif battery_supported == battery_support.BATTERY_LEVEL then
profile_name = profile_name .. "-batteryLevel"
end
-- remove leading "-"
profile_name = string.sub(profile_name, 2)
device.log.info_with({hub_logs=true}, string.format("Updating device profile to %s.", profile_name))
device:try_update_metadata({profile = profile_name})
end
local function do_configure(driver, device)
local battery_feature_eps = device:get_endpoints(clusters.PowerSource.ID, {feature_bitmap = clusters.PowerSource.types.PowerSourceFeature.BATTERY})
if #battery_feature_eps > 0 then
local attribute_list_read = im.InteractionRequest(im.InteractionRequest.RequestType.READ, {})
attribute_list_read:merge(clusters.PowerSource.attributes.AttributeList:read())
device:send(attribute_list_read)
else
match_profile(driver, device, battery_support.NO_BATTERY)
end
end
@nayelyz Can you please ask the team to add the missing leak (without battery) profile to the Matter Sensor driver?
Fixed with this PR!
Matter, Thread Border Router, Zigbee, no Zwave. 
Also
>connect up to 300 devices
Hi, @Andreas_Roedl
The engineering team also saw this issue opened today:
So, they’ll work on it and put up a PR adding other profiles, including this one.
Thank you for bringing this to our attention.
While they’re at it, since it’s the same matter-sensor driver, are they going to add sensitivity support for contact and occupancy sensors? There are already devices in the market supporting it like the Aqara sensors.
I reported that a few days ago but since I got no feedback I don’t know if they’re aware or not:
For the sensitivity in particular, drivers almost support it but somehow for contact sensors the implementation is not finished (“N/A”) and for motion/occupancy sensors there’s no support when the Matter attribute is the same.
Note that a motion/occupancy sensor is not a Boolean State device type but Matter 1.4 specifies that sensitivity for occupancy sensors must be set with the Boolean State Configuration too:
add sensitivity setting (via co-located BooleanStateConfiguration cluster on same endpoint))