Samfox2/homebridge-videodoorbell

Cameras

UKenGB opened this issue · 11 comments

How do multiple cameras work?
Do they appear separately in Home.app?
Does button push event Notification end snapshot of only the camera with port specified in HTTP POST?
Can the same Platform be used with multiple cameras, one at each of 2 different doors?
Would it be possible to have a 'Camera' with no actual camera (no videoConfig section?), so just use with a button that triggers the notification?

They appear as different cameras and triggered with their specific port. One platform can handle multiple cameras. As this is a videodoorbell-plugin a camera should be assigned. However you can put anything in the source part and do only use the trigger but the cam will show up in home app with a black image.

That's what I thought. Thing is, I added another camera with 'sources' that all work as they should and other parameters same or similar to the first one, but now nothing works. The config is all good and saves without error and I've restarted Homebridge several times, but testing by sending 'curl…' with either of the specified ports produces no Notification at all.
I'll cut the extra camera and see if it works again, but at the moment it looks like more than one camera stops it working.

Cutting the new camera didn't help and the original cam no longer works.
I changed some names, are they sync'd with HomeKit so no longer linked?
I'll check in Home.app.

Yup, Home.app cannot find them. Name change completely confused it. Shame there's no way to simply update Home.app for new names.

Removed and re-added them and now I am getting appropriate Notifications for both cams.

Yes sometimes those syncing issues between icloud and ios devices are really a pain.

…As this is a videodoorbell-plugin a camera should be assigned. However you can put anything in the source part and do only use the trigger but the cam will show up in home app with a black image.

Would I be correct in thinking that although a missing 'source' line prevents Homebridge from even starting, 'stillImageSource' is not actually required?

An actual question though, should I not be able to point "stillImageSource" to an image on the Homebridge server and have that appear in Home.app? I tried that with the absolute path to an image on that server, but it never appeared in Home.app. There is an issue with Apple's app anyway as it keeps using the last image it found, even though Homebridge's config now points to a totally different image. Home.app needs a 'Refresh' button.

But back to using a static image, should I be able to point to an image file located on the server and in which case, what would be the correct path?

Yes, still image part is not required. It should also work with static images. If you have any issues with that, please try to check the resolution of the image first. It has to be supported by homekit. If it is still not working, please make sure that both image path and access rights are ok. Homebridge user needs to be allowed to read the image.

Ah thanks, didn't realise HomeKit had specific resolution requirements. Can you let me know what they are, or point me to this info somewhere?

I'll check perms again, but should be good to read.

You can see them in file ffmpeg.js at the beginning where resolutions are checked.

It simply checks which maximum compatible resolution is supported an can be used.