goruck / alexa-ip-cam Goto Github PK

View Code? Open in Web Editor NEW

160.0 24.0 27.0 371 KB

Use Alexa's Smart Home Skill API with standalone IP cameras without needing cloud service.

License: MIT License

JavaScript 97.35% Shell 2.65%

alexa-skill smarthome camera ip-camera alexa-smart amazon-alexa axis

alexa-ip-cam's People

Contributors

Stargazers

Watchers

alexa-ip-cam's Issues

Alexsa Account Linking

How do you handle the account linking required by Amazon's Camera Skill? It looks like it needs an OAUTH 2.0 endpoint. Thoughts?

MongoDB

In your file config.json.

there is a lot field where is : REPLACE

for lot of i have the value, but i see mongodb ?
in your tutorial there never mentionned a mongoDB server.

can you indicate me if i miss a step

Issue with LetsEncrypt expiration

I am using Echo Show 10 (3rd Gen). Sometimes back, out of the blue, Alexa couldn't connect to my RTSP feed. I wonder if this is related to the issue that you described on the home page. Am hoping I can create an issue here, just so to keep track of when issue is resolved. Thank you for the good work! =)

ALL CAMERAS ARE NOT RESPONDING!

Hello,
i used your Code as a skill for a few weeks (3 cams).
Since March, 22 Amazon has changed something.
now if I call "show door" Alexa says "Camera is not responding". In German "Die Kamera reagiert gerade nicht"
On 2 Forums i could find the same Problems from Users have other Skills eg "Monocle".
Cams that are compatible with Alexa, don't have the Problem...
Read this
https://forums.developer.amazon.com/questions/140767/help-all-cameras-are-not-responding-was-working-fi.html

Alexa skill not discovering new devices

I've set everything up following your instructions and got the Skill installed for Alexa but when I try to discover new devices it doesn't find anything.

I have a pi setup running the live555 proxy and stunnel which all talk to my actual IP camera which I've also created the SSL cert for etc and my Skill and Lambda function all appear to be correct.
What troubleshooting can I do for the Alexa part? I'm very new to this side of things unfortunately so I don't know where I could have gone wrong.
Happy to provide logs/config outputs etc for additional help.

Thanks

Why did you need a rtsp proxy?

I'm very intrigued by this project. I use zoneminder for my NVR and was look to to solve the same problem as you (Show my LAN Cameras on my Echo Show).

However I'm a bit confused on why you need live555 at all.

Can't you just add your individual rtsp streams to the camera.json?

video plays for about a second or two, then buffers indefinitely

Sorry to inundate with tickets, but thought maybe you've seen this one. Per my other ticket, I have gotten the full setup working, at least as far as all the functional pieces are concerned. I can get video to display on my Fire, but only for a second or two before it starts buffering indefinitely.

Here are the stunnel logs for what happens when I stop the video.

What I can't quite figure out how to read is the 'Connection closed' line. Is it saying that stunnel received ~21MB from the camera, but only sent less than 1K to the tablet?

2018.12.01 09:52:19 LOG6[2]: TLSv1.2 ciphersuite: ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption)
2018.12.01 09:52:19 LOG7[2]: Compression: null, expansion: null
2018.12.01 09:52:19 LOG6[2]: s_connect: connecting 127.0.0.1:554
2018.12.01 09:52:19 LOG7[2]: s_connect: s_poll_wait 127.0.0.1:554: waiting 10 seconds
2018.12.01 09:52:19 LOG5[2]: s_connect: connected 127.0.0.1:554
2018.12.01 09:52:19 LOG6[2]: persistence: 127.0.0.1:554 cached
2018.12.01 09:52:19 LOG5[2]: Service [rtsp] connected remote server from 127.0.0.1:54790
2018.12.01 09:52:19 LOG7[2]: Setting remote socket options (FD=11)
2018.12.01 09:52:19 LOG7[2]: Option TCP_NODELAY set on remote socket
2018.12.01 09:52:19 LOG7[2]: Remote descriptor (FD=11) initialized
2018.12.01 09:54:21 LOG6[2]: TLS socket closed (SSL_read)
2018.12.01 09:54:21 LOG7[2]: Sent socket write shutdown
2018.12.01 09:54:21 LOG5[2]: Connection closed: 21099067 byte(s) sent to TLS, 984 byte(s) sent to socket
2018.12.01 09:54:21 LOG7[2]: Remote descriptor (FD=11) closed
2018.12.01 09:54:21 LOG7[2]: Local descriptor (FD=3) closed
2018.12.01 09:54:21 LOG7[2]: Service [rtsp] finished (0 left)

Noob Account linking problems

