Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: SoloCam S40 (T8124P) connection issues #380

Open
marcprenger opened this issue Sep 22, 2023 · 4 comments
Open

[Bug]: SoloCam S40 (T8124P) connection issues #380

marcprenger opened this issue Sep 22, 2023 · 4 comments
Labels
bug Something isn't working fixed
Milestone

Comments

@marcprenger
Copy link

Adapter version

1.1.2

JS-Controller version

5.0.12

Node version

18.17.1

Operating System type

Linux

Operating system version

Debian

Describe the bug

After some while the connection to my battery powered S40 cannot be re-established. When I restart the adapter it works, but only until connection is terminated again (to save battery).

Let me know if you need more logs or if I need to share the camera.

To reproduce

Restart adapter and wait until connection to battery powered S40 goes down. Then try to set some station / camera parameter and view the logs.

Screenshots & Logfiles

2023-09-22 13:20:50.193 warn Tried all hosts, no connection could be established to station T8124P********.
2023-09-22 13:20:40.193 debug [P2PClientProtocol.handleMsg] Received unknown message [{"stationSN":"T8124P**********","remoteAddress":"13.251..","remotePort":32100,"response":{"message":"f1690084080000000002102765f2fa0d0000000000000000000210274bf23a3400000000000000000002102765f2fa0d0000000000000000000210274bf23a3400000000000000000002102765f2fa0d0000000000000000000210274bf23a3400000000000000000002102765f2fa0d0000000000000000000210274bf23a340000000000000000","length":136}}]
2023-09-22 13:20:40.193 debug [P2PClientProtocol.handleMsg] Connecting to host 52.58.. on port 10000 (CHECK_CAM2)... [{"stationSN":"T8124P**********","ip":"52.58..","port":10000,"data":"031ec4ed"}]
2023-09-22 13:20:40.193 debug [P2PClientProtocol.handleMsg] Received message - LOOKUP_ADDR2 - Got response [{"stationSN":"T8124P**********","remoteAddress":"13.251..","remotePort":32100,"response":{"ip":"52.58..","port":10000,"data":"031ec4ed"}}]
2023-09-22 13:20:40.192 debug [P2PClientProtocol.handleMsg] Connecting to host 13.250.. on port 10000 (CHECK_CAM2)... [{"stationSN":"T8124P**********","ip":"13.250..","port":10000,"data":"031ec4ec"}]
2023-09-22 13:20:40.192 debug [P2PClientProtocol.handleMsg] Received message - LOOKUP_ADDR2 - Got response [{"stationSN":"T8124P**********","remoteAddress":"13.251..","remotePort":32100,"response":{"ip":"13.250..","port":10000,"data":"031ec4ec"}}]
2023-09-22 13:20:35.192 debug [P2PClientProtocol._connect] Connecting to host 192.168.. on port 23838 (CHECK_CAM) [{"stationSN":"T8124P**********","address":{"host":"192.168..","port":23838},"p2pDid":"HXEUCAM-876818-NHUUC"}]
2023-09-22 13:20:35.192 debug [P2PClientProtocol.handleMsg] Trying to connect in QUICKEST mode... [{"stationSN":"T8124P**********","ip":"192.168..","port":23838}]
2023-09-22 13:20:35.192 debug [P2PClientProtocol.handleMsg] Received message - LOOKUP_ADDR - Got response [{"stationSN":"T8124P**********","remoteAddress":"13.251..","remotePort":32100,"response":{"ip":"192.168..","port":23838}}]
2023-09-22 13:20:35.191 debug [P2PClientProtocol._connect] Connecting to host 91.51.. on port 9767 (CHECK_CAM) [{"stationSN":"T8124P**********","address":{"host":"91.51..","port":9767},"p2pDid":"HXEUCAM-876818-NHUUC"}]
2023-09-22 13:20:35.191 debug [P2PClientProtocol.handleMsg] Trying to connect in QUICKEST mode... [{"stationSN":"T8124P**********","ip":"91.51..","port":9767}]
2023-09-22 13:20:35.191 debug [P2PClientProtocol.handleMsg] Received message - LOOKUP_ADDR - Got response [{"stationSN":"T8124P**********","remoteAddress":"13.251..","remotePort":32100,"response":{"ip":"91.51..","port":9767}}]
2023-09-22 13:20:35.191 debug [P2PClientProtocol.handleMsg] Received message - LOOKUP_RESP - Got response [{"stationSN":"T8124P**********","remoteAddress":"13.251..","remotePort":32100,"response":{"responseCode":0}}]
2023-09-22 13:20:35.054 debug [P2PClientProtocol.handleMsg] Received message - LOCAL_LOOKUP_RESP - Unwanted device was found, don't connect to it [{"stationSN":"T8124P**********","ip":"192.168..","port":15743,"p2pDid":"EUPRAMA-095744-JPNEC"}]
2023-09-22 13:20:35.054 debug [P2PClientProtocol.handleMsg] Received message - LOCAL_LOOKUP_RESP - Got response [{"stationSN":"T8124P**********","ip":"192.168..","port":15743,"p2pDid":"EUPRAMA-095744-JPNEC"}]
2023-09-22 13:20:34.945 debug [P2PClientProtocol.handleMsg] Received message - LOOKUP_RESP - Got response [{"stationSN":"T8124P**********","remoteAddress":"18.197..","remotePort":32100,"response":{"responseCode":254}}]
2023-09-22 13:20:34.934 debug [P2PClientProtocol.localLookup] Trying to local lookup address for station T8124P********** with host 192.168.12.255
2023-09-22 13:20:34.934 debug [Station.connect] Connecting to station T8124P**********... [{"stationSN":"T8124P**********","p2pConnectionType":"QUICKEST"}]
2023-09-22 13:20:29.933 debug [Station.scheduleReconnect] Station schedule reconnect [{"stationSN":"T8124P**********","delay":5000}]
2023-09-22 13:20:29.933 info Timeout connecting to station T8124P************

