One user is having problem with one 200+ network with tuya TBGW that is updated to EZSP 6.7.8.0 from factory firmware 6.5.0.0 and is keeping the original config parameters in NVM and tuye is using key storage for all ZB3 devices and bellows is using hashed link keys
The that ending with that the key storage is not working then the new firmware have other setting then the original.
The network was getting one complete breakdown and hi is desperate getting it up and running.
The user is trying splitting the network to 3 or 4 system for getting up and working but its not so easy getting the NCP resetting but possible.
If implementing one "leave" function in ZHA_custom it being much easy to doing the oration, Sending the command and ZHA is very likely caching or getting problem but restarting ZHA shall forming the new parameters from ZHA config and all is being OK on the NCP side. Perhaps the command shall executing one (Z)HA restart command then its have executing the leave.
Not very nice way doing one reconfigure but its easy getting the user up and running but need "cleaning"" ZHA after that but better then having one 200+ network complete dead.
Or do you have one better way making the NCP being forces updating network key, PAN-ID and extended PAN-ID that is nervelessly for getting the network working OK without interfere with each other and getting thee "working mode" being initiated with "ZHA parameters" and getting the old away ?
One user is having problem with one 200+ network with tuya TBGW that is updated to EZSP 6.7.8.0 from factory firmware 6.5.0.0 and is keeping the original config parameters in NVM and tuye is using key storage for all ZB3 devices and bellows is using hashed link keys The that ending with that the key storage is not working then the new firmware have other setting then the original. The network was getting one complete breakdown and hi is desperate getting it up and running. The user is trying splitting the network to 3 or 4 system for getting up and working but its not so easy getting the NCP resetting but possible. If implementing one "leave" function in ZHA_custom it being much easy to doing the oration, Sending the command and ZHA is very likely caching or getting problem but restarting ZHA shall forming the new parameters from ZHA config and all is being OK on the NCP side. Perhaps the command shall executing one (Z)HA restart command then its have executing the leave.
Not very nice way doing one reconfigure but its easy getting the user up and running but need "cleaning"" ZHA after that but better then having one 200+ network complete dead.
Or do you have one better way making the NCP being forces updating network key, PAN-ID and extended PAN-ID that is nervelessly for getting the network working OK without interfere with each other and getting thee "working mode" being initiated with "ZHA parameters" and getting the old away ?