1/858e-6 sec = 1165 Hz. They were likely trying for 1200 Hz, but the crystal was a bit off.
Somehow when they stack, they know where they are relative to the other pagers (at least something does).
Could the attacker write it themselves? Probably. Will reducing the cost by providing ready-made code increase attacks? Almost certainly. I wish that more people would consider whether releasing the code will be a net benefit (by enabling legitimate research, education, proof-of-concept demonstrations of vulnerability) or harm (by enabling malicious attacks). Even if the underlying exploit/vuln/feature is the same, form matters: A ready-to-use attack toolkit with multi-client management capability is much more likely to be useful to attackers than defenders, where a simple proof of concept that is hardcoded to show a pre-defined message with no easy way to change that is much less likely to be reused maliciously.
And pranking a pager system sounds pretty harmless, until you realize that a restaurant is likely quite strongly relying on it and essentially DoS'ing it has the potential to affect their business.
>Multiple keyboards call the same pager. The pager system long range supports multiple keyboard call the same restaurant pagers.
As an aside, all the church nursery references stand out to me. Are pager systems common for that and am I just out of touch?
[1] https://www.amazon.com/Retekess-Restaurant-Adjustable-Remind...
https://github.com/leedave/flipper-zero-meal-pager