I'll start by apologising - sorry i'm a complete noob when it comes to anysort of programming!
I've managed to create the Amazon skill but i'm hitting problems when I try to setup the account linking, i've got the following entered;
Authorisation URL: https://www.amazon.com/ap/oa
Ticket access URL: https://api.amazon.com/auth/o2/token
Client ID: my client ID created in the Login with Amazon portal
Client Secret: the secret created in the Login with Amazon portal
Client Authentication Scheme: HTTP Basic
No Scope defined
No domains defined
No default token expiration defined

When I try to Save it I get "Account linking information is not valid."

Any pointers on where I can look to try and sort this out?
Any help much appreciated
Dave

domain and TLS certs problem

Hi,
I noticed 2 prerequisites.
It means that each camera needs to have its own separate domain name and certificate?
or,
One domain name is enough and use subdomain identify different cameras?
Live555's proxy address format is rtsp://domain:443:/proxyStream-1 , .../proxyStream-2
I see that "officecamerapi.dev-cloud.co.uk:443/h264, rtsp://hallcamerapi.dev-cloud.co.uk:443/h264"
Are u have 2 live555 process to proxy 2 camera rtsp feed?

stunnel appears to be closing the connection after a couple seconds

When I try and view the camera feed on my Fire HD 8, it times out after ~10-15 seconds, give or take. I'm pretty sure I've configured everything properly. Stunnel certs are in the right place.

Looking at the stunnel logs, I can see the Fire making the connection, but then it seems to close it pretty quickly after that. Here is the start of the logs, including the initial connection:

2018.11.20 21:25:23 LOG7[ui]: Clients allowed=500
2018.11.20 21:25:23 LOG5[ui]: stunnel 5.30 on x86_64-pc-linux-gnu platform
2018.11.20 21:25:23 LOG5[ui]: Compiled/running with OpenSSL 1.0.2g  1 Mar 2016
2018.11.20 21:25:23 LOG7[cron]: Cron thread initialized
2018.11.20 21:25:23 LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP
2018.11.20 21:25:23 LOG7[ui]: errno: (*__errno_location ())
2018.11.20 21:25:23 LOG5[ui]: Reading configuration from file /etc/stunnel/stunnel.conf
2018.11.20 21:25:23 LOG5[ui]: UTF-8 byte order mark not detected
2018.11.20 21:25:23 LOG5[ui]: FIPS mode disabled
2018.11.20 21:25:23 LOG7[ui]: Compression disabled
2018.11.20 21:25:23 LOG7[ui]: PRNG seeded successfully
2018.11.20 21:25:23 LOG6[ui]: Initializing service [rtsp]
2018.11.20 21:25:23 LOG6[ui]: Loading certificate from file: /etc/stunnel/fullchain.pem
2018.11.20 21:25:23 LOG6[ui]: Certificate loaded from file: /etc/stunnel/fullchain.pem
2018.11.20 21:25:23 LOG6[ui]: Loading private key from file: /etc/stunnel/privkey.pem
2018.11.20 21:25:23 LOG6[ui]: Private key loaded from file: /etc/stunnel/privkey.pem
2018.11.20 21:25:23 LOG7[ui]: Private key check succeeded
2018.11.20 21:25:23 LOG7[ui]: DH initialization
2018.11.20 21:25:23 LOG7[ui]: Could not load DH parameters from /etc/stunnel/fullchain.pem
2018.11.20 21:25:23 LOG6[ui]: Using dynamic DH parameters
2018.11.20 21:25:23 LOG7[ui]: ECDH initialization
2018.11.20 21:25:23 LOG7[ui]: ECDH initialized with curve prime256v1
2018.11.20 21:25:23 LOG7[ui]: SSL options: 0x03004004 (+0x03004000, -0x00000000)
2018.11.20 21:25:23 LOG5[ui]: Configuration successful
2018.11.20 21:25:23 LOG7[ui]: Listening file descriptor created (FD=7)
2018.11.20 21:25:23 LOG7[ui]: Service [rtsp] (FD=7) bound to 0.0.0.0:443
2018.11.20 21:25:23 LOG7[ui]: Created pid file /var/run/stunnel4.pid
2018.11.20 21:26:23 LOG6[cron]: Executing cron jobs
2018.11.20 21:26:23 LOG5[cron]: Updating DH parameters
2018.11.20 21:26:49 LOG5[cron]: DH parameters updated
2018.11.20 21:26:49 LOG6[cron]: Cron jobs completed in 26 seconds
2018.11.20 21:26:49 LOG7[cron]: Waiting 86374 seconds
2018.11.20 21:29:00 LOG7[ui]: Found 1 ready file descriptor(s)
2018.11.20 21:29:00 LOG7[ui]: FD=4 events=0x2001 revents=0x0
2018.11.20 21:29:00 LOG7[ui]: FD=7 events=0x2001 revents=0x1
2018.11.20 21:29:00 LOG7[ui]: Service [rtsp] accepted (FD=3) from 192.168.1.66:54508
2018.11.20 21:29:00 LOG7[0]: Service [rtsp] started
2018.11.20 21:29:00 LOG5[0]: Service [rtsp] accepted connection from 192.168.1.66:54508
2018.11.20 21:29:00 LOG7[0]: SSL state (accept): before/accept initialization
2018.11.20 21:29:00 LOG7[0]: SNI: no virtual services defined
2018.11.20 21:29:00 LOG7[0]: New session callback
2018.11.20 21:29:00 LOG7[0]:      1 server accept(s) requested
2018.11.20 21:29:00 LOG7[0]:      1 server accept(s) succeeded
2018.11.20 21:29:00 LOG7[0]:      0 server renegotiation(s) requested
2018.11.20 21:29:00 LOG7[0]:      0 session reuse(s)
2018.11.20 21:29:00 LOG7[0]:      0 internal session cache item(s)
2018.11.20 21:29:00 LOG7[0]:      0 internal session cache fill-up(s)
2018.11.20 21:29:00 LOG7[0]:      0 internal session cache miss(es)
2018.11.20 21:29:00 LOG7[0]:      0 external session cache hit(s)
2018.11.20 21:29:00 LOG7[0]:      0 expired session(s) retrieved
2018.11.20 21:29:00 LOG6[0]: SSL accepted: new session negotiated
2018.11.20 21:29:00 LOG6[0]: No peer certificate received
2018.11.20 21:29:00 LOG6[0]: Negotiated TLSv1.2 ciphersuite ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption)
2018.11.20 21:29:00 LOG7[0]: Compression: null, expansion: null
2018.11.20 21:29:00 LOG6[0]: s_connect: connecting 192.168.1.13:554
2018.11.20 21:29:00 LOG7[0]: s_connect: s_poll_wait 192.168.1.13:554: waiting 10 seconds
2018.11.20 21:29:00 LOG5[0]: s_connect: connected 192.168.1.13:554
2018.11.20 21:29:00 LOG6[0]: persistence: 192.168.1.13:554 cached
2018.11.20 21:29:00 LOG5[0]: Service [rtsp] connected remote server from 192.168.1.8:51646
2018.11.20 21:29:00 LOG7[0]: Remote descriptor (FD=9) initialized
2018.11.20 21:29:00 LOG6[0]: SSL socket closed (SSL_read)
2018.11.20 21:29:00 LOG7[0]: Sent socket write shutdown
2018.11.20 21:29:00 LOG5[0]: Connection closed: 139 byte(s) sent to SSL, 163 byte(s) sent to socket
2018.11.20 21:29:00 LOG7[0]: Remote descriptor (FD=9) closed
2018.11.20 21:29:00 LOG7[0]: Local descriptor (FD=3) closed
2018.11.20 21:29:00 LOG7[0]: Service [rtsp] finished (0 left)

