Skip to content
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

Sonos speakers returning "No Response", effecting all HomeKit Triggers when this happens. #36

Open
leoneleone opened this issue Aug 21, 2016 · 4 comments

Comments

@leoneleone
Copy link

This happens at least once every 24 hours. My Sonos speakers return "No Response" in HomeKit, all my other devices from other plugins seems to be working fine. Well my Sonos plugin fails, any and all of my configured triggers and rules stop working, even if the Sonos speakers are not part of the trigger or the scenes being triggered.

The only way to solve this is restart homebridge until the Sonos devices start to give a response in HomeKit. Is there any way to stop this "No Response" from happening. It's becoming quite annoying now 😔

Any help is much appreciated.
Thanks

@leoneleone
Copy link
Author

leoneleone commented Aug 25, 2016

I'm sorry to say this plugin is very unstable for me. It's causing everything in HomeKit to be unreponsive, and it's causing disconnection issues on the Sonos side as well. I've removed it from my HomeKit configuration and everything is far more stable now.

Please update this plugin and fix the disconnect/stability issues

@Phononaut
Copy link

What are you running this on? I have mine on a RPi2 Rasbian jesse and it is super stable, have run homebridge with the sonos and nest plugins for 30 days straight without a single hiccup, I wonder if the OS/hardware it is running on makes a difference. Just updated to iOS 10 yesterday, so far no issues to note

@leoneleone
Copy link
Author

Same setup for me. It's only one or two of my Sonos speakers that seem to be problematic and consistently return "No Response".

I'll Debug and try to pinpoint the issue

@fwboettger
Copy link
Contributor

@leoneleone - you might want to take a look at pull request #39 . Could potentially be related and be a solution to this situation, would be worthwhile checking i believe. Would be great if you could update in case you'd be able to try this out and would see improvements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants