Monocle gateways fails showing Sricam camera by second time



  • Currently I have two Sricam cameras, one SP015 and one SP012. I have configured Monocle Gateway on a Raspberry Pi B+ (yes, oldest) using an Echo Show 5 for watching and all work nice first time.

    The issue is when I switch between the two cameras because the streaming fails showing the camera. For example:

    I ask Alexa for showing Balcón camera, all ok. Then I ask for showing Living Room camera and Alexa shows it as well, but, if I ask for Balcón camera again, it fails showing the following message:

    Jul 27 14:59:47 raspberrypi monocle-gateway[381]: 2019-07-27T19:59:47.419Z [ERROR] Uncaught Exception Cannot read property 'match' of null
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]: [ 'Uncaught Exception',
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:   'Cannot read property \'match\' of null' ]
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]: 2019-07-27T19:59:47.427Z [ERROR] TypeError: Cannot read property 'match' of null
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]: [ TypeError: Cannot read property 'match' of null
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:     at Object.exports.parse (/snapshot/monocle-gateway/node_modules/rtsp-stream/lib/request-line.js:12:20)
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:     at new module.exports (/snapshot/monocle-gateway/node_modules/rtsp-stream/lib/incoming-message.js:26:24)
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:     at module.exports.Decoder._writeHead (/snapshot/monocle-gateway/node_modules/rtsp-stream/decoder.js:83:15)
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:     at module.exports.Decoder._writeOffset (/snapshot/monocle-gateway/node_modules/rtsp-stream/decoder.js:37:21)
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:     at module.exports.Decoder._write (/snapshot/monocle-gateway/node_modules/rtsp-stream/decoder.js:27:8)
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:     at doWrite (/snapshot/monocle-gateway/node_modules/readable-stream/lib/_stream_writable.js:428:64)
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:     at writeOrBuffer (/snapshot/monocle-gateway/node_modules/readable-stream/lib/_stream_writable.js:417:5)
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:     at module.exports.Writable.write (/snapshot/monocle-gateway/node_modules/readable-stream/lib/_stream_writable.js:334:11)
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:     at Socket.ondata (_stream_readable.js:642:20)
    Jul 27 14:59:47 raspberrypi monocle-gateway[381]:     at Socket.emit (events.js:159:13) ]
    Jul 27 14:59:57 raspberrypi monocle-gateway[381]: 2019-07-27T19:59:57.588Z [INFO]  [192.168.0.131:33668 <BJcVpQ5MH>] RTSP CLIENT SOCKET CLOSED
    Jul 27 14:59:57 raspberrypi monocle-gateway[381]: 2019-07-27T19:59:57.601Z [INFO]  [192.168.0.131:33668 <BJcVpQ5MH>] RTSP CLIENT DETACHED FROM STREAM: Balcón (STREAM:4129c43b-82a4-4257-81d8-121eee9bbe29)
    Jul 27 14:59:57 raspberrypi monocle-gateway[381]: 2019-07-27T19:59:57.603Z [INFO]  [192.168.0.131:33668 <BJcVpQ5MH>] RTSP ENDPOINT SOCKET CLOSED [192.168.0.131:33668 <BJcVpQ5MH>]
    
    Jul 27 15:00:39 raspberrypi monocle-gateway[381]: 2019-07-27T20:00:39.151Z [INFO]  [RTSP PROXY] STREAM [Sala/PRIMARY] WILL BE DE-REGISTERED IN 2 MINUTES
    
    Jul 27 15:01:39 raspberrypi monocle-gateway[381]: 2019-07-27T20:01:39.207Z [INFO]  [RTSP PROXY] STREAM [Sala/PRIMARY] WILL BE DE-REGISTERED IN 1 MINUTES
    

    Does anyone else have this issue?



  • Sounds like I am having a similar issue with a Reolink camera and an Echo Show 5 using the Monocle Gateway. I’ve posted about it but no resolution at this time.

    Are you trying to view the camera again right after the last request? My gut feeling is that a connection along the way is not being closed properly and it is being left to timeout and flush on it’s own. I say that because the camera will successfully stream if I wait 5+ minutes before asking to “show” the camera again.



  • @picharras

    I have seen a similar error before. I believe its a bug in the RTSP layer we are using in the Monocle Gateway and we are working on replacing it.

    In the meantime, can you try using either @proxy or @proxy-tcp instead of @tunnel? I think most Sricams in the past have used @proxy successfully.

    Thanks, Robert



  • @spicymikey Yes, I’m trying to see the camera immediately after the last one. I also think about an issue closing previous connection. Also have saw the rtsp-stream module has a log time without updates.



  • @Monocle @spicymikey I have set @proxy-tcp instead of @proxy previously set and the issue is gone. Thank a lot!



  • @picharras

    Additional discussion on this topic is at the bottom of this thread:
    https://forum.monoclecam.com/topic/217/monocle-gateway-throws-proxy-error-at-startup-on-win2012r2-server-solved/37

    Take a look at the @hangup tag mentioned in that thread – that might help too.

    Thanks, Robert



  • Hi,

    I’ve the same issue with my Video1one ISIS-MDR5100-3.2 Camera’s but for me is the @proxy-tcp or with the @hangup option not an solution. It doesn’t work for me.

    VLC works fine and my other 4 Camera’s (Axis F41) also working well with monocle… Is there an developer version available newer than 0.0.4 from may 2019?

    Regards
    Habib



  • @Habib

    There is not a newer version available at this time, but one is in the works, but won’t likely be available until Q1 2020.


Log in to reply