I would recommend selling those on Ebay ASAP before they depreciate too much.
For several grand you can get some top notch IP PoE cameras and a PoE switch, boxes of Cat6 cable and tools to do a good install.
Yes, cabling will take time - but the results are well worth it if you own the property.
Hi mate.My 2 Nest cams and my Nest Hello are still working in BI. Check to see if you RTMPS URL has changed. This has happened to me before.
Hi again.The RTMPS URL can be determined using Microsoft Edge. Go to your public link from the Nest camera in Edge. Right click on the video stream in Edge and go to inspect element. Copy the entire https URL. It should look something like this: "stream-us1-alfa.dropcam.com/nexus_aac/Unique Identifier"
You will need to remove the suffix after nexus. You then go into BI and select RTMPS and paste the URL. The corrected URL looks like this: "stream-us1-alfa.dropcam.com/nexus/Unique Identifier"
The quotes that I put in don't need to be included (I put them there because the forum is changing the links to something strange).
From reading other posts, it appears that Google removed the RTMPS URL section recently, but you can still use the same modified URL that they give you that is HTTPS.
I hope that this makes sense. If you have any questions just let me know.
Unfortunately this method no longer works. Now you need to select Nest/Dropcam as the make and RTMPS via public page as model and then put the public URL in the address bar in the camera properties.Does this still work? I used Microsoft Edge to "inspect element" for my Nest Hello but I don't see a link similar to what you mentioned "stream-us1..."