Smarthome Forum — Smart Home Community for Matter, Zigbee & HomeKit

Sarah_D

When I started moving my heating over to Zigbee, I assumed choosing a thermostat would be the easy part. Pick one with good reviews, pair it, done. It turned out the thermostat itself mattered a lot less than whether it actually matched my heating system and my hub. I ended up returning one before I got it right, so here’s what I learned along the way.

Start with your heating system, not the brand

This was my first mistake. Not every Zigbee thermostat works with every type of heating, and the categories are pretty different:

Central HVAC (24V): your typical furnace or heat pump setup. Most wall thermostats are built for this.
Electric baseboard or radiant floor (line voltage): needs a thermostat rated for high voltage. A standard 24V unit will not work here and can be dangerous to wire in.
Water radiators: you don’t need a wall thermostat at all. A Zigbee TRV (thermostatic radiator valve) mounts directly on each radiator and gives you room by room control.

If you only check one thing before buying, check this.

Check for a C-wire

A lot of 24V thermostats want constant power through a C-wire. My hallway didn’t have one. Your options if you’re in the same boat:

Go with a battery-powered model
Use a thermostat that ships with a power extender kit
Run a new wire if you’re comfortable doing it (or get an electrician)

Make sure your hub actually supports it

Zigbee thermostats don’t connect to your router, they join your mesh through a coordinator. I run Home Assistant, and most of the models I looked at work through either Z2M or ZHA, but device support isn’t identical between the two. Before buying, I’d search the Z2M supported devices list or the ZHA quirks for the exact model number. Zigbee 3.0 certified devices generally give you the fewest headaches.

Why I went Zigbee instead of Wi-Fi

Schedules and automations keep running locally when the internet drops
Mains-powered thermostats act as routers, so they actually strengthen the mesh
Response to automations felt noticeably quicker than the cloud-based unit I had before

One heads up: if your thermostat is battery powered, it’s an end device, not a router. It won’t help your mesh, and it needs a decent router nearby to stay reliable. Worth checking the LQI after pairing.

Models worth a look

While researching, I found this breakdown of the best zigbee thermostats really useful because it splits recommendations by heating type instead of just ranking everything together. A few that stood out for different setups:

Sinope TH1124ZB: for electric baseboard heating, also reports energy usage
SONOFF TRV: for radiator systems, works well with Home Assistant
Centralite Pearl: a budget-friendly option for standard 24V systems
Aqara W100: if you’re already in the Aqara ecosystem
Third Reality: simple battery-powered option with a local LCD readout

Note that the Stelpro KI, which a lot of older threads recommend for baseboard heaters, has been discontinued, so don’t count on finding it new.

My quick checklist before buying

Confirm heating type (24V, line voltage, or radiators)
Check whether you have a C-wire
Look up the exact model in Z2M or ZHA support
Decide if you want it acting as a router (mains powered) or not

Curious what everyone else is running. Has anyone had trouble getting a thermostat’s setpoint or mode to sync properly in Z2M? That’s the one area where I’ve seen the most inconsistency between models.

Amanda Jones

I've been poking around the Home Hubs screen in the Home app more than usual lately, and with Apple reportedly about to show off its long-delayed home hub, it feels like the right time to ask: what are you all running as your apple homekit hub right now, and what would actually make you switch?

My current setup
• HomePod mini in the living room acting as the connected hub
• Apple TV 4K in the bedroom sitting on standby
• Home Assistant running alongside, with my Zigbee network on an SLZB-06M and a handful of sensors exposed to Apple Home through the HomeKit Bridge integration

It works well most days. But living with it has shown me exactly where the gaps are.

Where my hub setup falls short today
• No say in which device is the hub. Apple picks it for you. When my HomePod mini had a Wi-Fi hiccup, remote control and a couple of automations stalled until the Apple TV took over.
• Thread is a black box. Both devices are Thread border routers, but the Home app tells me almost nothing about which one my Matter over Thread devices are actually using or how healthy that network is.
• No good wall control. I have an old iPad on a kitchen stand, but iPads can't act as a home hub under the newer Home architecture, so it's just a remote with a battery I keep forgetting to charge.
• Bridged devices feel second class. My Zigbee sensors show up fine, but there's no glanceable view that pulls everything together in one place.

