Statusupdate: I have Bluetooth enabled on my three gateways, and on those two locations with Switchbot Bluetooth sensors, Home Assistant shows them under Settings - Bluetooth - Advertisements. Don't know if that data is actually used, because I have several Shellys active at the same time. But it looks OK.
Today I stumbled upon a Reddit post where someone built a stove monitor. Would it be possible to add a temperature sensor to that gateway as well? Does it have additional drivers for that kind of sensor compiled in, e.g. a MAX6675?
There is a MAX6675 driver present in OpenBeken, but not enabled.
Don't know if I2S works, but here you can find a firmware with "ENABLE_DRIVER_MAX6675" for RTL8720D and RTL8721DA:
What do you want temperature sensor for? If it's just for room temperature, AHT20 sensor would be a better choice (since it also measures humidity). Or a DS18B20.
Not many things are supported by bluetooth without connections. Majority of them are sensors, anything that can be controlled is a no-go.
I use it with a very cheap Tuya sensors based on PHY6222 chip (THB2/BTH01/TH05 etc) or TLSR825x (zigbee originally) flashed with BTHome firmware.
If I got it right it was about stove temperature. And you'll need something more heat resistant in that case...
insmod wrote:
What do you want temperature sensor for?
Exactly, I want to monitor the exhaust temperature of our wood stove. And that can get quite hot, but I don't know how hot exactly. But it should be at least above 120 °C going into the chimney. And that's our problem, I think we don't reach that temperature when keeping the fire low (bad for the chimney and for efficiency as well, probably). So I want to send a notification if that temperature is too low, or too high. Since the sensor is directly exposed to smoke (and maybe flames as well, in the worst case?), it should be built for that.
I found this on Amazon, and since that chip is supported, I would try it. But it could be any other supported model as well.
https://www.amazon.de/dp/B0DRFQ59VT
Our wood stove even has a built-in temperature sensor with a motor-controlled air inlet, but I would not try to mess around with this, replacement parts for it are really expensive.
If I can't get this to work with this gateway, I would try with a Raspberry Pi or some ESP board. But since the gateway is there, it should be used for something practical.
Added after 22 [minutes]:
insmod wrote:
Not many things are supported by Bluetooth without connections. Majority of them are sensors, anything that can be controlled is a no-go.
I use it with very cheap Tuya sensors based on PHY6222 chip (THB2/BTH01/TH05 etc.) or TLSR825x (Zigbee originally) flashed with BTHome firmware.
Yes, I know. It's probably the same level as Shelly supports? I only use it for my SwitchBot outdoor temp/humidity sensors, which I chose, because they are for outdoor usage and run on AAA batteries. Initially, I searched for Zigbee sensors, but could not find anything appropriate. In the beginning, I got a Shelly Plug S Gen 2 especially for that, but in the meantime I have other Shellys as well, e.g. for the central gas heater, in addition to the regular wall thermostat. So more than enough Bluetooth proxies around the house.
almost a year later, I'm starting to get excited about this device. I'm just looking into the Zigbee IKEA Tradfri bulb and wondering what I have to make use of Zigbee
✨ The discussion focuses on converting the Smart Gateway model RSH-GW006 to run OpenBeken (OBK) firmware, aiming to centralize tools, files, setup instructions, and integration guidance. The device teardown reveals four hidden screws and detailed board pinouts and schematics. Firmware for the WBRG1 module is based on OpenRTL8720D, with stable operation reported. The ZS3L module firmware is built with hardware flow offload and can be updated via TCP, though flashing can be sporadic and sometimes requires bootloader mode activation by pulling specific pins high. Universal-silabs-flasher is the primary tool used for flashing ZS3L firmware, supporting both UART and socket connections. Various firmware versions (8.0.2.0, 8.1.1.0, 8.2.0.0, and stock Tuya 6.5.5.0) were tested, with 8.2.0.0 and a specific build for MGM210L022JNF silicon identified as stable and fully functional for the ZS3L on the Tuya MOES NH-THP01-ZB gateway. Challenges include bootloader detection issues, secure boot possibly blocking custom firmware, and hardware differences in ZS3L variants. J-Link and ST-LINK V2 probes with custom OpenOCD were used for chip unlocking, backup, and flashing, as standard Segger tools are limited to STM32 devices. ESP32-S3 and C3 modules were tested for Bluetooth proxy functionality, with temperature and frequency tuning discussed. Bluetooth support in OBK is limited, with ongoing efforts to add BTHome support. The thread includes detailed logs, flashing commands, and troubleshooting steps to aid in successful firmware conversion and integration with Zigbee2MQTT (Z2M) and Home Assistant (HA). Generated by the language model.
TL;DR: Convert the Smart Gateway RSH-GW006 to OBK on the WBRG1 and bridge its ZS3L Zigbee over TCP. 1 month uptime reported; "Stable, I've got a month uptime." Flash with Ameba Image Tool, integrate ZHA at tcp://:8888, and update ZS3L via universal‑silabs‑flasher. [Elektroda, insmod, post #21588192]
Why it matters: You reclaim a Tuya gateway for local control with Home Assistant or Zigbee2MQTT, no cloud required.
Zigbee2MQTT: ZS3L 8.2.0.0 needs latest-dev (EZSP v17); 8.1.1.0 works on stable. [Elektroda, insmod, #21589890
What hardware is inside the RSH-GW006, and where does OBK run?
The gateway houses a WBRG1 (Realtek RTL8720D/AmebaD) Wi‑Fi SoC and a Silicon Labs ZS3L Zigbee NCP. OBK (OpenRTL8720D) runs on the WBRG1, while the ZS3L stays as the Zigbee radio exposed over a TCP‑to‑UART bridge. [Elektroda, DeDaMrAz, post #21588187]
How do I open the RSH-GW006 case without damage?
Flip the unit and peel the four rubber feet. Remove the four small screws hidden beneath them. Lift the lid carefully to avoid stressing internal cables. This exposes the WBRG1 and ZS3L modules for UART and J‑Link access. [Elektroda, DeDaMrAz, post #21588187]
How do I put the WBRG1 into bootloader (download) mode?
Follow this 3‑step sequence:
Connect UART (GND, 3V3, RX, TX) to P1 and pull ENABLE to GND.
How can I back up the original WBRG1 firmware safely?
Enter download mode, then run rtltool.py to read full flash, e.g., py -3.12 rtltool.py -p COMx -b1000000 rf 0 0x8000000 ff.bin. Adjust Python version with python -V and tweak baud (up to 1,500,000). Expect ff.bin ≈ 8Mb. Use COMx on Windows or /dev/tty* on Linux. [Elektroda, DeDaMrAz, post #21588187]
How do I flash OBK onto the WBRG1 with Ameba Image Tool?
Open Ameba-ImageTool v2.3.2, load the latest RTL8720D UART build into the first field, and do not change other options. Put WBRG1 into bootloader, click Download, then reboot. The device should broadcast an OBK AP; connect and configure at 192.168.4.1. [Elektroda, DeDaMrAz, post #21588187]
What OBK pin roles should I set for LEDs and the button?
Use these roles: pin 25 = LED;1, pin 54 = WifiLED;0, pin 55 = Btn_n;0. Apply via OBK’s pin configuration. This maps the status LED, Wi‑Fi LED, and the front button to expected behaviors. [Elektroda, DeDaMrAz, post #21588187]
How do I expose Zigbee over TCP and add it in Home Assistant (ZHA)?
In OBK autoexec.bat, start the TCP‑UART bridge: startdriver uarttcp 115200 512 1 1, label the channel, hide it, and set type OpenClosed_Inv. In Home Assistant, add ZHA and select tcp://:8888 as the port. Enable Hardware flow control only if you flashed the latest ZS3L FW. [Elektroda, DeDaMrAz, post #21588187]
How do I flash or update the ZS3L Zigbee firmware over TCP?
Use universal‑silabs‑flasher from your PC: universal-silabs-flasher --device socket://:8888 flash --firmware zs3l_zigbeencp_115200.gbl. It detects EZSP and Gecko bootloader, then writes the GBL image. You can downgrade with --allow-downgrades. Example upgrades to 8.2.0.0 and downgrades to 8.1.1.0 were successful. [Elektroda, insmod, post #21589890]
Which ZS3L firmware version should I use with Zigbee2MQTT today?
Use 8.1.1.0 with stable Zigbee2MQTT. Version 8.2.0.0 requires the latest‑dev container because it uses EZSP protocol v17. As one tester noted, “8.1.1.0 works.” You can switch with universal‑silabs‑flasher as needed. [Elektroda, insmod, post #21589890]
Zigbee2MQTT fails after upgrading to ZS3L 8.2.0.0—what’s the fix?
You may see: “Adapter EZSP protocol version (17) is not supported by Host [13‑16].” Run the latest‑dev Zigbee2MQTT (dev branch supports EZSP v17), or downgrade the NCP to 8.1.1.0 using universal‑silabs‑flasher with --allow-downgrades. This restores stable connectivity. [Elektroda, insmod, post #21589890]
Can I flash the ZS3L over UART directly?
Direct UART flashing proved unreliable here. The author tried multiple tool combinations without success. Recommended methods are J‑Link with Simplicity Commander or universal‑silabs‑flasher over the OBK TCP bridge on port 8888. [Elektroda, DeDaMrAz, post #21588187]
My USB‑UART struggles at 1,500,000 bps. What should I do?
Lower the baud rate and retry. Edit the script’s -b value and test alternatives like 921600 or 1000000. Confirm your Python version (python -V) and call the correct interpreter (e.g., py -3.12). Use quality cables and a reliable adapter. [Elektroda, DeDaMrAz, post #21588187]
Does Bluetooth work on this gateway under OBK?
Not currently. A UART‑to‑Linux BT attempt required kernel patches and still failed to function; bluetoothctl saw nothing. The developer mentioned exploring BTHome support in OBK later. “It didn’t work” summarizes current status. [Elektroda, insmod, post #21588894]
Can I update the ZS3L while the gateway still runs stock Tuya firmware?
Yes. universal‑silabs‑flasher can talk to the stock NCP. However, very old stock may not work with the ember driver in Zigbee2MQTT. Plan to update NCP firmware after migrating WBRG1 to OBK for best compatibility. [Elektroda, insmod, post #21588402]
What extra universal‑silabs‑flasher flags are useful but hidden from --help?
Useful flags include --allow-cross-flashing, --allow-downgrades, --ensure-exact-version, and --force. These control cross‑flashes, downgrades, strict versioning, or skipping safeguards. They are handy when aligning NCP firmware with your Zigbee stack or rolling back from an incompatible build. [Elektroda, DeDaMrAz, post #21590140]
Should I always flash the newest ZS3L firmware?
No. Match firmware to your Zigbee stack support level. As the maintainer noted, “Newer does not mean better.” Prefer 8.1.1.0 for broad compatibility now, or move to 8.2.0.0 if your Zigbee2MQTT build supports EZSP v17. [Elektroda, insmod, post #21588567]
