Hi
Thanks
The images - I think I have described either here on GitHub the pros and cons of current approach
Basically there is a single indigo plug-in thread managing images - this does nothing unless a HomeKit app is open somewhere wishing an image.
This to my mind is a good compromise as doesn’t matter whether 1 camera or 22 - and has NO impact on HomeKit other devices.
When an image is requested / the camera thread pulls an image from the camera and saves image locally. Meanwhile it gives HomeKit the previous image - as don’t want to hang HomeKit until image ready.
This means that images are always one cycle behind - if cycle 10 seconds then not noticeable, if cycle 60s then need 2 cycles to get most update image
So to some extent expected - and only other solution would be to pull images constantly (lots of overhead) so instantly available or wait for first image (will hang the whole HomeKit bridge until completed - and continue to hang as well for that matter)
&
New devices;
Yep they appear instantly all going well:
The other trick is they will appear in the default room for the HomeKitLink bridge that you have added them to. (This default room is created when you add the bridge by user selection).
Glenn
Sent from my iPhone using Tapatalk