What's been reported about Apple's new hub
Nothing is official until Apple announces it, so treat all of this as rumour for now:
• A roughly 6 to 7 inch square display
• Two versions: a countertop model with a design that reportedly nods to the old iMac G4, and a wall mount version that needs to stay plugged in
• A front camera for FaceTime, plus voice and face recognition to show personalised content to whoever walks up
• A new Siri AI based operating system with Apple's own apps built in, but no App Store at launch
• Price talk in the region of $350
• A new HomePod mini and Apple TV 4K expected alongside it

My wishlist
• Let me choose the primary hub. Even a simple "prefer this device" toggle would save a lot of head scratching.
• Thread border router and Matter controller built in, with real diagnostics. Show me which devices route through what.
• Local first. Automations should keep running when the internet drops, full stop.
• A wall mount without a dangling cable. Power over Ethernet would be a dream, a tidy in-wall option would be fine.
• A proper device dashboard, including Matter and bridged devices, not just Apple widgets.
• Privacy controls I can see. Face recognition processed on device and a physical way to kill the camera.
• A price that makes sense. If it lands near $350, it has to do a lot more than an Echo Show or Nest Hub to earn a spot on my counter.

Over to you
• Which device is your HomeKit hub right now: HomePod, HomePod mini, or Apple TV?
• Anyone else running Home Assistant or Homebridge alongside Apple Home? How are you bridging things in?
• Day one buy, wait for reviews, or skip?
• If you could add one feature to Apple's hub, what would it be?

Curious to see what everyone's running. Drop your setup below, even if it's just one HomePod mini doing all the heavy lifting.

For transparency, I'm on the forum staff team here, but genuinely asking this as someone trying to sort out their own setup!

Amanda Jones

I've been reworking the cameras around my place over the last few weeks, and it made me realise how differently everyone seems to approach this. Picking a homekit camera sounds simple until you actually try it, and then you find there are really three separate routes with very different trade-offs.

So I'm curious: which HomeKit cameras are you running, and how did you get them into Apple Home?

Here's how I see the three camps, and where I've landed so far:

1. Native HomeKit cameras

These are the ones you scan with the Home app and you're done. No extra hardware, no plugins.
• Setup takes minutes and they tend to stay paired
• Live view, notifications and automations work out of the box
• The catch is choice: the list of native models is short, and outdoor and PoE options are thin

I started here with an Aqara Camera Hub G2H Pro in the hallway. It has been the least trouble of anything I own, but I ran out of options quickly once I wanted something outside.

2. HomeKit Secure Video (HKSV) models

This is where it gets interesting for recording. Footage is analysed locally on your home hub, then stored end to end encrypted in iCloud.
• You need a home hub (Apple TV or HomePod) and an iCloud+ plan
• The plan tier sets how many cameras can record, so check that before you buy a fifth camera
• Recordings don't count against your iCloud storage
• Person, pet, vehicle and package detection, plus activity zones, are handled in the Home app

What I like is having one timeline in one app. What I don't like is that recording tops out at 1080p even on a higher resolution camera, and clips sometimes take a while to load when I'm away from home.

3. Bridge-based setups (Homebridge, Scrypted, RTSP)

This is the route for cameras that were never meant to work with HomeKit. If the camera exposes an RTSP or ONVIF stream, you can usually bring it in.
• Opens up far more hardware, including PoE and proper outdoor cameras
• Scrypted can add HKSV support to cameras that don't have it natively
• Homebridge with a camera plugin works well for live view and motion alerts
• The trade-off is that you are now running a server, so updates, codecs and stream settings become your job

My outdoor camera is a Reolink E1 Outdoor Pro coming in over RTSP through Scrypted. It took an evening of fiddling with stream settings before it loaded quickly, but it has been steady since.

What I'd love to hear from you

• Which cameras are you running, and which of the three routes are they on?
• If you use HKSV, how reliable are the notifications and the detection?
• For the bridge crowd: Homebridge or Scrypted, and what hardware is it running on?
• Any camera you regretted buying, and why?
• Has anyone mixed all three in one home without it turning into a mess?

For transparency, I'm on the forum team here, but I'm asking this one as someone still trying to sort out their own setup.

Amanda Jones

Hi all, this is a genuine discussion question, not an announcement. Nothing to sell and no links to follow.

