I have 2 buildings on 5 acres with a total of 3 panels (2 for main home, 1 for detached shop 200' away. I originally had X10 modules throughout and would experience signal problems on a regular basis. I started out forcing AHP to send multiple command repeats to make them work. After following the various troubleshooting guides and talking to the experts here (especially Jeff Volp, dhouston, Brian H, etc) I was able to systematically locate the issues (of which I had several) and develop a scheme to address each one. If I had continued down the same path of blindly trying things, buying different modules, changing settings, etc without understanding the problem, I'd have a huge system footprint with no expectation of stability. As it is now, I've had 1 failure in 2 years and bend rick stable for much longer (2016 or 2017).
There are some very knowledgeable people who frequent this forum and are very happy to help as they can. I'd encourage you to look for a solution to the source of the signal or module problems over brute force but both will technically work.
The code I posted in my github page were all developed by me (with some framework derived from other projects in a couple cases). They are all documented in the code but I do not write a separate document outside of that. Each code has a specific goal that I needed filled and may not be useful for anyone else. The stuck module code was designed to detect a RF sensor being left in the on state which can happen if the RF "OFF" is not received which is not uncommon for MS16 or other X10 RF motion sensors which send a flood of "ON" commands but a single "OFF". The code simply starts a timer when an "ON" is received and if OFF isnt seen before the time is up it turns the sensor off. My prior comment was suggesting that it might be close to what you were looking for and with a little tweaking could be adapted to your needs. I do not recommend that approach since I found Gene's code that does exactly what you need.