-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Segmentation Fault: 11 #8
Comments
It's not happening on my Homebridge, so maybe it's the newly added ping feature that's causing it. |
Hey,
I will try this out now without the Ping Module!
Thanks for the suggestion.
…Sent from my iPad
On 17 Jun 2020, at 12:20, Shingo Takagi ***@***.***> wrote:
It's not happening on my Homebridge, so maybe it's the newly added ping feature that's causing it.
Could you remove the ping settings once and see if the problem occurs?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hey, I’ve been using it all day without the crash. Seems to be the ping module. Let me know if there’s any more logs I can provide. |
Thank you for the confirmation and the suggestion to provide a log. I'm sorry, but I can only work on it on weekends, so it will take some time. |
The |
I have released
Unfortunately, if you still have problems with https://github.com/zizi4n5/homebridge-switchbot-for-mac#ping |
Hey! Thanks for updating this so quickly. I have updated and inserted the new sample config and will let you know if I get the same error. With the printer switched off I am getting an error every second: [Error: No route to Host] followed by [Error: Host is down]. Which makes sense as the printer is off. But it does fill the homebridge terminal up. |
Wow! You’re the best. Thanks for being so responsive. Is there somewhere I can donate to your efforts? This is a great plugin. Can we hound you when the SwitchBot curtain comes out? Haha. I’ll update to 0.1.3. But I can confirm I haven’t had the segmentation error and Homebridge has been running for over 24 hours now. |
Hey! I just updated and now I'm getting this error: Church-Server:~ churchserver$ homebridge -V I've since uninstalled and downgraded back to 0.1.2 and now it's working. Is there something I need to change in the config code? `==================== [22/06/2020, 08:11:01] ====================
|
Sorry. |
That’s so strange - I updated Homebridge before raised the issue. But it looks like I’m incredibly out of date!
Do you know how I can force it from 0.4.53 to >1.0?
…Sent from my iPhone
On 22 Jun 2020, at 08:46, Shingo Takagi ***@***.***> wrote:
Sorry.
For TypeScript support, the required version of homebridge has been changed to 1.0.0 or later.
Is it possible to up-date homebridge to 1.0.0 or later?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hey! So I've done a bit of digging and homebridge -V isn't representative of my current version. I think I need to update the link somehow between typing homebridge in the CLI and what's actually installed.. I think it might be linked to an old version. None the less I've installed Homebridge 1.1.0, updated to your 0.1.3 version and manually run the command:
And now it's behaving. |
Thanks for the confirmation. |
Hi,
Since installing the latest updateI'm now getting 'Segmentation Fault: 11'. Homebridge stops after a couple hours and I have to re-run it start.
I uninstalled the SwitchBot plugin and haven’t the issue since. Here is my config, and I attached the output of running in Debug Mode.
Versions:
Church-Server:~ churchserver$ node -v
v14.3.0
Church-Server:~ churchserver$ npm -v
6.14.5
Church-Server:~ churchserver$ homebridge -V
0.4.53
Mac OS 10.4
sudo homebridge -I -D.txt
The text was updated successfully, but these errors were encountered: