Recent content by Aspiring Geek

Also using Yoosee 24/7 with BI setup, attached to Yoosee wifi chime. Two-way communication works through the Yoosee app on phone/ipad, but is cumbersome (one needs to have the app always open in background, otherwise it takes too much time to pull it up and initiate conversation). Effectively...

After your comment, I also reverted to Cam #1, and unchecked the “Get ONVIF Trigger Events”, using BI only, not the camera. All of these individually did not work - collectively they did.

Ok - now have it working again after reviewing another Yoosee thread on this site (page 6of 24) which contains a recommended set up from Yoosee support. I unchecked the “RTSP keep alives” checkbox. This was also unsuccessful - at least not in the time frame I waited. Yoosee does say in that...

Also doesn’t matter whether I specify Cam#1 or Cam5 - the latter being the correct number allocated elsewhere in the BI add-camera process.

Thanks for response. Yes, have deleted and reinstalled the camera several times, with and without it connected in the Yoosee app on phone and iPad (where it works)! Have used the find/inspect button too. When it worked previously, BI found the stream without having to specify the stream in...

Trying to add Yoosee front doorbell camera to BI (5.3.9.3 x64, 7 Feb 2021. Have been looking for a POE front doorbell camera with WiFi ringer, and this seemed to fit the bill - and it was cheap! Thought I would try it out. I had this working and visible on an earlier version of BI, but then...

Ok. This seems to have fixed the problem (thanks to fenderman for the step-by-step diagnoses): In the video configuration of the camera, select encoding to be consistent with CPU capabilities - I had selected H.265, but my CPU can only handle H.264. Should have known this, but I am still only...

I think I understand your comment to mean that : if the cameras are set to H.265, and the processor doesn't support that, BI should not have given me the option to select any of the HA modes in the drop down tab? Which should have sent me straight back to the cameras to select H.264 instead...

Within BI, in the HA drop down box under the Video tab for each camera, there is a "No" option which is now selected, but there is no "yes" option - just several hardware specific options. I had selected "Intel", although another option available is "Intel+VPP".

In camera settings have only had bit rate changed to 4096 as you suggested, which had no impact. Cameras went from H.265 to H.264 and now back to H.265 BI change is that HA has been set to "No". CPU usage has gone up overall. Other than that, no change - except that triggers have stopped and...

The group of three we have been discussing have had HA set to "No" in BI, and I have set them back to H.265 within the camera GUI. Have not set H.265+ to on Other cameras only support H.264 CPU at around 40% Extraneous false triggers seem to have ceased.....

OK - all cameras set HA to "No" within BI CPU at 34%

Ok - all cameras set to H.264 from H.265 - thanks! Current CPU at 20% Just to clarify - set HA within BI to "No" from "Intel" and test?

now happening on the third camera of the group. Cameras are DS-2CD2155FWD-I

i7 - 4790 with 8gb Ram the camera is triggered for some reason, with the green stripe, followed by nine successive triggers a couple of seconds apart (without the green stripe) - for no apparent reason.