iOS 27 has been out for a few weeks now, and HomeKit Secure Video got more attention in this release than it has in years. I've read plenty of feature lists, but feature lists don't tell you how it holds up on a real front porch with a real camera. So I'd like to hear from people who are living with it.

The redesigned camera experience

The Home app now handles recordings differently. Clips it considers important are pulled to the top, and related alerts are bundled into one notification that updates as things happen.

Does the new layout make it faster to find the clip you want, or are you scrubbing more than before?
Are the "important" clips actually the important ones?
Has the notification bundling cut the noise, or have you missed something because of it?

4K cameras

The 1080p cap on HomeKit Secure Video is finally gone, as long as the camera supports it.

Is anyone actually recording in 4K yet? Which camera, and did it need a firmware update first?
Can you see a real difference on faces and number plates, or only when you zoom in?
Any impact on your Wi-Fi, upload speed, or how smoothly clips load?

Apple Intelligence summaries and natural-language search

This is the part I'm most curious about. The Home app can now describe what happened in a clip before you open it, and you can search recordings by typing what you're looking for.

How accurate are the summaries? Useful, or confidently wrong?
Has natural-language search found things for you that scrolling would not have? What did you search for?
Did your iPhone, home hub, or iCloud+ plan stop you from turning any of this on?

What I'd love to know

Your camera model and home hub (Apple TV or HomePod)
The one change you'd keep and the one you'd undo
Anything that broke or got worse after updating

Short replies are welcome. "Nothing changed for me" is a useful answer too, especially if you can say what setup you're on.

Thanks in advance. I'll be reading and replying in the thread.

Sarah_D

I picked up the SONOFF Bridge Max (model Bridge-M) to replace an aging gateway, and wanted to share some honest impressions for anyone weighing it as their next Zigbee hub or a way into Matter without a full ecosystem swap.

What it actually is

Bridge Max is positioned as an all-in-one Matter Bridge and Zigbee gateway. It runs on a SigmaStar SSD2351Q chip paired with an EFR32MG21 for the Zigbee radio, supports both 2.4GHz and 5GHz Wi-Fi plus Ethernet (RJ45), and powers over USB-C at 5V/1A. It's small, just 82x82x28mm, so it tucks away easily near your router or wherever your mesh is centered.

Setup and first impressions

You can power it up over Wi-Fi through the eWeLink app or just plug in Ethernet for zero-config networking, which I'd recommend if you want the most reliable backbone for your mesh
There's a local web interface too, so you can bridge devices over LAN without touching the cloud at all. That's a genuinely useful option if privacy or offline reliability matters to you
If you're migrating from a ZBBridge Pro, there's a one-step transfer for devices, scenes, and security settings, which saves you from re-pairing everything. Worth noting it currently only supports migrating from the ZBBridge-P, not the Ultra or an iHost
Pairing new Zigbee devices through the app was straightforward. Nothing fancy, just the standard scan-and-join flow

Zigbee performance

SONOFF rates the Bridge Max for up to 128 Zigbee devices for stable performance, with more technically possible but at some cost to reliability. That's a reasonable ceiling for most home setups, though anyone running a large mesh with dozens of routers and sensors will want to plan around it.

One thing worth flagging before you buy: some reviewers have reported devices dropping off if they're more than a couple meters away with obstacles in between. SONOFF's own guidance here is to check each device's RSSI (anything below -65 is a weak signal) and add a Zigbee repeater if you're seeing drops. That's standard mesh advice, but it means this isn't a bridge you can treat as plug-and-forget in a larger or more spread-out home. Budget for a router device or two if your layout has any dead zones.

The Matter Bridge piece

This is really the headline feature. Bridge Max can take Zigbee, BTHome, and eWeLink devices and expose them to Apple Home, Alexa, Google Home, SmartThings, and Home Assistant through Matter. A couple of practical notes:

The web interface is Matter-setup only. You can't control devices directly from it, so day-to-day control still goes through the eWeLink app or whichever Matter platform you bridged into
If you're already running Home Assistant, you can skip Matter entirely and sync Zigbee devices over MQTT instead

Who this makes sense for

Anyone wanting a single box that bridges Zigbee devices into Apple Home or another Matter ecosystem without buying a dedicated Matter hub
Anyone upgrading from a ZBBridge Pro who wants a clean, one-step migration
Home Assistant users who want the option of both an eWeLink/Matter path and a straight MQTT sync

