[BUG] No response in debug window

[thomasssso]

Hey all,

New on github and working on a RPI with node-red and homekit. Happy about the easy setup. One thing is driving me crazy. I seem to not get any data in my debug window. The state updates on the node but no msg is created. (first time use it works, after another deploy there is no trigger made any more)

I any error logs are required let me know. Curious about the community.

[crxporter]

I would guess your issue is with the deploy bug - see #118 for the temporary fix.

My recommendation to (mostly) avoid the issue is set node red to deploy only modified nodes. Then you’ll only have problems when you change a homekit node.

Rumor is that @shaquu has a fix for this in mind, hopefully coming soon! Welcome to the community!

[thomasssso]

Ai, this does look like a big bug to fix for the developers... Hopefully it is quickly resolved. Every time updating the bridge is a hassle, but does solve the problem.

[crxporter]

I'd like to mention that while this is an important bug to fix, the plugin here is far more advanced and capable than any other node-red option...

The only time this issue will arise is when you've made changes to a homekit node. Once it's set up, everything runs great. The way I deal with it is to leave myself an inject node connected to an exec node - the exec node simply runs sudo systemctl restart nodered.service. This way when I'm changing my homekit nodes, I can just hit that inject button and have things back. The restart only takes 5 seconds or so on my RPI 3 B+.

Looks like this:

[benchuk]

Any news about this bug? I am running Pi model B (2011) with buster image and the restart are very slow - so making changes are getting harder - I would love to help and fix this bug if someone can point me at the right direction.

[crxporter]

@benchuk - I believe the plan for the coming version 1 is to run homekit as a separate process from nodered. This should make the deploy work as expected. here is the most recent comment from the main developer about fixing this bug.

That being said- are you restarting the whole pi or just your nodered.service? I run a few pi zero’s and the node red restart only takes about 30 seconds on those...

[benchuk]

@crxporter Thanks for the fast replay :) . I restart the service only (no need to restart the PI). (node-red-stopthen node-red-start)

[Shaquu]

What @crxporter wrote here is true. I’m working to make NRCHKB better and more reliable.

I am testing on pi0 so I will make sure it’s reasonable to run on slower machines as well.

_{Sent with GitHawk}

[benchuk]

@Shaquu Hi, sound great!! Btw I will be more than happy to help if needed...

_{Sent with GitHawk}

[thomasssso]

@crxporter thanks for the quick fix, my system takes approx 15 seconds and after that everything is up and running again. Hope you get this issue solved. I would like to keep this ticket open for other users so the know this solution. Don't know if that is the right thing to do.

[Shaquu]

I am closing this Issue as it is old. If you need more help then comment or feel free to open new one.

In case of problems follow #118 as we have some well known bugs right now. If solution not worked then comment and we will figure it out :)