Node-red-contrib-homekit-bridged: [BUG] Debug option on Camera service doesn't seem to work

[feens]

Describe the bug
I'm having issues getting camera service to work with an RTSP stream. I've tried to debug this but all I get is ERROR: FFmpeg exited with code 1, and no further details, which isn't that helpful.

I'm running 0.8.0, and I've also tried changing my log level to debug in settings.js.

What's also interesting: the service seemed to be generating snapshots fine.

[Shaquu]

You can run node-red in debug mode. It might help to see what is an error.

[feens]

I'm not sure where this magical "debug" mode is for node-red. Reading the docs, all I can find is the option to set which log-level to use. As noted above, I tried debug which didn't give me any more information for the camera stuff. I even tried trace, which still gives me the same output of ERROR: FFmpeg exited with code 1 when I try and access the stream in the Home app.

[Shaquu]

How can I generate Debug logs?

Stop your node-red instance and start it again using the following command:
DEBUG=NRCHKB,NRCHKB_Camera node-red

This should output detailed information regarding everything in the homekit context.

Also read #16

[radokristof]

@Shaquu I also have a problem and I know why.
I want to use video codec copy but I can't clear the video filter (and copy and video filter cannot be used together) because the default is scale=1280:720. Can I somehow override this?

[radokristof]

Did a quick and dirty solution, but this should be corrected and video-filter (and maybe all additional parameters) should be optional not required (now shows required in the Node-RED GUI) and also if no parameter specified, don't add defaults to the stream...

[Shaquu]

Did a quick and dirty solution, but this

Would like to make a PR?

[radokristof]

The solution involves that it now overwrites the vf local variable with an empty array (so now you can't supply video filters). However I think I can make them optional.

[feens]

Closing this as I was able to fix it...thanks!

[Shaquu]

I know it's closed but @radokristof still please make a PR :)

[radokristof]

I'm on it :) However I have a little time right now (I will have more next week) and I didn't figured out a neat way to do this... I'm not a JavaScript expert :)

[Shaquu]

I will open this Issue to not forget about it.

[feens]

@Shaquu unrelated, but didn't want to open an issue quite yet. I've noticed a weird issue while adding a second camera: both cameras are showing the same image as a still image. One of my cameras creates its own, so I have a URL provide for the still image source option. The second camera doesn't have this, so that option is blank. Both have Content selected for the snapshot option

[Shaquu]

@feens One bridge can have only one camera.
We should add a better info to readme and block adding second and more.

[feens]

@Shaquu oh interesting. Is that a limitation on HomeKit itself? It's interesting because the feeds both work.

[crxporter]

Is that a limitation on HomeKit itself

Yes. Homekit protocol mandates one camera per bridge.

[Shaquu]

@radokristof would you test latest dev if it solve the problem?
Now video filter should be able to be cleared and will not generate default value underneath.

[andreypopov]

remove required field please

[Shaquu]

@andreypopov @radokristof

Video Filter should now be fully optional in 1.0.3 (just released).
Let's discuss further problems in #214

To debug camera problem in NRCHKB with node-red you have to:

• start node-red in debug mode via DEBUG=NRCHKB* node-red
• tick debug option in Camera Control service node