Where it falls short

128 devices is the practical ceiling for stable operation, so larger networks will want a dedicated coordinator instead
The local web console is setup-only, not a full control dashboard, which might frustrate anyone expecting to manage devices from it
Range with obstacles is a real consideration. Don't expect it to cover a sprawling floor plan without help from routers

Buy here: https://zigbeehubs.com/shop/products/sonoff-bridge-max-bridge-m/

Sarah_D

I finally pulled the trigger on the Inovelli Blue Series Zigbee fan switch after seeing it mentioned a few times in this community, and I wanted to write up my honest experience now that it's been running for a while.

What it actually is

The VZM35-SN is an in-wall fan switch, not a canopy module. It replaces your existing wall switch and gives you variable fan speed control for AC fan motors, though it's not compatible with DC motor fans. If your fan also has a light kit, this specific switch won't handle that. Inovelli's line has a separate Fan/Light Canopy Module for fans that need both fan and light control from one device.
Inovelli
Inovelli

Installation

This is an in-wall install, and a neutral wire is required for proper operation
ZWaveProducts
If you're not comfortable with electrical work, I'd second Inovelli's own recommendation and get an electrician involved
Max load is rated at 2.5 amps, and Inovelli specifically says not to run more than two identical fans off one switch, and not to exceed that resistive load
Inovelli Help Center
It is not rated for lighting loads like LED, CFL, or incandescent, so don't try to sneak a light circuit onto it

Pairing and hub compatibility

Paired cleanly on my Zigbee2MQTT setup through my SLZB-06M. Inovelli confirms support across SmartThings, Home Assistant ZHA, Home Assistant Zigbee2MQTT, Hubitat, and Amazon Echo, so compatibility isn't a concern regardless of what you're running.
Inovelli Help Center

Speed control in Z2M

This is where the switch earns its reputation. Because it implements the actual Zigbee Fan Control cluster rather than just basic on/off commands, it exposes real discrete speed levels instead of just a single toggle. In Z2M this shows up cleanly as a proper fan entity with distinct speed steps, not the flaky pseudo-dimming you get from some cheaper AC fan controllers that just chop the sine wave.
Alibaba

The parameter depth is the real story

This is the part that separates it from generic Zigbee fan modules:

There's a Breeze Mode feature that cycles between Low, Medium, and High to simulate natural airflow, and the same mechanism can be flipped around into a "Wind Down Mode" that ramps the fan down from High to Low over a set time
Inovelli Help Center
There's a Fan Module Binding Control option that lets you use the config or favorites button as a binding endpoint, handy if you want a second physical control point without adding another device
Inovelli Help Center
Overall the switch ships with dozens of tunable parameters, which is more than I've seen on any other Zigbee fan device

Zigbee mesh impact

Since it's mains powered it acts as a router on the mesh. After adding it I checked my network map and it picked up a solid LQI link back to the coordinator, and it's now sitting as a hop point for a couple of battery sensors nearby, similar to what I've seen with other in-wall Inovelli switches.

A few caveats

If your fan has an integrated light, this specific switch is the wrong pick. Look at the canopy module instead
Neutral wire is mandatory, so older homes without one at the switch box are out of luck unless you can pull new wire
This works with Inovelli's own Aux Switch or another Inovelli smart switch for multi-way setups, but it will not work paired with an existing dumb switch, so plan your wiring accordingly if you have a 3-way setup
Inovelli

Bottom line

If you want proper multi-speed Zigbee fan control with real automation depth rather than a basic on/off relay, this is the switch to get. The parameter list alone makes it worth the price over cheaper alternatives, and the fact that it plays nicely with Z2M and ZHA without quirks or custom converters made setup painless. My only real regret is not doing this years ago.

Sarah_D

I had two devices in my house that refused to join the smart home party: a window AC unit and a ceiling fan, both only controllable by their little IR remotes. I didn't want another app, another remote, or a bunch of tape holding a remote hostage in front of the unit. So I picked up a Zigbee IR blaster and got them both onto my existing mesh. Here's how it went.

Why a Zigbee IR blaster instead of a standalone WiFi one

I already run Zigbee2MQTT on an SLZB-06M, so this was less about the tech and more about not wanting a third ecosystem in the house.

No separate app or cloud account
Joins the same mesh as the rest of my routers and sensors, so LQI and coverage benefit from devices I already have
One coordinator to manage instead of juggling WiFi devices with their own quirks

