If you are looking to update Multisensor 6’s firmware by other means refer to the separate firmware article. **A workaround** until this is fixed is **migrating back to a 500 series stick**, using the migration tool 700500 series. This page presents download files and installation instructions to update your Multisensor 6’s Z-Wave firmware via HomeSeer’s OTA function and form part of the larger Multisensor 6 user guide. Failure to heal the network or individual nodes, especially in busy situations controller doesn't list some/any nodes as neighbors, etc.)

Floods of incoming reports that are transmitted over and over Failure to send anything (`TransmitStatus: Fail`) I already have the Gen 5 stick connected to all my devices using Z-Wave JS so wondering is there a way to transfer it all over to the new stick without having. I’ve recently bought the Z-Stick 7 as I got a really good deal so want to migrate my setup to it. Huge delays (up to 60 seconds) when sending messages Aeotec Z-Stick Gen 5 upgrade to Z-Stick 7. We believe the following symptoms are all caused by this: **If you want to help express the severity of this issue, please email Silabs and/or your stick manufacturer to let them know you are having zwave network problems so they are aware how many users this affects** # We're working with Silabs to get to the bottom of this. It looks like the stick is somehow blocked and simply doesn’t send anything, maybe not even the protocol level acknowledgements for receiving the messages, causing end nodes to repeat their messages over and over, making the situation even worse. When lots of reports reach the controller in a short time, the 700-series sticks are not able to send any message. * are relatively busy (lots of unsolicited reports like motion sensor, power meters)

It seems that **700-series sticks** (including the currently latest firmware 7.1 … 7) have some problems which mostly appear on networks that:

Homeseer update zstick