Hi,
My local cube is using SONOFF ZBDongle-LMG21 via USB (screenshot below).
How do I know which Zigbee channel the dongle is using?
How to set different Zigbee channel in the Cube?
Thank you.
Typically, after you plug in the dongle, you can click on the pop-up here to enable automatic configuration. However, you need to ensure that your dongle’s Zigbee version is below 7.4.5. If the version is greater than that, you will need to manually configure it and select the Ember driver.
Nice tutorial, but in my opinion there are no examples of setting up ZBDongle-MAX.
Interesting. Seems like the next step is starting all over again. X)
Also, as far as I am now: I do not know my dongle version and I do not know about Ember driver.
Let my try it during this long lebaran holiday.
Thank you.
Is it possible to add Sonoff RF devices to CUBE?
I have some RF buttons in my iHost, which runs CUBE. You just sign into your eWeLink account and they get Incorporated. I may have one device type but can’t see why other device types wouldn’t. My RF bridge is a V2. Maybe the V1 doesn’t have local mode or something…
1 Like
That’s good to know. So you can still use an RF device through the Cube without internet?
Because that’s my point… Hosting the Cube independently for full offline autonomy. 
The only problem is that I have a rather mixed RF, Wi-Fi, and ZigBee environment…
The compatibility of RF devices may vary depending on the specific model. Could you please let me know the exact model of the Sonoff RF device you are trying to add? I can help you further confirm its compatibility. Looking forward to your reply!
Hi,
I’m not adding any devices at the moment. I’m just figuring things out…
I’m interested in how the RF-based ecosystem works in the Cube.
Currently, the RF devices are paired with my first-generation Sonoff RF Bridge (RFBridge433) FW 3.6.2, the black one. This hub is used by several different devices, such as the DW2 and several different buttons.
I’m wondering if it’s possible to pair the hub with the Cube via LAN. I don’t want the Cube to communicate with the cloud, which the RF hub will also communicate with, but rather completely offline, something like LAN mode.
But is it feasible? With ZigBee, I need a suitable radio in the server for the Cube, which I don’t like with RF. Can RFBridge433 keep its functionality and devices and only work with Cube without internet?
We regret to inform you that it is currently not possible to add the RFBridge433 directly to the eWeLink CUBE OS via LAN.
However, we do have a viable alternative solution: You can install the eWeLink Smart Home add-on via the Docker feature in CUBE OS. By adding the RFBridge433 and its sub-devices to the eWeLink App first, you can then indirectly integrate them into CUBE OS through this add-on, enabling local control and automation.
If you need any assistance during the setup process or have further questions about this alternative, please feel free to contact us anytime. Thank you again for your understanding and support!
Is this V1 and v2 of the RF bridge?
If I understand correctly, assuming this applies to V2, the iHost communicates with the cloud and the cloud then communicates with the V2 even if you have enabled local mode?
I think I would just tasmotise my RF bridge and then communicate locally with them using Node Red MQTT in/out and and use the eWeLink palette to create a virtual device locally. Seems easier than installing the docker image and then talking over matter between the docker and the iHost.
I have RF bridge version 2 to iHost, I added it via ewelink addon, but the ewelink application itself shows me local control. I haven’t researched what it is, really. In older posts I wrote about it, all the gateways could communicate via mgtt with each other.
As far as I know from my tests and use here, both V1 and V2 with Local Control enabled work locally! In fact, these hubs are on a VLAN that doesn’t have internet access precisely to test this!
1 Like
I was thinking of creating a separate VLAN that can’t get to WAN in addition to my standard IoT VLAN. I currently block my TV from getting to WAN individually with its own PBR but now Belkin Wemo have dropped their cloud I have loads of devices and I don’t know which is them. So it might be sensible to just create a separate local only VLAN. How have you blocked this VLAN from getting to the WAN? I am torn between blocking it with PBR or the Firewall. What have you gone for?
I have a Mikrotik and I set a rule for a range of addresses that do not have access to the WAN. If you have a Mikrotik, I can help.
I use TP-LINK equipment because it’s easy to separate VLANs and define who has internet access and who doesn’t!
After using the ewelink add-on to bring the RF devices into iHost, then using Node-red with the ewelink Cube node, the control is LAN and eWelink can be uninstalled.