Error: This callback function has already been called by someone else...
See original GitHub issueHello guys,
thank you very much for the large progress you have made with version 0.6.0. I’m really exited how linked services work now. Right now the only issue I have with that is I got a lot of this message in my node-red-log:
18 Mar 14:35:26 - [error] [homekit-service:XXXXX-XXXX-temp] Error: This callback function has already been called by someone else; it can only be called one time.
It looks like this is cause by re-deploying modified flows on node-red but I haven’t figured out right now if this is based on changes on node-red-contrib-homekit-bridged-nodes or on changes of any other nodes as well.
Any ideas?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:20 (9 by maintainers)
Top Results From Across the Web
Error: This callback function has already been called ... - GitHub
Error: This callback function has already been called by someone else; it can only be called one time. #1075.
Read more >Callback function has already been called by someone else
I'm unable to to control my lights through homebridge or the home app with the latest 1.4.1 version. Here's what's happening in the...
Read more >How to make sure that a callback has NOT been called?
First of all, the function design could use improvement. It relies on the global variable cond , which is brittle; if cond changes...
Read more >How to prevent disasters caused by the callback getting called ...
In this situation execute() is the function of the third party module which I am using, and this callback gets called multiple times...
Read more >Frequently Asked Questions - Jasmine Documentation
How do I test async behavior that I don't have a promise or callback for, like a UI component that renders something after...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Please update to new version 0.6.1 using node-red. Then please retest this bug if it’s still occurs.
I’ll look at it