How denr01/fz-chiefcooker works
Project type and purpose
• Chief Cooker is a firmware “app” (plugin) for Flipper Zero (Momentum firmware) that receives, decodes, edits, stores, and re-sends restaurant pager signals via an external CC1101 Sub-GHz radio module.
Top-level logical layers
a. UI Layer
b. Application Core
c. Storage & Configuration
d. Hardware Abstraction
Main components
– UiManager (lib/ui/UiManager.hpp)
– Views (lib/ui/view/…)
– Screens (app/screen/MainMenuScreen, ScanStationsScreen, EditPagerScreen, etc.)
– Notifications UI (app/AppNotifications.hpp → lib/hardware/notification/Notification.hpp)
– App (app/App.hpp & AppConfig.hpp)
– Pager Module (app/pager/…)
• PagerReceiver (captures raw Sub-GHz payloads)
• ProtocolAndDecoderProvider (chooses correct app/pager/protocol/*Protocol & app/pager/decoder/*Decoder)
• PagerDecoder classes (Td157Decoder, L8RDecoder, etc.)
• PagerSerializer (serializes messages for storage or re-transmission)
• PagerAction (triggers sending or re-sending)
• SavedStationStrategy (logic for storing/naming stations)
– AppFileSystem (app/AppFileSystem.hpp)
– FileManager, Directory, FlipperFile (lib/file/*)
– Data models (app/pager/data/KnownStationData, NamedPagerData, StoredPagerData, ReceivedPagerData)
– SubGhzModule & FrequencyManager (lib/hardware/subghz/*)
– SubGhzPayload, SubGhzState, SubGhzReceivedData implementations
– Notification hardware (lib/hardware/notification/Notification.hpp)
– FlipperDolphin core helpers (lib/FlipperDolphin.hpp, HandlerContext.hpp)
Relationships and data flow
• On app startup, AppConfig + SavedStationData loaded from Storage → feeds Core & UI
Architectural patterns and principles
• Layered separation: UI, business logic, storage, hardware
• Strategy pattern: ProtocolAndDecoderProvider chooses a decoding strategy
• Adapter/Facade: AppFileSystem + lib/file classes wrap raw filesystem
• Modular design: each pager protocol, decoder, and screen is its own class/file