Domoticz:

Starting with a native implementation, thanks to Ad for providing the RF interfaces.

Maybe best (for domoticz) to continue on the forum,
i need serial logs of all possible combinations and meaning

node-id;child-sensor-id;message-type;ack;sub-type;payload

we developers probably have to do some special tricks to get some nice sensors

for instance, it would be nice if there where subtypes for:

• Temp+Hum
• Temp+Hum+Baro
• Kwh+Watt
• Wind+Gust+Direction

I can not watch this forum, if you want to contribute, plz use the domoticz forum

As for Domoticz, you could make a forum post what you would like to see changed...
It might be a bit difficult to setup initially, working with idx values, but when you just go to the devices table, you can quickly find the correct idx.
As for the value type/name, that is stored in the correct influxdb password

So the series name comment does not make sense.

Now, the reason why i choose for the idx value, instead of a name, is because when you rename a device, the idx stays the same.
But on the other hand, when you have a cheap temperature sensor, and the battery runs out, you probably get a new device-id when inserting new batteries, so the idx changes.
You will also have to deal with scenarios when using other solutions.

As for username/password support, this will be added soon (i need to find some time, unless someone beats me to it).

If you have a better solution, you can always propose this on the forum/github

The code looks wrong to me

this

MyMessage msgC(SSR_B_ID, V_STATUS);

should probably be

MyMessage msgC(SSR_C_ID, V_STATUS);

The distance sensor is supported in the beta version of Domoticz