Indeed, hence my initial question about the code. Why go through a loop to iterate over all values. If the purpose was to take only the last one a "payload = results[size-1]" would have been enough.

Having said that, looking at MySensors sensors/variables types, it seems that only the V_POSITION is ...

It seems that indeed, the payload gets truncated. I have made a test with a S_INFO sensor sending a V_TEXT. Below the result of the serial monitor and domoticz results:

I am not making any assumptions really (especially not of buggy behaviour), I am trying to understand how things work. Indeed for now I have not tested anything, I have just read the code. Hence the initial question "Have I missed something?"
I will not have my hand on the stuff needed to test for ...

@gizmocuz sorry to pester you regarding domoticz code but I have a question regarding the implementation of the V_CUSTOM variable. It seems that in the parseLine method, the part returning the variable from the domoticz db to the sensor is in the section of "message_type == MT_Set" where all the ...

In 'results', yes, but not in 'payload' which is used in the further processing.
In the case of the gps position, results.size would be 8,
Payload would successivelly be assigned results(5), results(6) and finally results(7). At the end of the loop, payload would only contain the altitude.
Equally ...

Hello,

I am trying to understand the code in MySensorBase.cpp.
In

void MySensorsBase::ParseLine()
{
if (m_bufferpos<2)
return;
std::string sLine((char*)&m_buffer);

//_log.Log(LOG_STATUS, sLine.c_str());

std::vector<std::string> results;
StringSplit(sLine, ";", results);
if (results.size ...