Setup, start to finish

Paired it in Z2M like any other device (put it in pairing mode, hit permit join, it showed up within a few seconds)
Placed it with a clear line of sight to both the AC and the fan, about 2 meters from each, since IR still needs line of sight even though the mesh side is wireless
Used the "learn" function in Z2M to capture each button from the original remotes, one at a time (power, temp up/down, fan speed, swing)
Named each captured command something sane in Z2M so I wasn't guessing which "IR code 4" did what six months later

The line-of-sight gotcha nobody warns you about

Zigbee mesh doesn't care about walls and IR very much does. I first put the blaster on a shelf that had a clean shot to the fan but was partially blocked from the AC by a bookshelf. Commands to the fan worked instantly, the AC would randomly miss maybe 1 in 5 commands. Moving the blaster about a foot to clear the sightline fixed it completely. Worth testing each command a few times right after setup rather than assuming it works because it worked once.

What this actually got me in Home Assistant

AC now turns off automatically when a window sensor in that room opens
Fan speed ties into a temperature automation instead of me getting up to adjust it
Both show up in the same dashboard as everything else, no separate card for "the IR stuff"

A couple of things I'd tell someone starting this

Capture every button you think you might ever want before you put the original remote in a drawer. I had to dig mine back out once because I forgot to capture "swing mode."
If you have more than one IR device in the same room, check for command collisions. Universal remote codes sometimes overlap between brands.

Anyone else running old AC units or fans through Zigbee IR blasters? Curious what devices you've resurrected this way.

Sarah_D

If you've ever opened Home Assistant and seen half your Zigbee devices marked unavailable, you know how frustrating it is. I went through this myself a few months back, losing motion sensors and plugs at random, sometimes for hours at a time. Here's what I learned tracking it down, in case it saves someone else the same headache.

Start with the network map, not the device

My first instinct was to reboot the offline device. That almost never fixed anything. What actually helped was pulling up the network map in Zigbee2MQTT (or the visualization in ZHA) and looking at how that device was routing. Devices that had lost their route to a router, or were trying to hop through a router that had itself gone flaky, were the ones dropping out. The map told me where the actual problem was instead of me guessing device by device.

Battery devices are not the same problem as mains-powered ones

I used to lump all my offline devices into one bucket, but battery sensors and mains-powered plugs fail for completely different reasons. Battery devices sleep most of the time and only report in on a schedule or when triggered, so a sensor that looks offline might just be low on battery or waiting for its next check-in. Mains-powered devices, on the other hand, are always-on routers for the mesh, so when one of those goes offline it can take a chunk of your network down with it since other devices were relying on it to relay.

Interference was my actual culprit

In my case, the real issue was my Zigbee coordinator sitting a few inches from a USB 3.0 hub. USB 3.0 is a known noise source in the 2.4GHz range, and it was quietly wrecking my signal without any obvious symptom other than random dropouts. Moving the coordinator onto a USB extension cable, away from the hub and my router, cleared up most of my problems immediately.

Channel congestion sneaks up on you

I also checked my Zigbee channel against my Wi-Fi channels, since overlap between the two causes intermittent packet loss that looks exactly like random offline devices. Switching to a Zigbee channel that didn't overlap with my 2.4GHz Wi-Fi channel helped stabilize the last few stragglers.

Give the mesh time before you panic

After making any change, whether it's adding a router device, moving the coordinator, or switching channels, I had to resist the urge to judge results immediately. The mesh needs time to rebuild its routes, sometimes several hours. I made the mistake of assuming a fix didn't work after ten minutes, when really the network just hadn't finished reorganizing yet.

What actually fixed it for me, in order

Moved my coordinator away from USB 3.0 interference
Added two router devices in the areas where I was seeing the most dropouts
Switched to a less congested Zigbee channel
Let the mesh sit overnight before checking again

Between those four changes, my offline device count went from a near-daily annoyance to essentially zero. If you're chasing the same problem, I'd start with the network map and the coordinator placement before touching anything else. Those two things caused the majority of my issues.

Sarah_D

I see this question pop up a lot, so figured I'd break down how I think about it after running both ZHA and Z2M on different setups.

Zigbee itself

