Øyvind Matheson Wergeland

Have you verified that target `staging` exists in `.firebaserc` and `firebase.json`?

We get the same warning in the log even with a `fixed` rollout strategy. ESPv2 logs the warning about every 130 seconds. ``` I1208 15:19:43.828927 7 config_manager.go:319] Envoy Dynamic Configuration...

I had to set `contents: read` in addition to the write permissions to avoid checkout failing with `remote: Repository not found.`, as per https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions > If you specify the access...

@niro1987 This PR works for me as well. Got all my existing entities (alarm panel, locks, binary sensors (doors and ethernet status), humidity, temperature, camera). Great work so far! I...

The passcode/lock issue is handled in issue #86963 After reading through the earlier comment, I understand this is to originally be about that the Verisure integration requires reload after restart...

I have already submitted PR #340 to address this. Would be good if some of the maintainers could follow up before Node 16 is sunset!

> Actions are now failing: That is most likely some other problem with your job. Sunset date for node 16 has not yet been communicated.

@johnnyoshika > This workaround to set a node version doesn't work: This is to set the node version your build uses, not the version used by the action itself. @steve-scorn:...

> The error is still occurring. It will occur until a fix is merged and released. Workaround is described here: https://github.com/FirebaseExtended/action-hosting-deploy/issues/341#issuecomment-1952388122

Fixed by #344 This issue can be closed. Can we please get a release?