@too said in Z probe Trigger value has no effect:
M558 P5 C"^io4.in" F1500 T12000
You're calling the full M558 line here in homez. I'm not sure, but I think this may be resetting your g31 to default values. If you only want to have two speeds for the G30 it would be easier to simply use two values for F in your M558 in config.g.
Ex: M558 P5 C"^io4.in" F1500:120 T12000
Otherwise, if you just want to alter a value in M558, just call it with the parameter you want to change.
Ex M558 F1500
The other thing that I notice is that your Z motors appear to be spread across the mainboard and expansion.
M584 X0.3 Y0.4 Z0.0:0.1:0.2:1.1
This may run into a limitation in RRF and it would be better to have all Z axis motors on the mainboard where the z probe connects.
Due to CAN latency the motors connected to expansion boards may slightly overshoot the position at which the endstop or Z probe was triggered. This would not usually matter for an endstop switch, but it does mean that if the Z motor(s) is/are connected to an expansion board then repeated probing with a Z probe (e.g. for mesh bed compensation) is not advisable. This will be fixed in a future release