Zigbee isn't software you choose, it's the wireless protocol your devices speak. Every bulb, sensor, and plug that says "Zigbee" on the box is talking the same low-power mesh protocol regardless of what's running on your Home Assistant server. The protocol handles the radio layer, pairing, and mesh routing between devices. What you do choose is the software that sits between your Zigbee coordinator (the USB stick or gateway) and Home Assistant, translating Zigbee traffic into something HA understands. That's where ZHA and Z2M come in.

ZHA (Zigbee Home Automation)

ZHA is Home Assistant's built-in integration. No separate app, no extra container, no MQTT broker to manage. You plug in a coordinator, add the integration, and pair devices straight from the HA UI.

What I like about it:

Setup is genuinely the fastest of the two. Fewer moving parts means fewer things to misconfigure.
Device support is handled through quirks, community-contributed device profiles that patch weird or non-standard implementations.
Everything lives inside HA, so there's no second web UI to check when something's not reporting.

Where it falls short:

Network visibility is limited. There's no built-in map showing which devices are routing through which repeaters, so diagnosing mesh problems is more guesswork.
Some devices get supported later than they do on Z2M, since the quirks system depends on community contributions catching up.

Zigbee2MQTT (Z2M)

Z2M runs as a separate add-on (or standalone service) and talks to HA over MQTT rather than being built into HA directly.

What I like about it:

The network map in the Z2M frontend is genuinely useful. You can see LQI (link quality) between every device and repeater, which makes tracking down a flaky sensor way faster than guessing.
Broader and often faster device support, especially for newer or less common devices.
More granular control over channel settings, reporting intervals, and per-device configuration.

Where it falls short:

You're now running MQTT as a dependency, which is one more thing that can go wrong or need troubleshooting.
Slightly more setup overhead upfront, especially if you've never touched an MQTT broker before.

So which one do you pick?

If you want the simplest possible setup and don't care about deep network diagnostics, ZHA is the easier starting point. If you've got a larger mesh, want to actually see what's happening between your coordinator and your devices, or you're chasing down flaky connections, Z2M's visibility is worth the extra setup step.

I run Z2M mainly because I lean on the network map constantly when troubleshooting range issues, but I know plenty of people happily running dozens of devices on ZHA without ever needing that level of detail. Neither one is "wrong," they're just optimized for different priorities.

Curious what others are running and why you landed where you did.

Sarah_D

Been meaning to write this up because I see the same question pop up every few weeks: "my Zigbee devices near the edge of the house keep going unresponsive, but everything close to the coordinator is fine."

I ran into this myself with a contact sensor on my back gate, about 40ft and two walls from the coordinator. It would work fine for a day or two, then just drop off and need re-pairing. Here's what I learned digging into it.

The mesh isn't as smart as people assume

Zigbee mesh networking sounds great on paper: routers repeat the signal, end devices hop through them to reach the coordinator. But it only works if you actually have routers in the right spots. A lot of people don't realize:

Battery-powered devices (sensors, most buttons) are almost always "end devices," not routers. They don't repeat signal for anyone else.
Only mains-powered devices (smart plugs, some bulbs, in-wall switches) act as routers.
If your edge-of-house devices are all battery sensors with no mains-powered Zigbee device nearby, there's nothing to relay them. They're relying on a direct, weak hop straight back to the coordinator.

What actually fixed it for me

I added a Zigbee smart plug about halfway between the coordinator and the back gate, specifically as a repeater. Within a day the contact sensor's LQI/RSSI reading jumped noticeably and it hasn't dropped since.

A few other things worth checking if you're in this situation:

Route table health: some coordinators/hubs let you see routing paths in their diagnostics. If a device is hopping through 3+ routers, that's a sign your mesh has gaps.
Channel interference: Zigbee channels 15, 20, 25 overlap with 2.4GHz Wi-Fi. If your router's on a busy channel, that can look like a range problem when it's actually noise.
Firmware: some manufacturers have quietly improved mesh healing behavior in updates.

The takeaway

Zigbee range problems are usually a topology problem, not a raw distance problem. A $15 to $20 mains-powered plug positioned as a repeater will usually do more for your edge devices than moving the coordinator around.

Curious if others have run into this. Did adding routers fix it for you, or was it something else (channel, firmware, specific brand)?

Smarthome Forum — Smart Home Community for Matter, Zigbee & HomeKit

Global Moderators

Posts

Member List