• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Unknowed brand IPcam

    Other Manufacturers
    5
    97
    7708
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Tueftler last edited by

      So there is nothing listing on Port 443

      I thing it is a permission probleme because if I start it with monocle-gateway without any options it works.

      
root@FhemServer:~# sudo lsof -i -P -n | grep LISTEN
java       397  root   18u  IPv6  15321      0t0  TCP *:8080 (LISTEN)
vncserver  440  root   11u  IPv6  13164      0t0  TCP *:5900 (LISTEN)
vncserver  440  root   12u  IPv4  13165      0t0  TCP *:5900 (LISTEN)
sshd       458  root    3u  IPv4  14437      0t0  TCP *:22 (LISTEN)sshd       458  root    4u  IPv6  12894      0t0  TCP *:22 (LISTEN)pilight-d  519  root   10u  IPv4  13152      0t0  TCP *:5000 (LISTEN)
pilight-d  519  root   14u  IPv4  12091      0t0  TCP *:5002 (LISTEN)
pilight-d  519  root   15u  IPv4  12092      0t0  TCP *:5001 (LISTEN)
perl       544  fhem    5u  IPv4  12111      0t0  TCP *:7072 (LISTEN)
perl       544  fhem    6u  IPv4  14749      0t0  TCP *:8083 (LISTEN)
perl       544  fhem    7u  IPv4  13723      0t0  TCP *:8084 (LISTEN)
perl       544  fhem    8u  IPv4  13724      0t0  TCP *:8085 (LISTEN)
perl       544  fhem   10u  IPv4  14752      0t0  TCP *:8091 (LISTEN)
perl       544  fhem   15u  IPv4  15213      0t0  TCP *:9999 (LISTEN)
perl       544  fhem   16u  IPv4  14227      0t0  TCP *:8090 (LISTEN)
perl       544  fhem   17u  IPv4  17086      0t0  TCP *:8081 (LISTEN)
perl       544  fhem   18u  IPv4  14249      0t0  TCP *:1883 (LISTEN)
perl       544  fhem   33u  IPv4  17363      0t0  TCP *:8383 (LISTEN)
smbd       708  root   33u  IPv6  15565      0t0  TCP *:445 (LISTEN)
smbd       708  root   34u  IPv6  15566      0t0  TCP *:139 (LISTEN)
smbd       708  root   35u  IPv4  15567      0t0  TCP *:445 (LISTEN)
smbd       708  root   36u  IPv4  15568      0t0  TCP *:139 (LISTEN)
node       878  fhem   18u  IPv6  18698      0t0  TCP *:8086 (LISTEN)
node\x20/ 1297  fhem   18u  IPv4  19473      0t0  TCP 127.0.0.1:34729 (LISTEN)
cupsd     5343  root    9u  IPv6 443540      0t0  TCP [::1]:631 (LISTEN)
cupsd     5343  root   10u  IPv4 443541      0t0  TCP 127.0.0.1:631 (LISTEN)
      Monocle 1 Reply Last reply Reply Quote 0
      • Monocle
        Monocle @Tueftler last edited by Monocle

        @Tueftler

        When the daemon/service is installed, this script is run to create a new “monocle” system user and grant them access to the monocle configuration directory:

        # Create Monocle service user account to run under
echo "Creating 'monocle' system user account"
useradd --system -m monocle

# Create required config directory
echo "Creating configuration directory at '/etc/monocle/'"
mkdir -p /etc/monocle/

