Aktuelle Test Version | x.x.4 |
---|---|
Veröffentlichungsdatum | xx.12.2020? |
Github Link | https://github.com/dbweb-ch/ioBroker.rtspstream |
Moin,
ich kämpfe zur Zeit mit rtspStream und hoffe dieser Thread ist noch aktuell.
Die Installation von rtspStream erfolgte nach der Anleitung.
Beim ersten Start der Instanz vergebe ich einen Namen, belasse den Access Port, füge den getesteten rtsp Link ein und passe den Port und die Auflösung an. Nach anklicken von ADD STREAM erscheint im unteren Teil des Fensters ein Eintrag.
Starte ich nun die Instanz wird kurz alles grün, geht dann aber bei "verbunden mit Host" und "Lebenszeichen" wieder auf rot.
Gleichzeitig meldet der Host einen Restart Loop.
Starte ich nun noch mal die Konfiguration der Instanz, ist der Eintrag im unteren Teil des Fensters verschwunden und es lässt sich auch kein Eintrag mehr erstellen.
Hier die Debug Logs
rtspstream.0
2022-04-09 13:14:00.698 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
rtspstream.0
2022-04-09 13:14:00.696 info terminating
rtspstream.0
2022-04-09 13:14:00.189 error Exception-Code: ERR_SOCKET_BAD_PORT: options.port should be >= 0 and < 65536. Received .
rtspstream.0
2022-04-09 13:14:00.189 error RangeError [ERR_SOCKET_BAD_PORT]: options.port should be >= 0 and < 65536. Received . at validatePort (internal/validators.js:182:11) at Server.listen (net.js:1442:5) at rtspstream.onReady (/opt/iobroker/node_modules/iobroker.rtspstream/main.js:68:16)
rtspstream.0
2022-04-09 13:14:00.188 error unhandled promise rejection: options.port should be >= 0 and < 65536. Received .
rtspstream.0
2022-04-09 13:14:00.187 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
rtspstream.0
2022-04-09 13:14:00.183 info Stream Kamera 1 starting Server on Port
rtspstream.0
2022-04-09 13:14:00.182 info Stream Kamera 1 using TcpPort 7447
rtspstream.0
2022-04-09 13:14:00.128 info Number of streams: 1
rtspstream.0
2022-04-09 13:14:00.097 warn State "rtspstream.0.info.connection" has no existing object, this might lead to an error in future versions
rtspstream.0
2022-04-09 13:14:00.065 debug Starting rtsp Stream
rtspstream.0
2022-04-09 13:14:00.029 info starting. Version 0.0.4 in /opt/iobroker/node_modules/iobroker.rtspstream, node: v12.22.11, js-controller: 4.0.21
rtspstream.0
2022-04-09 13:13:59.881 debug States connected to redis: 127.0.0.1:9000
rtspstream.0
2022-04-09 13:13:59.866 debug States create User PubSub Client
rtspstream.0
2022-04-09 13:13:59.865 debug States create System PubSub Client
rtspstream.0
2022-04-09 13:13:59.854 debug Redis States: Use Redis connection: 127.0.0.1:9000
rtspstream.0
2022-04-09 13:13:59.831 debug Objects connected to redis: 127.0.0.1:9001
rtspstream.0
2022-04-09 13:13:59.824 debug Objects client initialize lua scripts
rtspstream.0
2022-04-09 13:13:59.790 debug Objects create User PubSub Client
rtspstream.0
2022-04-09 13:13:59.788 debug Objects create System PubSub Client
rtspstream.0
2022-04-09 13:13:59.785 debug Objects client ready ... initialize now
rtspstream.0
2022-04-09 13:13:59.744 debug Redis Objects: Use Redis connection: 127.0.0.1:9001
rtspstream.0
2022-04-09 13:13:55.163 info Got terminate signal TERMINATE_YOURSELF
rtspstream.0
2022-04-09 13:13:54.988 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
rtspstream.0
2022-04-09 13:13:54.986 info terminating
rtspstream.0
2022-04-09 13:13:54.478 error Exception-Code: ERR_SOCKET_BAD_PORT: options.port should be >= 0 and < 65536. Received .
rtspstream.0
2022-04-09 13:13:54.477 error RangeError [ERR_SOCKET_BAD_PORT]: options.port should be >= 0 and < 65536. Received . at validatePort (internal/validators.js:182:11) at Server.listen (net.js:1442:5) at rtspstream.onReady (/opt/iobroker/node_modules/iobroker.rtspstream/main.js:68:16)
rtspstream.0
2022-04-09 13:13:54.477 error unhandled promise rejection: options.port should be >= 0 and < 65536. Received .
rtspstream.0
2022-04-09 13:13:54.476 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
rtspstream.0
2022-04-09 13:13:54.472 info Stream Kamera 1 starting Server on Port
rtspstream.0
2022-04-09 13:13:54.472 info Stream Kamera 1 using TcpPort 7447
rtspstream.0
2022-04-09 13:13:54.419 info Number of streams: 1
rtspstream.0
2022-04-09 13:13:54.389 warn State "rtspstream.0.info.connection" has no existing object, this might lead to an error in future versions
rtspstream.0
2022-04-09 13:13:54.357 debug Starting rtsp Stream
rtspstream.0
2022-04-09 13:13:54.322 info starting. Version 0.0.4 in /opt/iobroker/node_modules/iobroker.rtspstream, node: v12.22.11, js-controller: 4.0.21
rtspstream.0
2022-04-09 13:13:54.150 debug States connected to redis: 127.0.0.1:9000
rtspstream.0
2022-04-09 13:13:54.135 debug States create User PubSub Client
rtspstream.0
2022-04-09 13:13:54.134 debug States create System PubSub Client
rtspstream.0
2022-04-09 13:13:54.124 debug Redis States: Use Redis connection: 127.0.0.1:9000
rtspstream.0
2022-04-09 13:13:54.100 debug Objects connected to redis: 127.0.0.1:9001
rtspstream.0
2022-04-09 13:13:54.094 debug Objects client initialize lua scripts
rtspstream.0
2022-04-09 13:13:54.058 debug Objects create User PubSub Client
rtspstream.0
2022-04-09 13:13:54.056 debug Objects create System PubSub Client
rtspstream.0
2022-04-09 13:13:54.053 debug Objects client ready ... initialize now
rtspstream.0
2022-04-09 13:13:53.994 debug Redis Objects: Use Redis connection: 127.0.0.1:9001
rtspstream.0
2022-04-09 13:13:32.650 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
rtspstream.0
2022-04-09 13:13:32.647 info terminating
rtspstream.0
2022-04-09 13:13:32.138 error Exception-Code: ERR_SOCKET_BAD_PORT: options.port should be >= 0 and < 65536. Received .
rtspstream.0
2022-04-09 13:13:32.138 error RangeError [ERR_SOCKET_BAD_PORT]: options.port should be >= 0 and < 65536. Received . at validatePort (internal/validators.js:182:11) at Server.listen (net.js:1442:5) at rtspstream.onReady (/opt/iobroker/node_modules/iobroker.rtspstream/main.js:68:16)
rtspstream.0
2022-04-09 13:13:32.137 error unhandled promise rejection: options.port should be >= 0 and < 65536. Received .
rtspstream.0
2022-04-09 13:13:32.137 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
rtspstream.0
2022-04-09 13:13:32.133 info Stream Kamera 1 starting Server on Port
rtspstream.0
2022-04-09 13:13:32.132 info Stream Kamera 1 using TcpPort 7447
rtspstream.0
2022-04-09 13:13:32.073 info Number of streams: 1
rtspstream.0
2022-04-09 13:13:32.042 warn State "rtspstream.0.info.connection" has no existing object, this might lead to an error in future versions
rtspstream.0
2022-04-09 13:13:31.984 info starting. Version 0.0.4 in /opt/iobroker/node_modules/iobroker.rtspstream, node: v12.22.11, js-controller: 4.0.21
rtspstream.0
2022-04-09 13:13:10.210 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
rtspstream.0
2022-04-09 13:13:10.207 info terminating
rtspstream.0
2022-04-09 13:13:09.698 error Exception-Code: ERR_SOCKET_BAD_PORT: options.port should be >= 0 and < 65536. Received .
rtspstream.0
2022-04-09 13:13:09.698 error RangeError [ERR_SOCKET_BAD_PORT]: options.port should be >= 0 and < 65536. Received . at validatePort (internal/validators.js:182:11) at Server.listen (net.js:1442:5) at rtspstream.onReady (/opt/iobroker/node_modules/iobroker.rtspstream/main.js:68:16)
rtspstream.0
2022-04-09 13:13:09.697 error unhandled promise rejection: options.port should be >= 0 and < 65536. Received .
rtspstream.0
2022-04-09 13:13:09.697 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
rtspstream.0
2022-04-09 13:13:09.693 info Stream Kamera 1 starting Server on Port
rtspstream.0
2022-04-09 13:13:09.692 info Stream Kamera 1 using TcpPort 7447
rtspstream.0
2022-04-09 13:13:09.639 info Number of streams: 1
rtspstream.0
2022-04-09 13:13:09.604 warn State "rtspstream.0.info.connection" has no existing object, this might lead to an error in future versions
rtspstream.0
2022-04-09 13:13:09.550 info starting. Version 0.0.4 in /opt/iobroker/node_modules/iobroker.rtspstream, node: v12.22.11, js-controller: 4.0.21
rtspstream.0
2022-04-09 13:13:05.414 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
rtspstream.0
2022-04-09 13:13:05.413 info terminating
rtspstream.0
2022-04-09 13:13:04.912 info Got terminate signal TERMINATE_YOURSELF
rtspstream.0
2022-04-09 13:13:01.351 warn State Change: rtspstream.0.Kamera 1.startStream to false ack true
rtspstream.0
2022-04-09 13:13:01.342 warn State Change: rtspstream.0.Kamera 1.ffmpegOptions to ack true
rtspstream.0
2022-04-09 13:13:01.337 info State value to set for "rtspstream.0.Kamera 1.ffmpegOptions" has to be type "text" but received type "string"
rtspstream.0
2022-04-09 13:13:01.333 warn State Change: rtspstream.0.Kamera 1.tcpPort to 7447 ack true
rtspstream.0
2022-04-09 13:13:01.325 warn This object will not be created in future versions. Please report this to the developer.
rtspstream.0
2022-04-09 13:13:01.324 warn Object rtspstream.0.Kamera 1.ffmpegOptions is invalid: obj.common.type has an invalid value (text) but has to be one of number, string, boolean, array, object, mixed, file, json
rtspstream.0
2022-04-09 13:13:01.323 info State value to set for "rtspstream.0.Kamera 1.tcpPort" has to be type "number" but received type "string"
rtspstream.0
2022-04-09 13:13:01.316 warn State Change: rtspstream.0.Kamera 1.resolution to 1024x576 ack true
rtspstream.0
2022-04-09 13:13:01.303 warn State Change: rtspstream.0.Kamera 1.port to ack true
rtspstream.0
2022-04-09 13:13:01.293 info State value to set for "rtspstream.0.Kamera 1.port" has to be type "number" but received type "string"
rtspstream.0
2022-04-09 13:13:01.249 warn State Change: rtspstream.0.Kamera 1.rtspUrl to rtsp://192.168.xxx.xxx/XEqfJ3ykaDgqc88Q ack true
Hat jemand eine Idee was ich tun könnte?
Gruß,
Andreas