Thanks, but the bug descriptionspecifies that it was fixed:

Fixed-In

4.1(171.0)

I supose that 5.0.148 is newer than 4.1.171

So? now I'm lost

With wireless, your looking at different trains of code between 4.1 and 5.0

Fixed in the 4.1 train does not mean fixed in the 5.0 train.

The bug would need to say it was fixed in the 5.0 train. Check the release notes in 5.0.148....there are a number of crash/reboot related bugs other than the one mentioned. For now, your options are to live with the bugs in 5.0 or downgrade to 4.2.130 and loose some features.

If you don't have 1252's to support, I would suggest using 4.1.185. If you want to use 4.2 then go with the latest 4.2. 5.0 has too many issues.

What is taking so long for a 5.0 code refresh? It came out in Feb and no interim updates yet to resolve some killer bugs.

Well the thing is that they are going to bring the mesh train back into the same code for 5.1. So I would say that 4.2 is your best bet until all the bugs from 5.0 and 5.1 are fixed.