send reset when EmberZNet sends error

[zsmartsystems]

send reset when EmberZNet sends error

[cschwer]

I will create a PR for this shortly.

[cdjackson]

It would be really good if you could take a look at the ASH/EZSP WIP PR (#122) as I'd like to move over to this some time soon. It needs a little more testing, but I've now tested it against ASH V2 with both EZSP versions 4 and 5 having updated the firmware to 5.10 and then back to 5.8. It still needs a bit more work on ASH V3, but as it stands the ASH V2 implementation now has more features as the current code so it would be good to get it migrated before doing too many more changes to the existing ASH handler.

Let me know what you think.

[cdjackson]

Resetting the NCP and continuing at the ASH level does not seem like it will resolve the issue. Once RESET, the NCP must be reconfigured - the VERSION command must be sent, endpoints configured, and the NCP brought back into operation again.

Instead of resetting the ASH layer, and leaving the NCP unusable at application layer, I propose to set the dongle link state offline and leave the application to resolve this by restarting the link.

There may be a case for performing this reinitialisation within the Dongle layer, and if someone thinks this is a better approach, we can look at this.

[cdjackson]

#430 notifies the upper layers that the NCP is in the ERROR state so that the upper layers can reinitialise the connection.

If there's a desire/need to do this lower down, then please open a new issue to discuss.