# Set group ownership and permissions of config directory
chgrp -f -R monocle /etc/monocle
chmod -f -R g+rw /etc/monocle

        The following commands are also run after the executables are copied to the system:

                # Configure system to allow Monocle-Gateway access to port 443
        echo "Configuring bind access to system reserved port 443"
        setcap 'cap_net_bind_service=+ep' /usr/local/bin/monocle-gateway

        # Reload systemd services
        echo "Reloading systemd daemon"
        systemctl daemon-reload

        # Install Monocle Gateway as a system service
        echo "Starting Monocle Gateway service daemon"
        systemctl start monocle-gateway
        echo "Enabling Monocle Gateway service deamon to start automatically"
        systemctl enable monocle-gateway

        # Check the status of the Monocle service instance
        #sudo systemctl status monocle-gateway

        Take a look at this command:

        sudo setcap 'cap_net_bind_service=+ep' /usr/local/bin/monocle-gateway

        I wonder if that is the problem on your system. If that failed for any reason, that would explain why your daemon/service instance is not able to access port 443.
        Try running that single command (using sudo) and see what happens.

        Thanks, Robert

        Monocle: https://monoclecam.com
        Getting Started | Troubleshooting Guide | FAQ | Contact Support

        1 Reply Last reply Reply Quote 0
        • T
          Tueftler last edited by

          Ther coms nothing see

          pi@FhemServer:~ $ sudo setcap 'cap_net_bind_service=+ep' /usr/local/bin/monocle-gateway
pi@FhemServer:~ $
          Monocle 1 Reply Last reply Reply Quote 0
          • Monocle
            Monocle @Tueftler last edited by

            @Tueftler

            If you restart the monocle gateway, does it still have the port 443 error?

            I can also use this command to verify the attribute exits on the file:

            > sudo getcap /usr/local/bin/monocle-gateway

/usr/local/bin/monocle-gateway = cap_net_bind_service+ep

            Monocle: https://monoclecam.com
            Getting Started | Troubleshooting Guide | FAQ | Contact Support

            Monocle 1 Reply Last reply Reply Quote 0
            • Monocle
              Monocle @Monocle last edited by

              @Monocle

              Another thing you can try is editing this file:
              /etc/systemd/system/monocle-gateway.service

              Add the line AmbientCapabilities=CAP_NET_BIND_SERVICE under the [Service] section so that the file looks like this:

              # *********************************************************************
#              __  __  ___  _  _  ___   ___ _    ___
#             |  \/  |/ _ \| \| |/ _ \ / __| |  | __|
#             | |\/| | (_) | .` | (_) | (__| |__| _|
#             |_|  |_|\___/|_|\_|\___/ \___|____|___|
#
#  -------------------------------------------------------------------
#               MONOCLE GATEWAY SYSTEMD INIT SCRIPT
#       COPYRIGHT SHADEBLUE, LLC @ 2018, ALL RIGHTS RESERVED
#  -------------------------------------------------------------------
#
# *********************************************************************

[Unit]
Description=Monocle Gateway Service
After=network.target
ConditionPathExists=/usr/local/bin/monocle-gateway
ConditionPathExists=/usr/local/bin/monocle-proxy
ConditionFileIsExecutable=/usr/local/bin/monocle-gateway
ConditionFileIsExecutable=/usr/local/bin/monocle-proxy
ConditionPathExists=/etc/monocle/monocle.token
ConditionFileNotEmpty=/etc/monocle/monocle.token

[Service]
AmbientCapabilities=CAP_NET_BIND_SERVICE
ExecStart=/usr/local/bin/monocle-gateway
WorkingDirectory=/home/monocle/
StandardOutput=inherit
StandardError=inherit
Restart=always
RestartSec=120
StartLimitInterval=5
StartLimitBurst=10
User=monocle

