Hello, thank you for that well detailed video. I'd like to know if, with this method, it is possible to run ZHA and Z2M at the same time like it seems to be directly with dongle connection. I tried but i can't run both at the same time only one or the other, the multiprocol socket seems to accept only one connection at a time. Thanks in advance.
Did some extra research and it seems like even with direct dongle connection it's not possible to run Z2M and ZHA together. Only working with network coordinator. Otherwise need to have 2 physical coordinator, one for each integration.
Hi, sorry for the late response, there is something called Christmas happening ;). Yep, you found the correct answer, it is NOT possible to run ZHA and Z2MQTT on the same adaptor. Well not yet :)
@@ZamBloodyin general ZHA is for those wanting good native integration and ease of use. In general Z2MQTT provides more entities, and greater flexibility but at the expense of complexity.
Thank you very much for the detailed walk through. The Dongle failed to be defected on the firmware flash site when I use both Chrome and Edge. Then I tried to use Firefox with the WebSerial add in I am able to locate the Dongle and have the firmware updated.
To upgrade your Sonoff ZBDongle-E to support Thread when running Home Assistant in Docker, you'll need to take a slightly different approach since you don't have access to add-ons. Here's a step-by-step guide: 1 Flash the custom firmware: - Use the web flasher tool provided by darkxst to flash the custom RCP Multi- PAN firmware onto your Sonoff ZBDongle-E. - This firmware enables both Zigbee and Thread support on the dongle. 2 Set up the Silicon Labs Multiprotocol software: - Instead of using the add-on, you'll need to run the Silicon Labs Multiprotocol software as a separate Docker container. - Create a new Docker Compose file or add to your existing one: version: '3' services: silabs-multiprotocol: container_name: silabs-multiprotocol image: ghcr.io/home-assistant-libs/silicon-labs-multiprotocol:latest restart: unless-stopped privileged: true network_mode: host volumes: - /dev:/dev - /run/udev:/run/udev:ro 3 Update your Home Assistant Docker Compose file: - Modify your Home Assistant container configuration to use the Silicon Labs Multiprotocol container: services: homeassistant: # ... other configuration ... devices: - /dev/ttyACM0:/dev/ttyACM0 depends_on: - silabs-multiprotocol 4 Start the containers: - Run docker-compose up -d to start both the Silicon Labs Multiprotocol and Home Assistant containers. 5 Configure ZHA in Home Assistant: - Go to Settings > Devices & Services > Add Integration > Zigbee Home Automation. - Select "Enter Manually" for the serial port. - Enter socket://silabs-multiprotocol:9999 as the path. 6 Set up Thread and Matter: - Install the Thread integration in Home Assistant. - If you want to use Matter devices, install the Matter integration as well. Remember that Thread and Matter support in Home Assistant is still in development, so you may encounter some limitations or issues
I was about to follow your instructions but realised my USB stick is a Sonoff Zigbee Dongle-P. Are the instructions still applicable or only for the Sonoff Zigbee USB Dongle E?
Hmmm... OK afew things to check. - Make sure your Zigbee adapter's firmware is up-to-date and compatible with Zigbee2MQTT. - Double check your port, SETTINGS > SYSTEM > HARDWARE > ALL HARDWARE - Which to the relative USB address as oppsoed to the absolute - If using VM make sure the USB is getting passed through correctly - Try using a different USB port that's running USB 2.0 only If all that fails, then retry factory resetting the ZBDongle, upgrade to latest firmware and retry. Remember that Sonoff support is really good, so raise a ticket and see if they can also assist.
I was running this for years. Issue was that I started getting errors and everyone in the forums wouldn't help as they kept saying I was running an unsupported config. Ended up just flashing back to a ZigBee coordinator. I bought a second $15 dongle for Thread but haven't set it up. Any chance you can do a video on running these on separate dongles?
Thats the issue with running bleeding edge and topics where there is no community to collectively solve issues. Its one of the reasons I started this channel. Which Thread dongle did you buy? I'll see if I can get hold of one.
@@smart_home_australia I just bought another of the Sonoff ones. My WAF plummeted when I couldn't turn on or off the lights 😅 so I need a stable ZigBee coordinator but want to meas around with Thread too. I assume you could run two of the same dongles with different firmware on each?
OMG, WAF is the MOST important part of Smart Homes !! Get that fixed. ;) Yes you can run multiple Z2MQTT coordiantors (th-cam.com/video/ZBbl0I-Zpuk/w-d-xo.html) so you can setup a "primary" zigbee network and spin up a secondary for testing and YES they can be on different firmware with no issues. Good luck with the WAF :)
Yep, you can run a second ZBDongle just for thread if you want, just skip the section about setting up ZHA to access via the socket and leave your primary ZBDongle as ZHA. Let us know how that works out as I've never tried that.
Hmmm, it's looking much easier now. I had a crack at enabling this at the start of the year and gave up out of frustration. I couldn't for the life of me correctly configure the multiprotocol pass-through to Zigbee2MQTT, so I gave up on it all, reflashed the dongle back to Zigbee only and put ZHA back on. I even tried using the SkyConnect dongle I have as a spare, no joy there either. Right now I do have Thread on the network as well but it's currently using my Eero mesh APs as the border routers, and I really want to remove that hardware dependency. Might spin up a lab hassio on the weekend and have a tinker. Thanks for posting!
My advice, give it a go. :) Remember that you can have multiple Z2MQTT networks (check out that video th-cam.com/video/ZBbl0I-Zpuk/w-d-xo.html) so you don't even need a new HA instance to test it out.
I've installed the drivers but the dongle won't show up in the serial port thing in Chrome. It shows in device manager just fine, with COM25, but it has the name "Silicon Labs CP210x USB to UART Bridge" instead of "USB-Enhanced-Serial" as in the video. Could this be the problem? I installed the CP210x Universal Windows Driver from the website.
There are a few potential reasons why a ZBDongle-E might not show up in the web flasher upgrader even when the device driver is installed and it appears in Device Manager: 1) Incorrect or outdated driver: Make sure you have the correct and latest driver installed. For the ZBDongle-E, you typically need the CH340/CH341 driver. 2) USB port issues: Try connecting the dongle to a different USB port, preferably directly to the computer rather than through a hub. 3) Web browser permissions: Ensure your browser has the necessary permissions to access USB devices. You may need to grant access when prompted. 4) Firmware state: If the current firmware on the device is corrupted or in an unexpected state, it might not be recognized properly by the flasher. 5) Hardware flow control: Make sure hardware flow control is disabled in the device settings. 6) Interference: Using a USB extension cable can help reduce potential interference that might affect device recognition. 7) Windows updates: Ensure your Windows system is up-to-date, as this can sometimes affect driver functionality. 8) Reboot: Sometimes, a simple reboot of your computer after driver installation can resolve recognition issues. If you've checked these points and are still having issues, you might want to try manually flashing the firmware using a tool like Universal Silabs Flasher as an alternative to the web flasher
They no longer recommend this: Note! Beware that the RCP MultiPAN in multiprotocol mode is no longer recommended because running multi-protocol with multiple active networks on a single radio adapter has proven to not be stable when using Zigbee and Thread network protocols simultaneously on the same radio adapter, it also increases the complexity of software component dependencies needed, so if already using RCP Multi-PAN then it is highly recommended that you plan to migrate to separate dedicated radio adapters instead, (using Zigbee NCP and Thread RCP firmware respectively), even if using RCP MultiPAN on a single radio adapter dongle has been working fine for you so far.
Thanks Vulcan, I would agree with your statement. The video intends to show that it is possible and how to do it. But also teaches the community the instructions on how to flash or upgrade to a different version of the firmware. I run the latest supported version and only use my ZBDongle for Zigbee, as I need this network to rock solid and be available all the time. Any other protocols I use other adaptors for. Thanks for your comments, its appreciated.
When I try to connect, I get following failure message. What could be the reason for. Connection failed The running firmware could not be detected. Make sure the USB port works and if you are using a USB extension cable, make sure the cable can transfer data. Unplug the Sonoff ZBDongle-E and plug it back in to reset and try again.
I had same issue. On Opera it didn't work at all. Tried Edge, it worked first try but when I tried to upload custom firmware it failed at 0%. Then it no longer worked at Edge. Then tried again and again at opera/chrome/edge everywhere it worked 1/10 times and error at upload. Solution for me: 1. Try many times at different browsers, don't give up 2. When flash is successful firstly upgrade to 7.x.x.x! Don't try to change firmware! 3. After upgrade is successful it should work 10/10 at any browser 4. Change firmware
Who would have thought that Chromium based browsers were so temperamental. I thought that were supposed to be the most generic of all browsers. Thanks for your comments, its really appreciated.
You shouldn't need one as its created automatically. Check out the Thread integration page for more details (ref: www.home-assistant.io/integrations/thread/)
Great video as always.... thank you! I find these things so bloody frustrating - spent so much time mucking around with this thing and havent got much joy back in return... So in this weeks episode - a clean build of Win 11, plug the dongle in, load up the driver, connect via the web flasher - the running firmware could not be detected!!!!! URGH Not really sure how to tackle this new one if I'm honest... Rant over...
OK can I ask the obvious, sorry, are you using a chromium based browser? Can you see the device in device manager? and have you tried a different USB port.
@@smart_home_australia hi there, fair questions to be honest... Yes I had tried all of the above... Since my tantrum I've managed to flash it manually using Secure CRT and the latest firmware file. I think what is actually my greatest challenge here is getting the dongle to present to Home Assistant through my current crappy setup - virtualbox on win11. This seems to be the source of the bulk of my issues with the dongle. Cause I can't make the dongle appear in Settings/Hardware - I've presumed that the dongle is actually faulty and not an issue with my virtualbox setup. Thanks for taking the time to reply!!!
Wow its not supposed to be this hard.... very strange. I had some initial issues with making the dongle appear but that was in Edge (which is also a Chromium based browser and should work), but when I switched to Chrome it worked. Making the dongle appear inside of the VM should be super simple. 1) Launch VirtualBox on your system. 2) Click on the USB option present in the vertical menu. 3) Click on the USB 2.0 or USB 3.0 controller radio button. 4) Navigate to the USB device filters section and click on the add USB devices icon with a + sign on it. 5) You will see a list of the available devices. 6) Select the USB device you want to attach. 7) Click OK to save changes and exit. If this doesn't work then I think it might be a defective dongle, then i'd RMA the dongle.
Hello, thank you for that well detailed video.
I'd like to know if, with this method, it is possible to run ZHA and Z2M at the same time like it seems to be directly with dongle connection.
I tried but i can't run both at the same time only one or the other, the multiprocol socket seems to accept only one connection at a time.
Thanks in advance.
Did some extra research and it seems like even with direct dongle connection it's not possible to run Z2M and ZHA together. Only working with network coordinator. Otherwise need to have 2 physical coordinator, one for each integration.
Hi, sorry for the late response, there is something called Christmas happening ;).
Yep, you found the correct answer, it is NOT possible to run ZHA and Z2MQTT on the same adaptor. Well not yet :)
@@smart_home_australia All good. Thank you for your confirmation. I ended up with Z2M as it supports more devices
@@ZamBloodyin general ZHA is for those wanting good native integration and ease of use. In general Z2MQTT provides more entities, and greater flexibility but at the expense of complexity.
Thank you very much for the detailed walk through. The Dongle failed to be defected on the firmware flash site when I use both Chrome and Edge. Then I tried to use Firefox with the WebSerial add in I am able to locate the Dongle and have the firmware updated.
The joys of Chromium based browsers. Its unusual for Chrome itself not to work, but the point is that you got it working, thanks for lets us know.
USB-Flashing is also possible with Firefox if you add the "WebSerial for Firefox"-Addon to your Firefox-browser.
Thanks, I wasn't aware of that. I assumed as Firefox was not Chromium based it would not work, but am pleased it does as I've always liked Firefox.
Thank you for the advice. Only Firefox works for me ;)
What about if I'm running Home Assistant in docker (i.e. do not have access to add-ons)?
To upgrade your Sonoff ZBDongle-E to support Thread when running Home Assistant in Docker, you'll need to take a slightly different approach since you don't have access to add-ons. Here's a step-by-step guide:
1 Flash the custom firmware:
- Use the web flasher tool provided by
darkxst to flash the custom RCP Multi-
PAN firmware onto your Sonoff
ZBDongle-E.
- This firmware enables both Zigbee and
Thread support on the dongle.
2 Set up the Silicon Labs Multiprotocol
software:
- Instead of using the add-on, you'll need
to run the Silicon Labs Multiprotocol
software as a separate Docker container.
- Create a new Docker Compose file or
add to your existing one:
version: '3'
services:
silabs-multiprotocol:
container_name: silabs-multiprotocol
image: ghcr.io/home-assistant-libs/silicon-labs-multiprotocol:latest
restart: unless-stopped
privileged: true
network_mode: host
volumes:
- /dev:/dev
- /run/udev:/run/udev:ro
3 Update your Home Assistant Docker
Compose file:
- Modify your Home Assistant container
configuration to use the Silicon Labs
Multiprotocol container:
services:
homeassistant:
# ... other configuration ...
devices:
- /dev/ttyACM0:/dev/ttyACM0
depends_on:
- silabs-multiprotocol
4 Start the containers:
- Run docker-compose up -d to start both
the Silicon Labs Multiprotocol and Home
Assistant containers.
5 Configure ZHA in Home Assistant:
- Go to Settings > Devices & Services >
Add Integration > Zigbee Home
Automation.
- Select "Enter Manually" for the serial
port.
- Enter socket://silabs-multiprotocol:9999
as the path.
6 Set up Thread and Matter:
- Install the Thread integration in Home
Assistant.
- If you want to use Matter devices, install
the Matter integration as well.
Remember that Thread and Matter support in Home Assistant is still in development, so you may encounter some limitations or issues
I was about to follow your instructions but realised my USB stick is a Sonoff Zigbee Dongle-P. Are the instructions still applicable or only for the Sonoff Zigbee USB Dongle E?
Alas no, this video is for the E variant only, this is a hardware limitation so you won't find any similar videos for this variant. Sorry :(
Oh no i tried this and now nothing works anymore. There are errors in the log.
Can you tell me what's going wrong here?
Below the log and more below my config.
[16:09:25] INFO: Preparing to start...
[16:09:26] INFO: Socat not enabled
[16:09:26] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-09-24 16:09:28] info: z2m: Logging to console, file (filename: log.log)
[2024-09-24 16:09:28] info: z2m: Starting Zigbee2MQTT version 1.40.1 (commit #unknown)
[2024-09-24 16:09:28] info: z2m: Starting zigbee-herdsman (0.57.3)
[2024-09-24 16:09:28] info: zh:ember: Using default stack config.
[2024-09-24 16:09:28] info: zh:ember: ======== Ember Adapter Starting ========
[2024-09-24 16:09:28] info: zh:ember:ezsp: ======== EZSP starting ========
[2024-09-24 16:09:28] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2024-09-24 16:09:28] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2024-09-24 16:09:28] info: zh:ember:uart:ash: Serial port opened
[2024-09-24 16:09:28] info: zh:ember:uart:ash: ======== ASH starting ========
[2024-09-24 16:09:30] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2024-09-24 16:09:30] info: zh:ember:uart:ash: ======== ASH starting ========
[2024-09-24 16:09:33] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2024-09-24 16:09:33] info: zh:ember:uart:ash: ======== ASH starting ========
[2024-09-24 16:09:35] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2024-09-24 16:09:35] info: zh:ember:uart:ash: ======== ASH starting ========
[2024-09-24 16:09:38] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2024-09-24 16:09:38] info: zh:ember:uart:ash: ======== ASH starting ========
[2024-09-24 16:09:40] error: z2m: Error while starting zigbee-herdsman
[2024-09-24 16:09:40] error: z2m: Failed to start zigbee
[2024-09-24 16:09:40] error: z2m: Check www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-09-24 16:09:40] error: z2m: Exiting...
[2024-09-24 16:09:40] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
at EmberAdapter.initEzsp (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:701:19)
at EmberAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1708:24)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:138:29)
at Zigbee.start (/app/lib/zigbee.ts:64:27)
at Controller.start (/app/lib/controller.ts:140:27)
at start (/app/index.js:154:5)
Config:
data_path: /config/zigbee2mqtt
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: "-d -d"
log: false
mqtt:
server: mqtt://core-mosquitto:1883
user: mqtt
password: mqtt
serial:
port: >-
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220708150804-if00
adapter: ember
baudrate: 115200
Hmmm... OK afew things to check.
- Make sure your Zigbee adapter's firmware is up-to-date and compatible with Zigbee2MQTT.
- Double check your port, SETTINGS > SYSTEM > HARDWARE > ALL HARDWARE
- Which to the relative USB address as oppsoed to the absolute
- If using VM make sure the USB is getting passed through correctly
- Try using a different USB port that's running USB 2.0 only
If all that fails, then retry factory resetting the ZBDongle, upgrade to latest firmware and retry.
Remember that Sonoff support is really good, so raise a ticket and see if they can also assist.
I was running this for years. Issue was that I started getting errors and everyone in the forums wouldn't help as they kept saying I was running an unsupported config. Ended up just flashing back to a ZigBee coordinator. I bought a second $15 dongle for Thread but haven't set it up. Any chance you can do a video on running these on separate dongles?
Thats the issue with running bleeding edge and topics where there is no community to collectively solve issues. Its one of the reasons I started this channel.
Which Thread dongle did you buy? I'll see if I can get hold of one.
@@smart_home_australia I just bought another of the Sonoff ones. My WAF plummeted when I couldn't turn on or off the lights 😅 so I need a stable ZigBee coordinator but want to meas around with Thread too. I assume you could run two of the same dongles with different firmware on each?
OMG, WAF is the MOST important part of Smart Homes !! Get that fixed. ;)
Yes you can run multiple Z2MQTT coordiantors (th-cam.com/video/ZBbl0I-Zpuk/w-d-xo.html) so you can setup a "primary" zigbee network and spin up a secondary for testing and YES they can be on different firmware with no issues.
Good luck with the WAF :)
@@smart_home_australia I'm not using MQTT though. I want to just run ZHA on one and the thread stack on the other.
Yep, you can run a second ZBDongle just for thread if you want, just skip the section about setting up ZHA to access via the socket and leave your primary ZBDongle as ZHA. Let us know how that works out as I've never tried that.
Can I use ember and not EZ firmware on this?
Yep. Sure can.
Hmmm, it's looking much easier now. I had a crack at enabling this at the start of the year and gave up out of frustration. I couldn't for the life of me correctly configure the multiprotocol pass-through to Zigbee2MQTT, so I gave up on it all, reflashed the dongle back to Zigbee only and put ZHA back on. I even tried using the SkyConnect dongle I have as a spare, no joy there either. Right now I do have Thread on the network as well but it's currently using my Eero mesh APs as the border routers, and I really want to remove that hardware dependency.
Might spin up a lab hassio on the weekend and have a tinker. Thanks for posting!
My advice, give it a go. :)
Remember that you can have multiple Z2MQTT networks (check out that video th-cam.com/video/ZBbl0I-Zpuk/w-d-xo.html) so you don't even need a new HA instance to test it out.
I've installed the drivers but the dongle won't show up in the serial port thing in Chrome. It shows in device manager just fine, with COM25, but it has the name "Silicon Labs CP210x USB to UART Bridge" instead of "USB-Enhanced-Serial" as in the video. Could this be the problem? I installed the CP210x Universal Windows Driver from the website.
There are a few potential reasons why a ZBDongle-E might not show up in the web flasher upgrader even when the device driver is installed and it appears in Device Manager:
1) Incorrect or outdated driver: Make sure you have the correct and latest driver installed. For the ZBDongle-E, you typically need the CH340/CH341 driver.
2) USB port issues: Try connecting the dongle to a different USB port, preferably directly to the computer rather than through a hub.
3) Web browser permissions: Ensure your browser has the necessary permissions to access USB devices. You may need to grant access when prompted.
4) Firmware state: If the current firmware on the device is corrupted or in an unexpected state, it might not be recognized properly by the flasher.
5) Hardware flow control: Make sure hardware flow control is disabled in the device settings.
6) Interference: Using a USB extension cable can help reduce potential interference that might affect device recognition.
7) Windows updates: Ensure your Windows system is up-to-date, as this can sometimes affect driver functionality.
8) Reboot: Sometimes, a simple reboot of your computer after driver installation can resolve recognition issues.
If you've checked these points and are still having issues, you might want to try manually flashing the firmware using a tool like Universal Silabs Flasher as an alternative to the web flasher
They no longer recommend this:
Note! Beware that the RCP MultiPAN in multiprotocol mode is no longer recommended because running multi-protocol with multiple active networks on a single radio adapter has proven to not be stable when using Zigbee and Thread network protocols simultaneously on the same radio adapter, it also increases the complexity of software component dependencies needed, so if already using RCP Multi-PAN then it is highly recommended that you plan to migrate to separate dedicated radio adapters instead, (using Zigbee NCP and Thread RCP firmware respectively), even if using RCP MultiPAN on a single radio adapter dongle has been working fine for you so far.
Thanks Vulcan, I would agree with your statement. The video intends to show that it is possible and how to do it. But also teaches the community the instructions on how to flash or upgrade to a different version of the firmware.
I run the latest supported version and only use my ZBDongle for Zigbee, as I need this network to rock solid and be available all the time. Any other protocols I use other adaptors for.
Thanks for your comments, its appreciated.
When I try to connect, I get following failure message. What could be the reason for.
Connection failed
The running firmware could not be detected.
Make sure the USB port works and if you are using a USB extension cable, make sure the cable can transfer data. Unplug the Sonoff ZBDongle-E and plug it back in to reset and try again.
Are you trying from Chrome or a Chromium based browser?
@smart_home_australia I tried it with Edge and Chrome on two different computers.
I had same issue. On Opera it didn't work at all. Tried Edge, it worked first try but when I tried to upload custom firmware it failed at 0%. Then it no longer worked at Edge. Then tried again and again at opera/chrome/edge everywhere it worked 1/10 times and error at upload.
Solution for me:
1. Try many times at different browsers, don't give up
2. When flash is successful firstly upgrade to 7.x.x.x! Don't try to change firmware!
3. After upgrade is successful it should work 10/10 at any browser
4. Change firmware
Who would have thought that Chromium based browsers were so temperamental. I thought that were supposed to be the most generic of all browsers. Thanks for your comments, its really appreciated.
how do I get the Thread Network Key?
You shouldn't need one as its created automatically. Check out the Thread integration page for more details (ref: www.home-assistant.io/integrations/thread/)
Great video as always.... thank you!
I find these things so bloody frustrating - spent so much time mucking around with this thing and havent got much joy back in return...
So in this weeks episode - a clean build of Win 11, plug the dongle in, load up the driver, connect via the web flasher - the running firmware could not be detected!!!!! URGH
Not really sure how to tackle this new one if I'm honest...
Rant over...
OK can I ask the obvious, sorry, are you using a chromium based browser? Can you see the device in device manager? and have you tried a different USB port.
@@smart_home_australia hi there, fair questions to be honest... Yes I had tried all of the above...
Since my tantrum I've managed to flash it manually using Secure CRT and the latest firmware file.
I think what is actually my greatest challenge here is getting the dongle to present to Home Assistant through my current crappy setup - virtualbox on win11. This seems to be the source of the bulk of my issues with the dongle. Cause I can't make the dongle appear in Settings/Hardware - I've presumed that the dongle is actually faulty and not an issue with my virtualbox setup.
Thanks for taking the time to reply!!!
Wow its not supposed to be this hard.... very strange. I had some initial issues with making the dongle appear but that was in Edge (which is also a Chromium based browser and should work), but when I switched to Chrome it worked.
Making the dongle appear inside of the VM should be super simple.
1) Launch VirtualBox on your system.
2) Click on the USB option present in the vertical menu.
3) Click on the USB 2.0 or USB 3.0 controller radio button.
4) Navigate to the USB device filters section and click on the add USB devices icon with a + sign on it.
5) You will see a list of the available devices.
6) Select the USB device you want to attach.
7) Click OK to save changes and exit.
If this doesn't work then I think it might be a defective dongle, then i'd RMA the dongle.
@@smart_home_australia Thanj you again …. Might have a dongle then.
This has provided me though the impetus to get of Windows though.