I've found that a lot of our issues arise in the bus wiring and termination in our case, because we have a lot of retrofits out there where we are forced to use the retro-hubs, but that's another issue altogether. We've been doing new installs with 22/8 or 22/10 to the keypads and then doing the 485 wiring in the panels. I've tended to stay away from using category cables for the keypads or using the normal hubs, really just a preference and possibly a holdover from installing "normal" systems and their requirements.
Usually screwy results add up to a bus address/type being duplicated causing crashes or errors, but that's common with almost any addressable system I've ever put in.
The one thing unique to the Elk's that I've noticed is a re-enrollment or even resending the panel data sometimes magically fixes the gremlins, even though everyone swears it's been put in and addressed correctly. I've found that if we make any changes to or rewires of the bus that it's just a best practice to re-enroll everything and verify all the devices using RP while connected. Can't say it happens often, but given what the panel and M1 family platform can do....
