I just bought a Deco X60 TpLink WiFi6 router and now I cannot talk to my IOT devices (esp32 and D1mini and esp8266). Anyone seen this ...and is there a good solution... my shades, dog scale, garage doors,doors,windows,fireplace no longer work.
Thanks for any help.
Tim
Shot in the dark here - did you set the router up to use WPA3 authentication? If so, step it down to WPA2.
Also, wanted to add - while you have not described any issues with zigbee devices, be aware that Deco mesh routers set the width of the 2.4 GHz WiFi channel to be 40 MHz. They are also known to "optimize" after a firmware update to select a new 2.4 GHz WiFi channel. Both these issues can interfere with zigbee mesh networks (zigbee also uses the 2.4 GHz spectrum).
1 Like
As does Thread, which will become more popular as Matter over Thread devices mature.
2 Likes
I added a new Deco mesh many months ago and I started having join issues with older SmartThings devices. Just after that I put in solar and my system talks to the controllers via ZigBee. 
So between these 2 new users of ZB spectrum I have had to change my Hub 3 times.
20 to 15 to 11 now and things look ok except I can't get my ST Arrival sensors to work at all now. I have ble gateway/tags on the way to solve that, hopefully.
If you let Deco optomize the RF network then use a WiFI scanner you can possibly move to a clearer channel on the hub.
Have you considered returning the Deco system and looking for something else that provides much more flexibility in configuring the wireless networks (channels, channel width, etc...) to help make sure that your 2.4GHz Zigbee (and possibly Thread in the future) mesh networks are not impacted?
I have a full Ubiquiti UniFi network and I really like the flexibility it offers in terms of allowing me to configure everything as I see fit, rather than being forced to accept what some other system thinks is best.
Prior to the UniFi network hardware, I was using Asus Routers which also allowed for the detailed configuration options that I wanted to keep my Zigbee networks in the clear of my 2.4GHz WiFi network.
1 Like
thanks for all the great advice ... I will look at that Ubiquti... so I realize now that what likely happened was that the IP address changed and was not locked down by the new router ... I need to confirm that when I get home... @ogiewon hubduino still needs the IP address set in code vs using a hostname or mac address right ?
1 Like
I second this suggestion. I just moved from a setup with a Firewalla Gold router and TP-Link access points to a Ubiquiti Unifi setup. There is a bit of a learning curve, but the performance is excellent, and my zigbee mesh is rock-stable.
You will need a Unifi Cloud Gateway and as many access points as you find necessary for your house.
The only real issues I have found with Deco is 2.4 has n channel width adjustment which is not uncommon for a lot of WiFi routers.
The network optimization is fine for untechie people but I do wish I could just pick a channel.
Maybe I'll do something pointless like send support a feature request. 
1 Like
Pointless would be a good description. Here's a link to a 5 year-old request on the TP-Link community, along with the "Accepted Solution" from their Support Staff.
Ha, thanks for the link.
So according to Sesame Street, D(eco) is for Dummies.
I do get their market, we are the 1%.
1 Like
That is the most common method of addressing a HubDuino microcontroller device. However, there is also support for DHCP if one wants to use it. Of course, using DHCP for HubDuino does REQUIRE a DHCP Reservation on the router, as the IP address must not change in order for the Hubitat Hub to be able to communicate with the microcontroller.
If you're curious about using DHCP with HubDuino, just let me know. It is a simple comment out one line of code in the sketch, and uncomment another line of code. If you look in your sketch, it'll probably be fairly obvious.
1 Like
Plus, their WiFi-based smart home devices work fine with their mesh systems.
Dan, so thats how I had it setup with the old router...DHCP address reserved ...so of course when I switched to the new router I did not/forgot to RESERVE the DHCP address. My question was more of whether the hubduino device could have a network name OR specify the mac address and allow the IP to change (not require the reservation)
Nope! Definitely needs a fixed IP address for both the Hubitat Hub and the HubDuino microcontroller.
1 Like
so I found that the Deco has a separate IoT network that you can configure.
I did so and then changed my Hubduino D1mini to the new SSID and password and enabled the IoT network...
The D1mini will not show on this new IoT network...
arg....
@ogiewon actually if the device was on an IOT network with ssid A and the hub was on a network with ssid B would hubduino still work... it seems like they don't have a different IP address range best I can tell...
well if finally showed up on the IoT network and everything works even though the hub and IoT device have different ssid's
1 Like
well i guess not so fast, my D1mini and esp8266 showed up on the IoT network but then later showed not connected (although they were connected and devices still worked)
My esp32 device says it connected to IoT network on serial monitor but could not be found in the app.
I have a request to support but will be returning if not resolved.
I like the idea of the router having an IoT network...
Is there other 3 unit mesh routers in the approx $200 range that have that feature?
(the Ubiquiti seem a little out of my price range 
Just to double-check: have you tried using WPA2 authentication on the Deco system? I believe it defaults to WPA3.
Just to add a data point with respect to WPA wireless security versions... IIRC, on my UniFi Access Point that supports WiFi 6e/WiFi 7, WPA3 is required for using the 6GHz radio. WPA2 is allowed for 2.4GHz and 5GHz radios. For a little while this caused issues for my older 2.4GHz devices as they do not support WPA3. I had to create one SSID for 2.4GHz/5GHz and another for 6GHz to avoid this issue. I believe Ubiquiti may have improved this in later software versions. Just something to consider, as the Deco platform might be forcing WPA3 if using the 6GHz radio.
1 Like