[Install]
WantedBy=multi-user.target

              Next, run this command to RELAOD the service config:

              sudo systemctl daemon-reload

              Now restart the monocle gateway and check to log to see if that helped.

              Thanks, Robert

              Monocle: https://monoclecam.com
              Getting Started | Troubleshooting Guide | FAQ | Contact Support

              1 Reply Last reply Reply Quote 0
              • D
                Declan2511 last edited by

                Hi newbie here, I’ve just started using monocle on a Victure IP camera from Amazon. I had very similar problems to you (although I’ve not read all your threads). My problem was solved when I switched to a new Pi install. I think the problem was Apache running on my main Pi which I use for Domoticz. It was using port 443. I have the stream running on a show 5, Fire & Fire HD. Now all I have to solve is the buffering!

                1 Reply Last reply Reply Quote 0
                • T
                  Tueftler last edited by

                  Now after this command

                  > sudo getcap /usr/local/bin/monocle-gateway

                  It looks like good. I have made a restart from Raspberry Pi and Alexa can show me the Cam.
                  And there is no brake I test it some times and give them again feedback.

                  Monocle 1 Reply Last reply Reply Quote 0
                  • Monocle
                    Monocle @Tueftler last edited by

                    @Tueftler

                    Success?

                    Monocle: https://monoclecam.com
                    Getting Started | Troubleshooting Guide | FAQ | Contact Support

                    1 Reply Last reply Reply Quote 0
                    • T
                      Tueftler last edited by

                      Yes it works now, the stream runns with audio. And it did not stop from self. Is there also a way to use IP cams without RTSP viedeo streams? I have one more IP Cam but they did not have a RTSP it is a URL in this format http://ipaddress/videostream.cgi

                      Monocle 1 Reply Last reply Reply Quote 0
                      • Monocle
                        Monocle @Tueftler last edited by

                        @Tueftler

                        I have one more IP Cam but they did not have a RTSP it is a URL in this format http://ipaddress/videostream.cgi

                        At this time no. At least not with Monocle and Alexa. Alexa only supports RTSP (and WebRTC) streams. You would have to setup some external media server that can accept the camera stream and convert it into a H.264 RTSP stream.

                        Monocle: https://monoclecam.com
                        Getting Started | Troubleshooting Guide | FAQ | Contact Support

                        1 Reply Last reply Reply Quote 0
                        • T
                          Tueftler last edited by

                          So
                          I will say thank you for your support and the time you have spend.
                          I have ordered one more cam like this for 23€ with shipping is it very good.

                          Thanks a lot

                          Monocle 1 Reply Last reply Reply Quote 0
                          • Monocle
                            Monocle @Tueftler last edited by

                            @Tueftler

                            You are welcome. Enjoy!

                            Monocle: https://monoclecam.com
                            Getting Started | Troubleshooting Guide | FAQ | Contact Support

                            1 Reply Last reply Reply Quote 0
                            • petec
                              petec last edited by petec

                              Here have the same camera board as the first post and using an Alexa Show 5. (new).

                              I am hoping to update my very old Optex security cameras with these camera boards.

                              I can see two channels using VLC and the command:

                              1 - rtsp://192.168.244.151/user=admin_password=xxx_channel=0_stream=1.sdp
                              Which provides me with a 352X240 video resolution.

                              2 - rtsp://192.168.244.151/user=admin_password=xxx_channel=0_stream=0.sdp
                              which provides me with a 1920X1080 resolution.

                              I am using a PFSense firewall here. I have disabled sound on the camera.

                              I also have a Ring Doorbell which works fine with the Amazon Alexa Show. Looked to change over to the HikVision OEM doorbell in the next few weeks.

                              camerafeeds.jpg

                              Also installed the Monocle Gateway here, made above modifications and have tried all of the tags.

                              See this:
                              monocle-g 27697 monocle 12u IPv4 109131 0t0 TCP *:8555 (LISTEN)
                              monocle-g 27697 monocle 14u IPv4 109132 0t0 TCP *:443 (LISTEN)
                              monocle-p 27725 monocle 3u IPv4 109748 0t0 TCP *:8554 (LISTEN)

                              OK so adjusted my PFSense DNS Resolver adding custom options.

                              server:
                              private-domain: “xxx.mproxy.io”

                              Tested it by pinging xxx.mproxy.io and get a response.

                              Now when I ask Alexa to show test cam it appears to try for about a minute then quits. Beforehand it would quit right away…so I am getting close.

                              Got it working fine now changing @tunnel to @proxy.

                              Great stuff.

                              Auto mator

                              Monocle 1 Reply Last reply Reply Quote 0
                              • Monocle
                                Monocle @petec last edited by

                                @petec

                                Glad you found a way to get it working for your cameras!

                                Monocle: https://monoclecam.com
                                Getting Started | Troubleshooting Guide | FAQ | Contact Support

                                petec 1 Reply Last reply Reply Quote 0
                                • petec
                                  petec @Monocle last edited by

                                  @Monocle
                                  Great application.

                                  Today purchased my Echo Show #2.
                                  This is actually an IP HD camera board. Way long time ago had gone to using Grandstream cameras and boards for modded cameras. These boards came with an SDK for development. Looking to retrofit my Optex combo camera/PIRs with these camera boards.

                                  Auto mator

                                  Monocle 1 Reply Last reply Reply Quote 0
                                  • Monocle
                                    Monocle @petec last edited by

                                    @petec

                                    Sounds like an interesting project … I’ve modded lots of hardware in the past, but never an IP cam :-)

                                    Monocle: https://monoclecam.com
                                    Getting Started | Troubleshooting Guide | FAQ | Contact Support

                                    1 Reply Last reply Reply Quote 0
                                    • T
                                      Tueftler last edited by

                                      Hallo i have trubbel.
                                      My cam was working with the monocle gateway for long time but now, I thing since one week Alexa tells my “the Camera is not responding” the gateway service is running and the cam is working with other tools and with VLC Player.

                                      Was there any Changes or anything else?

                                      Monocle 1 Reply Last reply Reply Quote 0
                                      • Monocle
                                        Monocle @Tueftler last edited by

                                        @Tueftler

                                        No, no changes on our side. Feel free to post your log info from Monocle Gateway while you are requesting the camera feed that is no longer working.

                                        Its possible that Amazon has updated the system firmware and broken something. That happened with the Wansview cameras with the release of Echo Show 5.

                                        Monocle: https://monoclecam.com
                                        Getting Started | Troubleshooting Guide | FAQ | Contact Support

                                        1 Reply Last reply Reply Quote 0
                                        • T
                                          Tueftler last edited by

                                          Sorry I can’t remember, how can I find the logfile from monocle?
                                          Or is it only the Output on the Terminal?

                                          Linux FhemServer 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Dec 10 22:04:28 2019 from 192.168.2.73
root@FhemServer:~# monocle-gateway --tail

 ******************************************************************
 *             __  __  ___  _  _  ___   ___ _    ___              *
 *            |  \/  |/ _ \| \| |/ _ \ / __| |  | __|             *
 *            | |\/| | (_) | .` | (_) | (__| |__| _|              *
 *            |_|  |_|\___/|_|\_|\___/ \___|____|___|             *
 *                                                                *
 ******************************************************************

<<TAIL>> LOG FOR THE [MONOCLE-GATEWAY] SERVICE
-- Logs begin at Thu 2016-11-03 18:16:43 CET. --
Dez 10 22:04:52 FhemServer monocle-gateway[385]:     errno: 'EADDRNOTAVAIL',

Dez 10 22:04:52 FhemServer monocle-gateway[385]:     code: 'EADDRNOTAVAIL',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:     syscall: 'listen',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:     address: '192.168.2.172',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:     port: 8555 } ]
Dez 10 22:04:52 FhemServer monocle-gateway[385]: 2019-12-10T21:04:52.745Z [ERROR] [RTSP Server Error] listen EADDRNOTAVAIL 192.168.2.172:8555
Dez 10 22:04:52 FhemServer monocle-gateway[385]: [ '[RTSP Server Error]',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:   'listen EADDRNOTAVAIL 192.168.2.172:8555' ]
Dez 10 22:04:52 FhemServer monocle-gateway[385]: 2019-12-10T21:04:52.747Z [ERROR] [PROXY SERVER ERROR] Error: listen EADDRNOTAVAIL 192.168.2.172:443
Dez 10 22:04:52 FhemServer monocle-gateway[385]: [ '[PROXY SERVER ERROR]',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:   { Error: listen EADDRNOTAVAIL 192.168.2.172:443
Dez 10 22:04:52 FhemServer monocle-gateway[385]:       at Server.setupListenHandle [as _listen2] (net.js:1310:19)
Dez 10 22:04:52 FhemServer monocle-gateway[385]:       at listenInCluster (net.js:1375:12)
Dez 10 22:04:52 FhemServer monocle-gateway[385]:       at doListen (net.js:1501:7)
Dez 10 22:04:52 FhemServer monocle-gateway[385]:       at process._tickCallback (internal/process/next_tick.js:63:19)
Dez 10 22:04:52 FhemServer monocle-gateway[385]:       at Function.Module.runMain (pkg/prelude/bootstrap.js:1315:13)
Dez 10 22:04:52 FhemServer monocle-gateway[385]:       at startup (internal/bootstrap/node.js:274:19)
Dez 10 22:04:52 FhemServer monocle-gateway[385]:       at bootstrapNodeJSCore (internal/bootstrap/node.js:608:3)
Dez 10 22:04:52 FhemServer monocle-gateway[385]:     errno: 'EADDRNOTAVAIL',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:     code: 'EADDRNOTAVAIL',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:     syscall: 'listen',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:     address: '192.168.2.172',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:     port: 443 } ]
Dez 10 22:04:52 FhemServer monocle-gateway[385]: 2019-12-10T21:04:52.751Z [ERROR] [RTSP Server Error] listen EADDRNOTAVAIL 192.168.2.172:443
Dez 10 22:04:52 FhemServer monocle-gateway[385]: [ '[RTSP Server Error]',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:   'listen EADDRNOTAVAIL 192.168.2.172:443' ]
Dez 10 22:04:52 FhemServer monocle-gateway[385]: 2019-12-10T21:04:52.778Z [ERROR] [Monocle Error] getaddrinfo ENOTFOUND api.monoclecam.com api.monoclecam.com:443
Dez 10 22:04:52 FhemServer monocle-gateway[385]: [ '[Monocle Error]',
Dez 10 22:04:52 FhemServer monocle-gateway[385]:   'getaddrinfo ENOTFOUND api.monoclecam.com api.monoclecam.com:443' ]
Dez 10 22:04:52 FhemServer monocle-gateway[385]: [Monocle Disconnected]
Dez 10 22:04:52 FhemServer monocle-gateway[385]: [Monocle Reconnecting] ... in 5 seconds (attempt #1)
Dez 10 22:04:57 FhemServer monocle-gateway[385]: [Monocle Connecting]
Dez 10 22:04:58 FhemServer monocle-gateway[385]: [Monocle Connected]
Dez 10 22:04:58 FhemServer monocle-gateway[385]: [RTSP Server Registered]
Dez 10 22:04:58 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 10 22:04:58 FhemServer monocle-gateway[385]: MONOCLE RTSP SERVICE - INITIALIZED
Dez 10 22:04:58 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 10 22:04:58 FhemServer monocle-gateway[385]: FQDN = 9dd28fe1-40f2-4459-805d-daa62fdc6ff5.mproxy.io
Dez 10 22:04:58 FhemServer monocle-gateway[385]: HOST = 192.168.2.172
Dez 10 22:04:58 FhemServer monocle-gateway[385]: PORT = 443
Dez 10 22:04:58 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 15:36:41 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 15:36:41 FhemServer monocle-gateway[385]: INITIALIZE RTSP STREAM:  Garten
Dez 11 15:36:41 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 15:36:41 FhemServer monocle-gateway[385]:  - NAME  : Garten
Dez 11 15:36:41 FhemServer monocle-gateway[385]:  - LABEL : PRIMARY
Dez 11 15:36:41 FhemServer monocle-gateway[385]:  - URL   : rtsp://192.168.2.102:554/user=admin&password=xxxxxxxx&channel=1&stream=1.sdp
Dez 11 15:36:41 FhemServer monocle-gateway[385]:  - UUID  : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63
Dez 11 15:36:41 FhemServer monocle-gateway[385]:  - SESS  : 5382760b-ec6f-4f0e-8779-18d0a6e0574e
Dez 11 15:36:42 FhemServer monocle-gateway[385]:  - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00)
Dez 11 15:36:42 FhemServer monocle-gateway[385]:  - TAGS  : @hangup,@proxy-tcp
Dez 11 15:36:42 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 15:36:42 FhemServer monocle-gateway[385]: 2019-12-11T14:36:42.102Z [INFO]  [RTSP PROXY] REGISTERING STREAM [Garten/PRIMARY]; (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63)
Dez 11 15:36:42 FhemServer monocle-gateway[385]: 2019-12-11T14:36:42.254Z [DEBUG] <RTSP-PROXY> [REQUEST]  --> [REGISTER] rtsp://192.168.2.102:554/user=admin&password=xxxxxxxxx&channel=1&stream=1.sdp
Dez 11 15:36:42 FhemServer monocle-gateway[385]: 2019-12-11T14:36:42.255Z [TRACE] <RTSP-PROXY> [REQUEST]  --> [HEADERS] {
Dez 11 15:36:42 FhemServer monocle-gateway[385]:   "cseq": "1",
Dez 11 15:36:42 FhemServer monocle-gateway[385]:   "transport": "reuse_connection=0;preferred_delivery_protocol=interleaved;proxy_url_suffix=STREAM:df443cff-97a9-45ac-a21d-9768d4674f63"
Dez 11 15:36:42 FhemServer monocle-gateway[385]: }
Dez 11 15:36:42 FhemServer monocle-gateway[385]: 2019-12-11T14:36:42.269Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
Dez 11 15:36:42 FhemServer monocle-gateway[385]: 2019-12-11T14:36:42.270Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] {
Dez 11 15:36:42 FhemServer monocle-gateway[385]:   "cseq": "1",
Dez 11 15:36:42 FhemServer monocle-gateway[385]:   "date": "Wed, Dec 11 2019 14:36:42 GMT"
Dez 11 15:36:42 FhemServer monocle-gateway[385]: }
Dez 11 15:36:44 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 15:36:44 FhemServer monocle-gateway[385]: INITIALIZE RTSP STREAM:  Garten
Dez 11 15:36:44 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 15:36:44 FhemServer monocle-gateway[385]:  - NAME  : Garten
Dez 11 15:36:44 FhemServer monocle-gateway[385]:  - LABEL : PRIMARY
Dez 11 15:36:44 FhemServer monocle-gateway[385]:  - URL   : rtsp://192.168.2.102:554/user=admin&password=xxxxxxxx&channel=1&stream=1.sdp
Dez 11 15:36:44 FhemServer monocle-gateway[385]:  - UUID  : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63
Dez 11 15:36:44 FhemServer monocle-gateway[385]:  - SESS  : d5195bce-21c1-46ec-a7f8-e23127f94e88
Dez 11 15:36:44 FhemServer monocle-gateway[385]:  - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00)
Dez 11 15:36:44 FhemServer monocle-gateway[385]:  - TAGS  : @hangup,@proxy-tcp
Dez 11 15:36:44 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 15:36:45 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 15:36:45 FhemServer monocle-gateway[385]: INITIALIZE RTSP STREAM:  Garten
Dez 11 15:36:45 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 15:36:45 FhemServer monocle-gateway[385]:  - NAME  : Garten
Dez 11 15:36:45 FhemServer monocle-gateway[385]:  - LABEL : PRIMARY
Dez 11 15:36:45 FhemServer monocle-gateway[385]:  - URL   : rtsp://192.168.2.102:554/user=admin&password=xxxxxxxx&channel=1&stream=1.sdp
Dez 11 15:36:45 FhemServer monocle-gateway[385]:  - UUID  : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63
Dez 11 15:36:45 FhemServer monocle-gateway[385]:  - SESS  : ac6ef6ae-64eb-47ef-807a-9a4f6fbd45bb
Dez 11 15:36:45 FhemServer monocle-gateway[385]:  - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00)
Dez 11 15:36:45 FhemServer monocle-gateway[385]:  - TAGS  : @hangup,@proxy-tcp

Dez 11 15:36:45 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 15:37:39 FhemServer monocle-gateway[385]: 2019-12-11T14:37:39.478Z [INFO]  [RTSP PROXY] STREAM [Garten/PRIMARY] WILL BE DE-REGISTERED IN 4 MINUTES
Dez 11 15:38:39 FhemServer monocle-gateway[385]: 2019-12-11T14:38:39.538Z [INFO]  [RTSP PROXY] STREAM [Garten/PRIMARY] WILL BE DE-REGISTERED IN 3 MINUTES
Dez 11 15:39:39 FhemServer monocle-gateway[385]: 2019-12-11T14:39:39.598Z [INFO]  [RTSP PROXY] STREAM [Garten/PRIMARY] WILL BE DE-REGISTERED IN 2 MINUTES
Dez 11 15:40:39 FhemServer monocle-gateway[385]: 2019-12-11T14:40:39.655Z [INFO]  [RTSP PROXY] STREAM [Garten/PRIMARY] WILL BE DE-REGISTERED IN 1 MINUTES
Dez 11 15:41:39 FhemServer monocle-gateway[385]: 2019-12-11T14:41:39.688Z [INFO]  [RTSP PROXY] DE-REGISTERING STREAM [Garten/PRIMARY]; NO LONGER IN USE
Dez 11 15:41:39 FhemServer monocle-gateway[385]: 2019-12-11T14:41:39.706Z [DEBUG] <RTSP-PROXY> [REQUEST]  --> [DEREGISTER] rtsp://192.168.2.102:554/user=admin&password=xxxxxxxxxx&channel=1&stream=1.sdp
Dez 11 15:41:39 FhemServer monocle-gateway[385]: 2019-12-11T14:41:39.706Z [TRACE] <RTSP-PROXY> [REQUEST]  --> [HEADERS] {
Dez 11 15:41:39 FhemServer monocle-gateway[385]:   "cseq": "1",
Dez 11 15:41:39 FhemServer monocle-gateway[385]:   "transport": "reuse_connection=0;preferred_delivery_protocol=interleaved;proxy_url_suffix=STREAM:df443cff-97a9-45ac-a21d-9768d4674f63"
Dez 11 15:41:39 FhemServer monocle-gateway[385]: }
Dez 11 15:41:39 FhemServer monocle-gateway[385]: 2019-12-11T14:41:39.710Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
Dez 11 15:41:39 FhemServer monocle-gateway[385]: 2019-12-11T14:41:39.711Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] {
Dez 11 15:41:39 FhemServer monocle-gateway[385]:   "cseq": "1",
Dez 11 15:41:39 FhemServer monocle-gateway[385]:   "date": "Wed, Dec 11 2019 14:41:39 GMT"
Dez 11 15:41:39 FhemServer monocle-gateway[385]: }

Dez 11 16:11:58 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 16:11:59 FhemServer monocle-gateway[385]: INITIALIZE RTSP STREAM:  Garten
Dez 11 16:11:59 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 16:11:59 FhemServer monocle-gateway[385]:  - NAME  : Garten
Dez 11 16:11:59 FhemServer monocle-gateway[385]:  - LABEL : PRIMARY
Dez 11 16:11:59 FhemServer monocle-gateway[385]:  - URL   : rtsp://192.168.2.102:554/user=admin&password=xxxxxxxxxxx&channel=1&stream=1.sdp
Dez 11 16:11:59 FhemServer monocle-gateway[385]:  - UUID  : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63
Dez 11 16:11:59 FhemServer monocle-gateway[385]:  - SESS  : 04e0c2e8-ab3e-43ef-8277-11405679ad8a
Dez 11 16:11:59 FhemServer monocle-gateway[385]:  - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00)
Dez 11 16:11:59 FhemServer monocle-gateway[385]:  - TAGS  : @hangup,@proxy-tcp
Dez 11 16:11:59 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 16:11:59 FhemServer monocle-gateway[385]: 2019-12-11T15:11:59.000Z [INFO]  [RTSP PROXY] REGISTERING STREAM [Garten/PRIMARY]; (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63)
Dez 11 16:11:59 FhemServer monocle-gateway[385]: 2019-12-11T15:11:59.008Z [DEBUG] <RTSP-PROXY> [REQUEST]  --> [REGISTER] rtsp://192.168.2.102:554/user=admin&password=xxxxxxxxx&channel=1&stream=1.sdp
Dez 11 16:11:59 FhemServer monocle-gateway[385]: 2019-12-11T15:11:59.009Z [TRACE] <RTSP-PROXY> [REQUEST]  --> [HEADERS] {
Dez 11 16:11:59 FhemServer monocle-gateway[385]:   "cseq": "1",
Dez 11 16:11:59 FhemServer monocle-gateway[385]:   "transport": "reuse_connection=0;preferred_delivery_protocol=interleaved;proxy_url_suffix=STREAM:df443cff-97a9-45ac-a21d-9768d4674f63"
Dez 11 16:11:59 FhemServer monocle-gateway[385]: }
Dez 11 16:11:59 FhemServer monocle-gateway[385]: 2019-12-11T15:11:59.011Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
Dez 11 16:11:59 FhemServer monocle-gateway[385]: 2019-12-11T15:11:59.012Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] {
Dez 11 16:11:59 FhemServer monocle-gateway[385]:   "cseq": "1",
Dez 11 16:11:59 FhemServer monocle-gateway[385]:   "date": "Wed, Dec 11 2019 15:11:59 GMT"
Dez 11 16:11:59 FhemServer monocle-gateway[385]: }

Dez 11 16:12:01 FhemServer monocle-gateway[385]: -------------------------------------------------

Dez 11 16:12:01 FhemServer monocle-gateway[385]: INITIALIZE RTSP STREAM:  Garten
Dez 11 16:12:01 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 16:12:01 FhemServer monocle-gateway[385]:  - NAME  : Garten
Dez 11 16:12:01 FhemServer monocle-gateway[385]:  - LABEL : PRIMARY
Dez 11 16:12:01 FhemServer monocle-gateway[385]:  - URL   : rtsp://192.168.2.102:554/user=admin&password=xxxxxxxx&channel=1&stream=1.sdp
Dez 11 16:12:01 FhemServer monocle-gateway[385]:  - UUID  : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63
Dez 11 16:12:01 FhemServer monocle-gateway[385]:  - SESS  : 15d68dba-1a85-4503-9490-ac59b32dbc25
Dez 11 16:12:01 FhemServer monocle-gateway[385]:  - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00)
Dez 11 16:12:01 FhemServer monocle-gateway[385]:  - TAGS  : @hangup,@proxy-tcp
Dez 11 16:12:01 FhemServer monocle-gateway[385]: -------------------------------------------------

Dez 11 16:12:02 FhemServer monocle-gateway[385]: -------------------------------------------------

Dez 11 16:12:02 FhemServer monocle-gateway[385]: INITIALIZE RTSP STREAM:  Garten

Dez 11 16:12:02 FhemServer monocle-gateway[385]: -------------------------------------------------
Dez 11 16:12:02 FhemServer monocle-gateway[385]:  - NAME  : Garten
Dez 11 16:12:02 FhemServer monocle-gateway[385]:  - LABEL : PRIMARY
Dez 11 16:12:02 FhemServer monocle-gateway[385]:  - URL   : rtsp://192.168.2.102:554/user=admin&password=xxxxxx&channel=1&stream=1.sdp

Dez 11 16:12:02 FhemServer monocle-gateway[385]:  - UUID  : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63
Dez 11 16:12:02 FhemServer monocle-gateway[385]:  - SESS  : 17def47a-e79a-41e9-b537-a608f5b29b3e
Dez 11 16:12:02 FhemServer monocle-gateway[385]:  - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00)
Dez 11 16:12:02 FhemServer monocle-gateway[385]:  - TAGS  : @hangup,@proxy-tcp

Dez 11 16:12:02 FhemServer monocle-gateway[385]: -------------------------------------------------

^C
root@FhemServer:~#
                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            Tueftler last edited by

                                            Okay, IAM a little bit forward,
                                            There is no change if I restart the Raspberry where is running the Monocle-gateway, Alexa can still not connect to the Camera but if I Restart the service with

                                            monocle-gateway --restart

                                            After this I can connect the camera with Alexa.

                                            But why I must restart the service after rebooting the Raspberry?

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Privacy Policy  |  Terms & Conditions

                                            © 2018 shadeBlue, LLC.