Seems that reading the value of a JSON element with value null triggered the message; after handling the "Jsonelem_type_empty" case separately (and not accessing the element's value at all), the message disappeared.

Funny somehow, that the printed message refers to a datatype 0 - in Carl's findings here you can see that this type should have the value 64...