Additional context

No response

@marcprenger marcprenger added the bug Something isn't working label Sep 22, 2023
@bropat
Copy link
Owner

bropat commented Oct 6, 2023

Please send me more logs (also via mail).

@marcprenger
Copy link
Author

Sorry for the late reply. I was on vacation the last two weeks ...

I sent you some logs by email.

@hdering
Copy link

hdering commented Oct 20, 2023

I also sent my debug logs.

@bropat bropat added this to the 1.3.0 milestone Dec 3, 2023
@bropat bropat added the fixed label Dec 3, 2023
@hdering
Copy link

hdering commented Dec 15, 2023

@bropat
I have installed the version 1.2.1.

If I select Quickest connection in P2P connection type, forthermore I got the error:
Station: T8123xxx command CMD_DATABASE failed with error: ERROR_INVALID_PARAM (-110)

<html>
<body>
<!--StartFragment-->
eusec.0 | 2023-12-15 12:22:45.844 | info | Disconnected from station T8123xxx
-- | -- | -- | --
eusec.0 | 2023-12-15 12:22:45.843 | info | Initiated closing of connection to station T8123xxx for saving battery.
eusec.0 | 2023-12-15 12:22:23.928 | info | Push notification connection successfully established
eusec.0 | 2023-12-15 12:22:15.842 | error | Station: T8123xxx command CMD_DATABASE failed with error: ERROR_INVALID_PARAM (-110)
eusec.0 | 2023-12-15 12:22:15.408 | info | Connected to station T8123xxx on host 192.168.188.247 and port 19028
eusec.0 | 2023-12-15 12:22:12.182 | info | eusec.0 (371950) go2rtc started: 12:22:12.181 INF [api] listen addr=:1984 12:22:12.181 INF [rtsp] listen addr=:8554 12:22:12.182 INF [webrtc] listen addr=:8555
eusec.0 | 2023-12-15 12:22:12.181 | info | eusec.0 (371950) go2rtc started: 12:22:12.181 INF go2rtc version 1.8.1 linux/amd64
eusec.0 | 2023-12-15 12:22:10.248 | info | starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.eusec, node: v18.19.0, js-controller: 5.0.17

<!--EndFragment-->
</body>
</html>

I have shared my camera with you patrick.broetto+eu1@gmail.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed
Projects
None yet
Development

No branches or pull requests

3 participants