UDP string

horace:
an alternative and probably simpler technique was suggested in post #3 by @GoForSmoke where you look at the bytes as they arrive for the sequence "STATUS" and the required data then follows

As a kind of work-up to that, the code can buffer the text (know you have a whole line, serial has no guarantees) and the "walk through the array" using an index to address it a char at a time. With decently optimized code the speed that you could that will be very close to the speed of string.h functions like strstr().

You gain inside knowledge of what otherwise may be a "black box" function that you call with no understanding of how it works. It will appear mysteriously complex and you won't know so well how it deals with your data which means you can easily miss shortcuts/tricks that can simplify and speed your code and how fast you get the code done.

I've done both ways for more hours than I'd like to try counting. I prefer to not need string.h functions but when I do, I'm glad they're there. I spent time writing my own versions of some string.h commands just to know better, time well wasted as I used what I learned to not need string.h functions!