Skip to content

Show and Tell

24 Topics 24 Posts
Share your smart home setup, automations, and DIY builds.

This category can be followed from the open social web via the handle show-and-tell@smarthome.forum

  • Moving Sengled Zigbee bulbs off the Sengled hub: what I learned

    1
    0 Votes
    1 Posts
    113 Views
    S
    I had Sengled bulbs on the Sengled hub and wanted them in Home Assistant. Here's how it went. Getting them off the old hub • Factory-reset each bulb with the power-cycle method in Sengled's instructions. • Pair it to the new coordinator straight away, with the bulb close to it. Where they work well • Home Assistant with a ZBDongle-P. • Hubitat, Homey Pro and the Aqara M3 also support them. • Hue bridges can work too, though support varies. The big gotcha Sengled Zigbee bulbs don't act as routers. If you were relying on them to extend the mesh, add a smart plug or switch that does route. After a power outage, they default back to on. That's worth knowing if they're in a bedroom. Full Sengled ecosystem guide: https://zigbeehubs.com/blog/sengled-zigbee/
  • 0 Votes
    1 Posts
    56 Views
    S
    I moved Zigbee2MQTT from a Home Assistant add-on to plain Docker. Here's what the install looked like. What you need • Docker and Docker Compose. • An MQTT broker. I run Mosquitto in its own container. • A coordinator like a ZBDongle-P or ZBDongle-E. Key steps Pass the dongle into the container using its /dev/serial/by-id/... path. Mount a data folder so your config and network survive container updates. Set the adapter in the config: zstack for the P, ember for the E. Point Z2M at your MQTT broker. The fix that took me longest: permissions on the USB device. If Z2M can't open the port, check the device permissions and group. Do you need Home Assistant? No. Z2M in Docker works with anything that speaks MQTT. Updating is just pull and restart, but back up your data folder first. Full Docker setup guide: https://zigbeehubs.com/blog/zigbee2mqtt-docker/
  • Adding Zigbee devices to Alexa: Echo hub or a separate hub?

    1
    0 Votes
    1 Posts
    65 Views
    S
    Some Echo devices have a Zigbee hub built in, which confuses a lot of people. Here's how I'd decide. Using the Echo's built-in Zigbee • Works for simple devices like bulbs, plugs and basic sensors. • Pair from the Alexa app with "Discover devices". • Limited support for advanced features, and you're tied to Alexa. Using a separate hub • Hubitat, Homey Pro, the Aqara M3, or a ZBDongle-P with Home Assistant. • Pair everything there, then link the hub to Alexa for voice control. • Much better device support and local automations. What I do: devices pair to Home Assistant, and Alexa is only for voice. Voice control still needs the internet, but the automations don't. Full guide to adding any Zigbee device to Alexa: https://zigbeehubs.com/blog/zigbee-alexa/
  • 0 Votes
    1 Posts
    64 Views
    S
    I've helped a few friends set up ZHA lately, and they all got stuck in the same places. Here's the short version. Plug in the coordinator with a USB extension cable. Do it before you start. It saves debugging later. Go to Settings > Devices & Services. ZHA often discovers the stick automatically. If not, add the ZHA integration manually. Pick the serial port carefully. Choose the /dev/serial/by-id/... path, not /dev/ttyUSB0. The by-id path survives reboots and adding other USB devices. Let it create the network. The defaults are fine for most people. Pair mains devices first, then battery sensors. ZHA or Zigbee2MQTT? ZHA is the easiest start. Z2M gives more control. I covered the differences in another thread. Full step-by-step guide: https://zigbeehubs.com/blog/zigbee-home-assistant/
  • Getting Arduino talking Zigbee: PAN IDs, modules and the mistakes I made

    1
    0 Votes
    1 Posts
    63 Views
    S
    I spent a weekend getting an Arduino to send sensor data over Zigbee. Here's what I'd tell myself at the start. Setup • Arduino plus an XBee or similar Zigbee module over serial. • A second module or a USB coordinator on the receiving end. Mistakes I made • Mismatched PAN ID: the modules must share the same PAN ID or they'll never see each other. This took me an embarrassingly long time to spot. • Wrong roles: one device has to be the coordinator. Two routers won't form a network. • Baud rate mismatch between the Arduino and the module. Can Arduino be a Zigbee gateway? With the right module, yes. For a smart home gateway, though, a ready-made coordinator or an ESP32-C6 is far easier. Range depends on the module and antenna, so test it at the distance you actually need. Full Arduino Zigbee setup guide: https://zigbeehubs.com/blog/arduino-zigbee/
  • 0 Votes
    1 Posts
    59 Views
    S
    I've written plenty here about keeping a Zigbee network stable. This one is about what all that stability is for. Night path lighting: motion sensors turn on hallway lights at 10% after 11pm. No more stubbed toes. Leak alert: a sensor under the washing machine flashes every light and sends a notification. Window open, heating off: contact sensors pause the heating when a window has been open for five minutes. Goodnight button: one Zigbee button turns everything off and checks every door is shut. Bathroom humidity fan: the extractor fan turns on when humidity spikes and off when it settles. None of these need the cloud, and that's the point of Zigbee for me. What's your favourite automation? Full Zigbee home automation guide: https://zigbeehubs.com/blog/zigbee-home-automation/
  • CC2531 on a Pi 4 with Zigbee2MQTT: it works, but here's why I moved on

    1
    0 Votes
    1 Posts
    42 Views
    S
    My first Zigbee2MQTT setup was a CC2531 stick on a Raspberry Pi 4. Here's an honest look back for anyone tempted by one. Getting it running • Flash the right coordinator firmware first. • Install Mosquitto and Z2M, then set the serial port in Z2M's config. • Pair devices one at a time, close to the stick. Why it got unstable • Limited capacity: once I passed a modest number of devices, things started dropping. • Weak radio: no external antenna and easily affected by the Pi's USB 3.0 ports. • Older Zigbee stack: some newer 3.0 devices weren't happy. What I'd do instead Buy a ZBDongle-P or ZBDongle-E for not much more money. Use the CC2531 as a cheap router or for experiments. Full install guide, if you still want to try it: https://zigbeehubs.com/blog/cc2531/
  • ESP32-C6 vs ESP32-H2 for Zigbee projects: which board for which job

    1
    0 Votes
    1 Posts
    36 Views
    S
    After my ESP32-C6 coordinator experiments, I tried building actual Zigbee devices. Here's how I'd choose a board. • Classic ESP32 or ESP32-S3: no 802.15.4 radio, so no native Zigbee. You'd need an external radio. • ESP32-C6: Wi-Fi, BLE and 802.15.4. Best when your device also needs Wi-Fi, like a Zigbee-to-Wi-Fi gateway. • ESP32-H2: 802.15.4 and BLE, but no Wi-Fi. It uses less power, so it's great for battery Zigbee end devices. What I've built • A mains-powered Zigbee router on a C6 to patch a weak spot. • A battery temperature sensor on an H2 as an end device. Both pair with ZHA and Z2M, but custom devices sometimes need extra converter work in Z2M. Full ESP32 Zigbee setup guide: https://zigbeehubs.com/blog/esp32-zigbee/
  • 0 Votes
    1 Posts
    37 Views
    S
    If you've just bought an EFR32MG21-based dongle (ZBDongle-E, ZB-GW04 or SLZB-06M) and it's misbehaving in Zigbee2MQTT, check this first. The setting In Z2M, use the ember adapter for EFR32 sticks. The older ezsp driver is deprecated, and switching to ember fixed a lot of instability for me. Other things that helped • Update the firmware to a recent EmberZNet release that matches what Z2M expects. • USB extension cable: yes, again. • Don't mix up E and P. EFR32 sticks use ember. TI CC2652 sticks use zstack. Pick the wrong one and Z2M won't start. Which one? • ZBDongle-E: a good all-rounder. • ZB-GW04: a cheap, decent alternative. • SLZB-06M: if you want Ethernet or PoE. Full EFR32MG21 dongle comparison: https://zigbeehubs.com/blog/efr32mg21/
  • 0 Votes
    1 Posts
    37 Views
    S
    The Lidl Silvercrest gateway is cheap and pops up often, so I looked into using it with Home Assistant. The catch Out of the box it's tied to the Tuya cloud. To use it with ZHA or Zigbee2MQTT, you have to modify it so its Zigbee radio is exposed over the network. That means opening it up and working over a serial connection. Is it worth it? • If you enjoy tinkering: yes. It's a fun project and ends up as a cheap network coordinator. • If you just want it to work: no. A ZBDongle-P costs about the same and works straight away. Tips if you do it • Keep a backup of the original firmware. • Use a stable network connection. Network coordinators don't like dropouts. • Expect to tweak settings in ZHA or Z2M. Full Silvercrest setup guide: https://zigbeehubs.com/blog/silvercrest-gateway/
  • 0 Votes
    1 Posts
    35 Views
    S
    If you've paired Tuya Zigbee devices in Zigbee2MQTT, you've probably seen the same model name on completely different devices: TS0601. What's going on TS0601 is a generic model ID Tuya uses for devices with their own microcontroller. The real identity is in the manufacturer name, something like _TZE200_xxxxxxxx. Z2M uses that to work out what the device actually is. What helped me • Check the manufacturer name, not the model, when searching Z2M's supported devices list. • Same product, different internals: the same listing can ship with different manufacturer names over time. Two "identical" sensors can behave differently. • Unsupported device? Z2M external converters can add support. Check the Z2M GitHub issues first. • No Tuya hub needed. They pair directly with Z2M or ZHA and run fully local. Full TS0601 guide for Z2M and Home Assistant: https://zigbeehubs.com/blog/tuya-ts0601/
  • 0 Votes
    1 Posts
    29 Views
    S
    I swapped the antenna on my coordinator to see if it would fix some weak spots. The results weren't what I expected. What I found • Higher dBi isn't automatically better. A high-gain antenna focuses the signal in a flatter pattern. That can help on one floor but make things worse upstairs or downstairs. • The USB extension cable did more than the antenna. Moving the dongle away from the PC improved LQI more than the antenna swap did. • Orientation matters. Vertical worked best for my single-storey layout. • Check before and after. I compared LQI in Zigbee2MQTT before and after each change instead of guessing. An antenna upgrade is worth trying on a ZBDongle-E, ZBDongle-P or SLZB-06. It still won't replace a few well-placed routers. Full antenna guide, including when it actually helps: https://zigbeehubs.com/blog/zigbee-antennas/
  • Getting Zigbee to reach the garden, shed and gate: what worked outdoors

    1
    0 Votes
    1 Posts
    36 Views
    S
    Indoor Zigbee is one thing. Getting a reliable signal to a shed or garden sensor is another. What helped outdoors • Put a router near a window or outside wall facing the garden. A smart plug on a windowsill made the biggest difference for me. • Weatherproof routers outside: an outdoor-rated plug or relay in a covered spot extends the mesh further. • Watch for Wi-Fi overlap: Zigbee and Wi-Fi share 2.4 GHz. Choosing a Zigbee channel away from your Wi-Fi channel helps at the edge of range. • Coordinator placement: central and high, away from metal. A network coordinator like the SLZB-06 lets you move it closer to the outdoor side of the house. Outdoor range numbers on product pages are line-of-sight best cases. Walls, glass coatings and foliage cut them a lot. Indoor vs outdoor radio comparison: https://zigbeehubs.com/blog/zigbee-radio/
  • Aqara devices in Home Assistant: Aqara hub or straight to Zigbee2MQTT?

    1
    0 Votes
    1 Posts
    35 Views
    S
    I've run Aqara sensors both through an Aqara hub and paired directly to Home Assistant. Here's how they compare. Through an Aqara hub (M2, M3 or E1) • Easiest setup, and you keep the Aqara app. • Works well with HomeKit. • You're limited to what the hub exposes. Directly with ZHA or Zigbee2MQTT • Everything is local, and you get every attribute the device reports. • Watch your routers. Older Aqara end devices can be picky about which routers they stay connected to. This was my biggest source of dropouts. My favourite Aqara devices • T1 temperature and humidity sensor: accurate enough for heating automations. • T1 door and window sensor: tiny and reliable. • P1 motion sensor: adjustable timeout and long battery life. • FP2 presence sensor: for rooms where motion sensors miss people sitting still. Note this one is Wi-Fi. Full Aqara device guide and integration steps: https://zigbeehubs.com/blog/aqara-zigbee/
  • Building a Zigbee gateway on a Raspberry Pi: my setup notes

    1
    0 Votes
    1 Posts
    53 Views
    S
    A Raspberry Pi with a USB coordinator is still one of the cheapest ways to run a fully local Zigbee network. Here's what worked for me. Hardware • Raspberry Pi 4 (a Pi 5 is fine too) with a decent power supply. • A Zigbee 3.0 USB coordinator such as the SONOFF ZBDongle-P. • A USB extension cable. This is not optional. The Pi's USB 3.0 ports and Wi-Fi sit right next to the dongle and cause interference. • An SSD instead of an SD card if it's going to run 24/7. Software I run Home Assistant OS with ZHA. Zigbee2MQTT is a good alternative if you want more control. Tips • "Permit join" only needs to be on while you're pairing. Turn it off afterwards. • Pair mains-powered devices first so the mesh has routers before you add battery sensors. • Everything keeps working when the internet goes down, which was the main reason I went this route. Step-by-step guide here: https://zigbeehubs.com/blog/raspberry-pi-zigbee/
  • Using Zigbee soil moisture sensors to stop killing my houseplants

    1
    0 Votes
    1 Posts
    54 Views
    S
    I have a terrible record with houseplants, so I tried Zigbee soil moisture sensors with a simple Home Assistant alert. My setup • A soil sensor in each problem pot, reporting moisture and temperature. • An automation that pings my phone when moisture drops below a threshold I tuned per plant. • For the balcony, a Zigbee smart plug on a small pump. It's not fancy, but it works. What I learned • Calibrate per plant: "dry" for a succulent and "dry" for a fern are very different numbers. • Outdoor use: check the sensor's water resistance rating before leaving it out all year. • Range: pots on a balcony are often at the edge of the mesh. A smart plug acting as a router nearby made a big difference. The THIRDREALITY Gen2, Tuya GXM-01, MOES and Candeo sensors all came up when I was researching. This comparison covers battery life and outdoor suitability: https://zigbeehubs.com/blog/zigbee-soil-moisture-sensor/
  • I turned an ESP32-C6 into a Zigbee coordinator. Here's what tripped me up

    1
    0 Votes
    1 Posts
    49 Views
    S
    I've been curious whether a cheap ESP32-C6 board could run a Zigbee network on its own, since it has an 802.15.4 radio built in. Short answer: it can, but there are a few gotchas. What caught me out • Zigbee Mode setting: in Arduino IDE you have to set Tools > Zigbee Mode to ZCZR (coordinator/router). If you leave it on End Device, the coordinator sketch won't compile. • Partition scheme: it needs the matching Zigbee ZCZR partition for your board's flash size. Copying a setting from a tutorial for a different board caused me problems. • Charge-only USB cable: the board powered on but never showed up as a port. Swapping the cable fixed it. • Joining vs binding: my test bulb joined fine but didn't respond. The endpoint and binding setup was the real issue, not pairing. Would I run my house on it? No. It's a great learning tool and a solid base for a custom gateway. For a permanent Home Assistant network with dozens of devices, I'd still use a dedicated coordinator like a ZBDongle-P or an SLZB-06. Full walkthrough with the coordinator sketch and a troubleshooting checklist: https://zigbeehubs.com/blog/esp32c6/
  • Picking a Zigbee Thermostat: What I Wish I’d Checked First

    1
    0 Votes
    1 Posts
    169 Views
    S
    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.
  • 0 Votes
    1 Posts
    322 Views
    Amanda JonesA
    I kept searching “does Ring work with HomeKit” because I wanted to use my Ring doorbell with Apple Home. I couldn’t find a native HomeKit option for my Ring setup, so I started looking at other ways to connect it. Here are a few methods I tried. Homebridge Homebridge was the first option I tried. I already had a Raspberry Pi, so it was a good place to start. I installed the Ring plugin and connected it to Apple Home. The setup took a little time, but once everything was connected, I could see my Ring device in the Home app. The main downside for me was not having HomeKit Secure Video. Home Assistant I also tried Home Assistant because I was already using it for other smart home devices. I connected Ring to Home Assistant and then used HomeKit Bridge to bring it into Apple Home. It worked for basic use, but the Ring integration still relies on Ring’s cloud connection. HomeKit Secure Video isn’t supported through the Home Assistant HomeKit Bridge either. Scrypted Then I looked at Scrypted. It supports HomeKit Secure Video, which made it an interesting option for using cameras with Apple Home. The setup was a little more involved than the other options, but it’s worth looking at if HomeKit Secure Video is important to you. For me, there still isn’t one simple solution that does everything. These workarounds gave me a few different ways to bring Ring and Apple Home together. Has anyone here found another good way to use Ring with Apple Home? I’d like to know what worked for you.
  • 0 Votes
    1 Posts
    188 Views
    S
    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.