Take a look at: https://github.com/domoticz/domoticz/blob/a668baf917333e93f92dd9bb7c77eef8e0bc4ce4/hardware/MySensorsBase.cpp#L486
//V_TRIPPED
//V_ARMED
//V_LOCK_STATUS
//V_STATUS
//V_PERCENTAGE
//V_SCENE_ON
//V_SCENE_OFF
//V_UP
//V_DOWN
//V_STOP
//V_RGB
//V_RGBW
@sindrome73 said in Request data from Domoticz:
Hello
So if I understand, a node from domoticz can only ask the status of a sensor connected already him, and not the status of other nodes of the network!
So it is impossible for me to create nodes / displays to display the status of other sensors in the network.
The only way is to use some old mobile phone as a display point
You can directly request data from other node(nothing to do with domoticz).
From documentation: https://www.mysensors.org/download/sensor_api_20#requesting-data
Requests a variable value from gateway or some other sensor in the radio network.
void request(uint8_t childSensorId, uint8_t variableType, uint8_t destination);
childSensorId - The unique child id for the different sensors connected to this Arduino. 0-254.
variableType - The variableType to fetch.
destination - The nodeId of other node to request data from in radio network. Default is gateway.
Other way is that you can present some text sensors in your "screen" node and update those from scripts at domoticz.
Are your lights and temp sensors MySensored or would you like to get status from some random Domoticz devices?
another is having each node listen before transmitting
How would you describe this functionality in MySensors rs485 code?
https://github.com/mysensors/MySensors/blob/f5ed26c778c18107d1516bd86704f8c8f99ff571/hal/transport/RS485/MyTransportRS485.cpp#L246
If I'm reading the code correctly it is exactly reading the bus and making sure no other node is sending before sending anything.
The place where collision can happen is those 5 microseconds what the node is waiting to get driver tx enabled pin up.
So the collision avoidance is already there. So what MyS R485 transport is missing is collision detection and recovery from collision.
CAN bus( a mutli master 485 comaptible bus) is another option.
Its disadvantage is small payload size.
@nofox Its quite like how the Modbus works. By polling.
I think there is some better ways to do that. Check these out from google:
How about presenting additional S_BINARY/V_STATUS in your node. In domoticz when text changes set this to ON/OFF. From there you now its time to request text from domoticz.
@dbemowsk said in Domoticz help using V_VAR1 and S_CUSTOM:
So my questions are, first, are the V_VARx variables working? And if they are working, are they accessible from a device like the irrigation node?
There is the current state of V_VARx variables in domoticz: MySensors set and send V_VAR
And there is what you can store/request: hardware/MySensorsBase.cpp#L2241
@bbrowaros It has happened to me so many times that it was easy to guess 
@bbrowaros Have you enabled: "Accept new devices" from settings?
Cannot get the point what you exactly mean but I think you should check for what child the message is for:
if(message.sensor == CHILD_ID_aeg2 && message.type == ...) { ..do suff.. }