I can connect to port 554 via VLC (with authentication) just fine. I'm not using live555ProxyServer to start with for simplicity.

Any thoughts here?

Can this work using ip reservation and port forwarding intead of static ip?

I have spectrum internet and residential customers cannot get static ip's. Their only option available is to use ip reservation and port forwarding. Can this skill work in that environment? If so, could you provide assistance in setting it up or suggest a few links that might provide some assistance?

Problem with stunnel

Hi there,

good guide so far but i'm stuck with stunnel
Log tells me service started and connection is accepted but is then reseted because of error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol - tested with VLC

If connection is made directly to live555proxy stream works

Live555 blog link dead

The readme.md has:

Setup the RTSP Proxy

emtunc's blog provides excellent instructions on how to setup the proxy from Live555.

But while not technically a dead link, it looks like the content of how to configure Live555 is gone. Know of any other good references besides the Live555 source/web page?

have you converted Zoneminder mjpeg to RTSP for this project?

I too am a Zoneminder user but with numerous analog cameras hooked through a capture card and other older cameras which do not support direct RTSP. Might you have done any investigation of converting the Zoneminder mjpeg stream into RTSP with ffmpeg/ffserver/avconv or anything else? I've found a few general posts on mjpeg to rtsp conversion, but nothing specific to Zoneminder. Thanks in advance.

goruck / alexa-ip-cam Goto Github PK

alexa-ip-cam's People

Contributors

Stargazers

Watchers

Forkers

alexa-ip-cam's Issues

Recommend Projects

Recommend Topics

Recommend Org