Document macOS Application Firewall blocking OCPP after brew upgrade - #1147
Merged
Conversation
naltatis
enabled auto-merge (squash)
August 7, 2026 09:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1146
Homebrew installs each evcc version under a new path, so the macOS Application Firewall treats every upgrade as a new, unapproved binary and silently drops incoming connections. This breaks OCPP chargers while everything else keeps working, and on a headless Mac the approval dialog is never seen.
Adds a caution to the upgrade section of the macOS installation page (both locales) with the command-line approval fix. Uses $(brew --prefix) so the path works on both Intel and Apple Silicon.