Congratulations for such useful video, very insightful. One idea is using that seed tiny board, make it a thread node reading a button and/or sensor showing that handshake.... Regards. I also noticed your videos are mainly on Nordic, you should try esp32 ic that also has the thread radio...
👋Thanks for making all these tutorials. These are very helpful. I am recently struggling with multi-protocol Thread network using nRF microcontrollers. Would it be possible for you to record a tutorial on how to have multi-protocol Thread network with BLE?
Thank you for the wonderful video! I want to communicate the signal from each sensor in the way shown in this video using a raspberry pi. For example, if I want to send the value of the heart rate sensor to the raspberry pi combined with the nRF52840 dongle(BorderRouter), should the heart rate sensor be connected to the combination of Arduino and nRF52840DK board? Or do I have to connect it to the new Raspberry Pi and nRF52840 dongle combination?
Hi! Thank you for the tutorial. I am working on some projects with matter. Is it possible to make an esp32 S2 as a client device instead of nRF52840-dk?
Good video! Thank you for sharing! I was wondering two things … 1) If the Rpi was also configured with eg Homebridge & added to an existing Apple HomeKit could the Rpi gpio use the thread wireless route (via border router) as opposed to wifi ie to make communications more robust… 2) Also Could a second nrf52840 usb dongle be programmed to be an end device on the Apple HomeKit network to eg indicate both Digital & analogue inputs (switch operation or battery voltage)
Thx for the feedback. To 1: I can't really answer that. Homekit and Thread both use IPv6, so at least routing should theoretically be possible with Homebridge installed. However, I have not worked with Homekit or Homebridge so far, so I cannot make any reliable statements on this. To 2: Actually the same. I'm not familiar with Homekit. Theoretically, a nrf52840 dongle can be programmed to a thread device and send desired data to any thread device, including the home kit. However, I don't know what data the Homekit expect to process it.
Hello! I have been following your videos to setup a border router, but when i reach around 21:28 im getting an invalidcommand error when i use the br nat64prefix command. Also, i cant seem to get the ping command to work. What do you think could be the problem? Thanks.
@@pabloesquivel4528 Than i have not really a clue, without further investigation. Do your thread devices get an additional IPv6-IP-address for the routing process? Does sending a ping to google-dns-server from a thread device reaches the border router (tcpdump)?
@@wsniot Greetings, Markus. It seems that i was missing a step in the process. I had to run a command before " export NAT64=1 NAT64_SERVICE=openthread " right before the " build/bootstrap " command that you use on the video. That seems to have solved the problem for the br nat64prefix. I still cant succesfully ping a website globally, but Im working on it to see if i can solve this, It appears that i need to add a globally accessible IPv6 to the border router for it to be able to ping. Thanks for your responses!
I haven't tried it with the Xiao yet, but it could work because only the USB functionality is required and it works identically. The nRF52840 MDK USB dongle, for example, also works without any problems as a sniffer stick for Thread/IEEE802.15.4 and is also similar to the nRF52840 dongle.
Hi! I am working on some projects with nRF devices and your videos are very helpful, thanks a lot! One quick question I have: Do you know how to establish CoAP Block transfer from the Border Router to a nRF device using the OpenThread CoAP API? I have some issues there with the receive hook function. Just in case you once tried this, let me know :)
I haven't used block transfer yet. Haven't had to send any larger data packets yet. If I had a problem here, I would first test the transmission with the same software environment, i.e. block-wise communication between two Thread nRF modules with Zephyr. And of course log the network traffic with Wireshark and look at the CoAP packets. And if that doesn't work, you can than post the minimal example also in Nordic's devzone, their support is quiet good.
Hello, is it possible to work only with a raspberry pi and a nRF52840 Dongle as hardware to create a thread network at home? I build successfull with this video the OTBR and a test from your video works, but I cannot add matter devices to the OTBR. Can you help?
You mix here two things up. The OTBR just works as a bridge from the Thread network to an other IP network. You can provissioning Thread devices to this Thread network. A Matter network is a seperate network again which uses eather Thread/Wifi or your Lan as Transport. The network itself has it own credencials. To commisssion to this network you need a Matter controller.
As always very helpful.
Congratulations for such useful video, very insightful. One idea is using that seed tiny board, make it a thread node reading a button and/or sensor showing that handshake.... Regards.
I also noticed your videos are mainly on Nordic, you should try esp32 ic that also has the thread radio...
Awesome video
If the otbr is setup using a raspberry pi and nrf dongle how can i connect an eve door and window sensor to this network
👋Thanks for making all these tutorials. These are very helpful. I am recently struggling with multi-protocol Thread network using nRF microcontrollers. Would it be possible for you to record a tutorial on how to have multi-protocol Thread network with BLE?
I have already in mind to make a tutorial for BLE, already prepared a few things. Multi-protocol will maybe come after this.
@@wsniot That’s great. Looking forward to it. One more request, would love to see SEED and REED setup in a Thread network 🙏
Hello @wsniot, I am not able to read uart via putty with port ComX. I seen it inside Device Manager -> Ports (COM & LPT)
Were you able to add a global IPv6 address with the 2000::/3 prefix?
Thank you for the wonderful video! I want to communicate the signal from each sensor in the way shown in this video using a raspberry pi. For example, if I want to send the value of the heart rate sensor to the raspberry pi combined with the nRF52840 dongle(BorderRouter), should the heart rate sensor be connected to the combination of Arduino and nRF52840DK board? Or do I have to connect it to the new Raspberry Pi and nRF52840 dongle combination?
Hi! Thank you for the tutorial. I am working on some projects with matter. Is it possible to make an esp32 S2 as a client device instead of nRF52840-dk?
Good video! Thank you for sharing! I was wondering two things …
1) If the Rpi was also configured with eg Homebridge & added to an existing Apple HomeKit could the Rpi gpio use the thread wireless route (via border router) as opposed to wifi ie to make communications more robust…
2) Also Could a second nrf52840 usb dongle be programmed to be an end device on the Apple HomeKit network to eg indicate both Digital & analogue inputs (switch operation or battery voltage)
Thx for the feedback.
To 1: I can't really answer that. Homekit and Thread both use IPv6, so at least routing should theoretically be possible with Homebridge installed. However, I have not worked with Homekit or Homebridge so far, so I cannot make any reliable statements on this.
To 2: Actually the same. I'm not familiar with Homekit. Theoretically, a nrf52840 dongle can be programmed to a thread device and send desired data to any thread device, including the home kit. However, I don't know what data the Homekit expect to process it.
Ok, no doubt time will tell…. thanks for the reply. Cheers Hugh
Hello! I have been following your videos to setup a border router, but when i reach around 21:28 im getting an invalidcommand error when i use the br nat64prefix command. Also, i cant seem to get the ping command to work. What do you think could be the problem? Thanks.
Did you use the command at the border router? Only the border router supports the br command.
@@wsniot thanks for your answer. Yes the command was used in the border router
@@pabloesquivel4528 Than i have not really a clue, without further investigation. Do your thread devices get an additional IPv6-IP-address for the routing process? Does sending a ping to google-dns-server from a thread device reaches the border router (tcpdump)?
@@wsniot Greetings, Markus. It seems that i was missing a step in the process. I had to run a command before " export NAT64=1 NAT64_SERVICE=openthread " right before the " build/bootstrap " command that you use on the video. That seems to have solved the problem for the br nat64prefix. I still cant succesfully ping a website globally, but Im working on it to see if i can solve this, It appears that i need to add a globally accessible IPv6 to the border router for it to be able to ping. Thanks for your responses!
Interesting - will it work with the XIAO devices too or do I need the Nordic dongles?
I haven't tried it with the Xiao yet, but it could work because only the USB functionality is required and it works identically. The nRF52840 MDK USB dongle, for example, also works without any problems as a sniffer stick for Thread/IEEE802.15.4 and is also similar to the nRF52840 dongle.
Can you please share your .txt file used in this video? Thanks!
Hi! I am working on some projects with nRF devices and your videos are very helpful, thanks a lot! One quick question I have: Do you know how to establish CoAP Block transfer from the Border Router to a nRF device using the OpenThread CoAP API? I have some issues there with the receive hook function. Just in case you once tried this, let me know :)
I haven't used block transfer yet. Haven't had to send any larger data packets yet. If I had a problem here, I would first test the transmission with the same software environment, i.e. block-wise communication between two Thread nRF modules with Zephyr. And of course log the network traffic with Wireshark and look at the CoAP packets. And if that doesn't work, you can than post the minimal example also in Nordic's devzone, their support is quiet good.
Hello, is it possible to work only with a raspberry pi and a nRF52840 Dongle as hardware to create a thread network at home?
I build successfull with this video the OTBR and a test from your video works, but I cannot add matter devices to the OTBR.
Can you help?
You mix here two things up. The OTBR just works as a bridge from the Thread network to an other IP network. You can provissioning Thread devices to this Thread network. A Matter network is a seperate network again which uses eather Thread/Wifi or your Lan as Transport. The network itself has it own credencials. To commisssion to this network you need a Matter controller.
Hello @jojos1203, Did you add matter devices to the OTBR or Matter controller with any approach? If yes, then can you help me with your approach?
@@RaghavParwal-ko5othello, I tried connecting a Matter device to it. But I didn't make it and then I gave up.
Hi @@jojos1203, May I know how did you tried connecting a matter device to it means what process you implement?