@wallyllama

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:

• RS-485 Token ring
• uLAN
• RS-485 RRP (Round Robin Protocol)
• CSMA/CA

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.. }

@phil2020 try this in your sketch: #define MY_TRANSPORT_WAIT_READY_MS (200ul)
Its the "timeout" for waiting connection to gateway. Default 0 -> wait infinitely(?).

@mick Its still in use. I had one bus freeze since last "update post".

The gateway did pull the line up to 190mV what seems to be enough to get traffic frozen. After "reboot" of the gateway it was still pulling the bus to 160mV so it must be some solder on wrong place and bad chinese pin headers or protoboards.. I have to rebuild the "motherboard" of the gateway..

@dbemowsk there is the same with tensioning with motor: Tevo Tarantula Single Motor Dual Z Axis

@dbemowsk There is one example: Anet A2 dual Z single motor