-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maximum call stack size exceeded at shim-array.js #517
Comments
Humm - Had a user of my plugin report the same, turns out it was a different plugin |
Thanks, @NorthernMan54 - which plug-in is causing this (assuming it's not mqttthing either!)? |
The rumour is myq
I’m also wondering if it’s possibly a npm issue
… On Dec 25, 2021, at 7:11 PM, David Miller ***@***.***> wrote:
Thanks, @NorthernMan54 - which plug-in is causing this (assuming it's not mqttthing either!)?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.
|
for me it was homebridge-fritz (0.9.5) somehow, but that didnt get updated in a long time, maybe some changes inside homebridge itself broke that old plugin. Now using homebridge-fritz-platform and it works fine |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since upgrading the plugin i get the following error when starting up homebridge
A downgrade of the version also doesn't fix the error above. Is there some temp file the plugin generates that maybe stops it from starting up?
No changes to config from it running to upgrading and starting it again. Downgraded all the way to 1.1.31 but error still persists.
The text was updated successfully, but these errors were encountered: