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

node 8.0.0 with last version homebridge - mqtt updates dont work #1318

Closed
uronito opened this issue Jun 3, 2017 · 6 comments
Closed

node 8.0.0 with last version homebridge - mqtt updates dont work #1318

uronito opened this issue Jun 3, 2017 · 6 comments
Labels

Comments

@uronito
Copy link

uronito commented Jun 3, 2017

with node 8.0.0 and last version of homebridge mqtt updates dont work

@rswilem
Copy link

rswilem commented Jun 6, 2017

I think this issue is related to npm module caching.
Have answered this question here:

PatchworkBoy/homebridge-edomoticz#83

@uronito
Copy link
Author

uronito commented Jun 6, 2017

Hi @xTheRamon , i tried this option and homekit work correctly, But real-time updates per mqtt only work the first two times. Then homekit is still running but is no longer updated in real time. Not only edomoticz plugin, i have other plugins per mqtt and don't updates in realtime. In node 6.8.1 works correctly.

Thanks

@rswilem
Copy link

rswilem commented Jun 7, 2017

Hi @uronito,

Thank you for your clarification. I have forwarded your issue to https://github.com/KhaosT/HAP-NodeJS/issues/455.

I'm experiencing the same problem myself.

Thank you.

@rswilem
Copy link

rswilem commented Jul 20, 2017

Hi @uronito

Please update all of the modules to the latest version (npm update) in the homebridge directory.
I can confirm the issue is now resolved.

nodejs/node#13391

@uronito
Copy link
Author

uronito commented Jul 24, 2017

Thanks @xTheRamon !!!!!!

Regards

@stale
Copy link

stale bot commented Jan 20, 2018

This issue has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this issue was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

@stale stale bot added the stale label Jan 20, 2018
@stale stale bot closed this as completed Feb 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants