Comments

5 comments

  • Avatar
    Firewalla

    Not until there are some good use cases. Many IoT devices already doing this via their own devices. Example, apple TV, homepod and echo devices.

    0
    Comment actions Permalink
  • Avatar
    Erik Cobben

    That is exactly the use case, instead of using another device sending signals into the air, we want to have a device who is supporting all these protocols so you can manage iit centrally.

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    What is the app that you are using to manage them? just curious. My understanding is, the thread board router is very transparent.

    0
    Comment actions Permalink
  • Avatar
    Steven

    Based on research, I believe individuals are referring to the following;

    https://support.eero.com/hc/en-us/articles/360000104706-What-is-Thread

    Using Asus routers, when reaching out to their technical support, enabling a wifi router with Thread tends to be more hassle then its worth (hence their decision not to add that function) .  I have a lot of thread devices and has worked flawlessly.  I would be curious to know the true benefits as well when a lot of devices are already Thread border routers.

    Does anyone have experience they can share?

    0
    Comment actions Permalink
  • Avatar
    Mr Robinson

    I don't need this but one thing to consider for AP's being thread border routers is they are generally dispersed around the home for full connectivity.  Ones' homepods and apple tv's might not be in great locations.  So might improve the overall home thread routing efficiency by using AP's.  

     

    1
    Comment actions Permalink

Please sign in to leave a comment.