Hey @maheshgv,

Thanks for letting us know about this. A few users have mentioned something similar so our engineering team is looking at it directly. I am seeing a few similar reports on our subreddit and this was my response there.

For the Deco update, you may perform a firmware recovery to downgrade to a previous version. However, we expect the behavior to be fixed in an update soon.

You may try assigning an IP reservation for the device to see if the device is able to connect via that IP address, and then be able to roam between the satellite nodes with that same IP address.

From what I am seeing it mainly pertains to the 1.2.2 Firmware Version so only a few of the models listed above are affected, but our teams are aware and are looking into a fix.

---

The Reddit user found that the behavior appears to be mostly limited to devices that are connecting to the IoT network of the satellite nodes - with them being able to connect but not able to receive an IP address. The short-term solution for the user was to force problematic devices to use the main Deco for its connection with the new signal preference feature.

  @jax54321,

All firmware updates are releasing gradually as the firmware is developed. The XE75 Pro was released later than the XE75 and has a different set of ethernet ports for multigig connectivity. With the XE75 receiving the update, I would expect the pro to not be too too far behind.

Unfortunately, our teams don't have any insights into what models may receive the update and when it may happen, so your best bet is to keep an eye out for any updates as additional models are receiving the firmware each week. I even have a few models to add to this list from just the last few days.

  @maheshgv,

While it is not specifically listed, you can use the HTTP u-boot method for the XE5300 - the models listed are simply examples of compatible models, and the main difference is the presence of a web UI and not. If you look at the dropdown for compatible products, almost every Deco model is listed there.

If the behavior is limited to your satellite nodes, you may try resetting and adding them to the network again. This may help clear up any miscommunications between nodes, especially since their LED status is not matching their connectivity status.

I would still recommend trying to create an IP reservation, as this would automatically assign the IP address to that device and may allow a path for communication.

  @maheshgv,

Do you know what model and hardware version that specific node is?

Also, how do you have your network configured? Are the satellite nodes connected with a wire or wireless signal? 

If the last Deco is at the edge of your range, you may try to configure the Deco closer to your main node so that the device is not trying to wirelessly daisy chain your satellite nodes.

If your Decos are wired, you may try to change the configuration, such as using wireless backhaul, or adding/removing a network switch to the mix.