Dangling pointer in TheThingsMessage

[paulbendixen]

When calling TheThingsMessage::encodeDeviceData, the buffer pointer pointer gets set to a temporary array on the stack, this might happen to work in most cases, but if anything is called between encoding and sending, this might break horribly and is at least undefined behaviour.

[johanstokking]

Thanks for pointing out. Can you file a PR?