Well I can tell you I’ve had some interesting trials going through setting up 4-way and 3-way switches using all LZW31-SN’s for each switch. For both what I was able to get working was leaving parameter 22 alone. I reset all the switches, then joined one by one. Then got them all to talk using the zWave Association tool the 2 line dimmers with the 1 load dimmer. For the 3 and 4 way you need Groups 2 and 4 for each Line Dimmer configured like this…
Line Dimmer 1 Source --> Load Dimmer Destination
Line Dimmer 2 Source --> Load Dimmer Destination
So I had the same problem and I made a change and it’s fixed. I really don’t know what this change does other than fix the problem we are both having. What I did was unable the default Z wave toggle. See picture. Try that and let me know if it works. I also went into the smart things IDE website and made sure the parameter 22 was set at one and also performed a save from the website. After I did those two things the switch worked and continues to work from any of the three locations.
I had a similar problem with my switch. I set param 22 to value 1 through my z-wave bridge multiple times and it simply didn’t take until I set it locally through the switch.
What is strange is that according to my z-wave logs, the switch appeared to have successfully set the parameter via z-wave:
2020-07-19 14:22:57.182 Info, Node009, Response RTT 576 Average Response RTT 635
2020-07-19 14:22:57.182 Detail, Node009, Refreshed Value: old value=1, new value=1, type=list
2020-07-19 14:22:57.183 Detail, Node009, Changes to this value are not verified
2020-07-19 14:22:57.183 Info, Node009, Received Configuration report: Parameter=22, Value=1
2020-07-19 14:22:57.183 Detail, Node009, Expected reply and command class was received
2020-07-19 14:22:57.183 Detail, Node009, Message transaction complete
2020-07-19 14:22:57.183 Detail,
2020-07-19 14:22:57.183 Detail, Node009, Removing current message
2020-07-19 14:22:57.183 Detail, Node009, Notification: ValueChanged
Despite the logs purporting to show the value of parameter 22 to have already been set (old value=1), the switch did not function properly with my existing 3 and 4 way switches until the parameter was set locally at the switch.
Could this be a firmware bug? I have had no issues setting param 22 for momentary switches in the past, but this is the first time trying to switch it for a 3 way toggle and having it clearly be ignored when done over z-wave.