Replies: 3 comments 8 replies
-
|
Fresh brain, the rtsp might be working but I've got the name with a space in it and prior to now wasn't thinking I needed rtsp://ip:8554/camera_name (camera_name) at the end. I'll be able to check when I get home. |
Beta Was this translation helpful? Give feedback.
-
|
So rtsp is working great now. However, still no luck with mqtt. I've verified the settings match my other mqtt device as far as I can tell it should be working. I turned on debug log and it is below. Any suggestions? I notice here it is showing Back Yard (from my camera I presume. should I take the space out of that name?
|
Beta Was this translation helpful? Give feedback.
-
|
Cant see any issues on the mqtt logs. Do you have any logs from the broker? I usually use the eclipse mqtt broker for testing so if you have those logs it would be helpful. |
Beta Was this translation helpful? Give feedback.
-
|
I've monitored the mqtt logs from Home Assistant and don't see anything on the homeassistant discovery. I've also verified that homeassistant is the discovery mqtt topic. I'll install eclipse this evening and see if I can find anything. I am running HA Companion on a windows computer that communicates via mqtt and the Ring-MQTT integration without problem. |
Beta Was this translation helpful? Give feedback.
-
|
I've been playing with it a bit right now, unfortunately I'm not home and can't RDP from work to make sure the services are running, however I am getting a lot of connection closed messages. Every two minutes without fail. The neolink service is coming from .65 server and homeassistant is 137 and served by mosquitto broker. Full log: |
Beta Was this translation helpful? Give feedback.
-
|
This one is interesting. 137 is hosted on a VM on 65 but has it's own ip. I've also verified neolink has full access through firewall for any port any protocol. 2024-03-19 08:17:40: New connection from 127.0.0.1:56672 on port 1883. |
Beta Was this translation helpful? Give feedback.
-
|
It could be the thread holding the mqtt client is dying. Any chance you can start neolink with the environmental variable |
Beta Was this translation helpful? Give feedback.
-
|
There are some features that will cause disconnect (for example enabling floodlight when the camera dosent support it. The flood light fails and then the clients attempts a restart to restore it). So I'm hoping the debug logs can report anything like that |
Beta Was this translation helpful? Give feedback.
-
|
I can when I get home. Appreciate the responses, I'll check it at lunch. |
Beta Was this translation helpful? Give feedback.
-
I set some old Reolink cameras up at my house because I had them and thought it would be a great idea. Instead I've wasted a day+ trying to get them to work. I did install the latest firmware as a thread I read mentioned they "added" the regular http support in it. They did not. So then I discovered neolink and it's awesomeness but I'm not getting anywhere. I tried the latest version, the latest stable version, version 0.5.13 (the one linked to the thread) . The RTSP "log" shows me connected but I can't connect anything to the camera. the MQTT doesn't actually do anything.
`bind = "0.0.0.0"
[[cameras]]
name = "Back Yard"
username = "reolink"
password = ""
address = "192.168.1.178:9000"
[cameras.mqtt]
server = "192.168.1.137"
port = 1883 # mqtt servers port
credentials = ["mqtt-user", ""]
enable_motion = true
[cameras.mqtt.discovery]
topic = "homeassistant"
features = ["camera", "floodlight", "motion", "pir", "led", "reboot", "siren"]`
Beta Was this translation helpful? Give feedback.
All reactions