Blue Iris and Amazon Echo Show

I can stream the RSTP index feed from VLC but monocole does not want to work.

I have tried basic and digest authentication along with JPG and H.264 encoding.

Any other ideas?

My RTSP url looks like this:

rtsp:/user:pass@192.168.1.2:80/fence&w=1280&h=720

However user:pass is not allowed in monocole.
 
I love how we are all trying to get blue iris to integrate with Alexa and the echo show. I can’t believe how hard it is to do. I’ve given up.

But I do wonder if we should start a specific thread to see how many people would want this feature prioritised by blue iris for dev.

Maybe we can influence their backlog to prioritise this and have a single integration that works out of the box. If you agree like this and we can share the support and numbers with the blue iris dev.
 
  • Like
Reactions: jimmy0097, justwantv, Mel Patto and 1 other person
i got it working after some hours of testing, but i think at the moment it is too slow, it took about 10-14 secounds till i get the image.

Can't use it for "Alexa show door image".
 
I've worked on this extensively and had a flawless environment for about a year. Now I've broken it. I run Multiple Alexa's - Dot's and Show's. When I was first building out, I used the BI interface to 'connect to amazon echo'. it worked originally on the Echo show 5 (about 3 yrs back) but only would show 1 of my 5 cameras. Then I discovered the Monocle Gateway - and was able to get all of my camera's to display perfectly! Recent changes to requirements of Echo devices are causing problems, Amazon keeps moving the goalpost. By testing and tweaking the settings on the Monocle Gateway I was able to keep it working. It's important to understand there are TWO ways to run the gateway - a local 'service' (maybe you have a local computer you can dedicate) or the online web service (which I ultimately ended up going with). Once you have the gateway setup, it becomes test, test test. There are limits - such as the resolution, audio and even specifics about the cameras (I use only higher end Onvif units).

It's really simple to use Silk (the built in browser on your Alexa Show's) to set the home page of your BI Gui and go into kiosk mode. But thats not 'on demand'. I programmed my triggers to launch the doorbell cam on motion, as well as the ability to say 'Alexa, show the backyard'. And again, I repeat, this has all worked flawlessly now for a year. Until this month. What changed? Amazon - the new 10" moving screen model Gen 3. I can't get IT to display squat. And since I can't see logs really all I can see is the failure.

I'm coming to the decision point to send this 10" movable back. It's value - for $250 is it's camera 'follow me' and 10" screen size. It also has much better audio pickup and is generally a smarter device - but if I can't use it for the most important feature I need, I'm not really interested in it any more. I came here today having been a BI user since forever to see if anyone had any clues about forcing the gen3 (4?) echo 10 to work and haven't found much yet except this thread. I wanted to add - I have tried 2 times now to get support from Amazon - Nada. Tried their phone service and there online chat. Waited in queue for 2 hrs online and gave up, waited 30 mins on phone and gave up. Their just going to fingerpoint i've no doubt.
 
Update: During my previous post - I made a mistatement about Monocle. I said there are 2 ways to run it - and this was true but I described it incorrectly. The simple, basic way to get Monocle to run is this: Use the MonocleCam.com website, setup an account then setup cameras. These cameras - lets call them virtual - you can either point directly at the camera which gives the fastest response, or point at the BlueIris stream. I won't detail the string difference here. The BI stream is MUCH more compatible and I am able to get 5 different manufacturer cameras to display on my Alexa Show's :). Then, if you're still having problems, you can push further and install a local service called Monocle-gateway. This tool is like an internal interface so Alexa can get a) a tls stream, b) a validated SSL response. There are configuration options on the gateway that can be used to get even really stubborn cameras to work.
Some quick info - If I get a direct stream from an ONVIF via the Monocle Web - from Alexa "OK" to an image is about 6 seconds. If I display the stream from the BlueIris server it is more like 11 secs. If I display the BI stream via Monocle WITH a local gateway the time is nearly 20 secs (and the video is actually 20 seconds behind as well!).
I am able to get all my cameras to work WITHOUT the internal gateway. HOWEVER. Recently I implemented a Alexa Show 10" gen 3. Thats the motorized screen model. It has failed. I have done everything I can to resolve this - including trying @proxy, @tunnel, @noaudio, @fakefmtp. I validated the SSL, checked all my settings and I can see the feeds on ALL my Alexas's EXCEPT the new 10" gen 3. I contacted Amazon and got diddly for help. They simply point at the camera manufacturer. Since Onvif is a standard, it's BS. They know it, and I know it. So it is going back. If anyone cares, I have some posts on Monocle gateway including logs from the amazon side. I came here today in hopes of finding notes or progress from BI changes that might improve the situation but see no joy.
 
R4nger said:
I can stream the RSTP index feed from VLC but monocole does not want to work.

I have tried basic and digest authentication along with JPG and H.264 encoding.

Any other ideas?

My RTSP url looks like this:

rtsp:/user:pass@192.168.1.2:80/fence&w=1280&h=720

However user:pass is not allowed in monocole.
Click to expand...
an RTSP stream on port 80? that seems VERY odd. RTSP is normally on 554. JPG is not supported and the string should not include user name paramaters. thats handled in the authentication. Be sure to put the correct case in user/pass fields in monocle.
 
I recently got the Echo Show 15 with the hopes and dreams to see my BI cameras. I can't get the damn thing to work. Tried pointing Monocle to my BI webserver (UI3), as well as point it directly to one of the cameras using, for example rtsp:/192.168.100.240:8686/cam/realmonitor?channel=1&subtype=0

One thing to note is I am still on Blue Iris version 4.8.6.3. Does it only work on v5 and above?

Has anyone successfully gotten this to work? Am I using the correct RTSP stream path?
 
Not to be a downer - but since gen 3 echo show's I've not been able. I went back to 5, 8 and 10" for my needs. I did a short writeup of the finding of the new OS (gen 3 and up) and Amazon changed the security and other things - I was never capable of getting it to work, even with Amazon's support (which sucked). AFAIK the only folks who've succeeded with the 15 (or the 21" fire tablets) have been folks who bought new cameras that had direct amazon support built in - ala skills like Reolink and Ring. ugh.
 
Any update on this front? I saw some dude on reddit showing off his Echo Show 15 displaying UI3, and it looked awesome. Now I think I need one of these.

Did anyone ever get it running? To be clear, I don't give a rats tail about the Amazon nature of this thing, just a big, touchscreen "Android" tablet.
 
NickTheGreat said:
Any update on this front? I saw some dude on reddit showing off his Echo Show 15 displaying UI3, and it looked awesome. Now I think I need one of these.

Did anyone ever get it running? To be clear, I don't give a rats tail about the Amazon nature of this thing, just a big, touchscreen "Android" tablet.
Click to expand...
I run UI3 on an older amazon fire tablet, just because I had one sitting around. works fine, if that's what you are looking at.
 
rdxny said:
I run UI3 on an older amazon fire tablet, just because I had one sitting around. works fine, if that's what you are looking at.
Click to expand...
I've done that too. It seemed like some in this thread were not successful with this thing though.
 
You must log in or register to reply here.
Top Bottom