Ring doorbell

Get any MQTT browser / monitoring tool and see if ring-mqtt is publishing messages there based on events ( e.g., https://mqtt-explorer.com/ ).

ring-mqtt publishes in Home Assistant format by default so the Things should just show up in your inbox if you have ā€œenable discoveryā€ turned on in the advanced settings of your MQTT broker Thing. If you can see the messages with something like MQTT explorer, I would check that. If you don’t see any messages being published I would check the logs on the container and make sure you don’t need to do anything like finish your 2 factor authentication setup

1 Like

Thanks @tardismechanic. Some progress. I now have the Ring devices visible in the Inbox. I’ve added them, but their status remains Unknown:

In addition, running my Docker instance interactively so I can see what’s going on, I’m getting the ā€œring-rtsp The rtsp-simple-server process exited unexpectedly, will restart in 5 secondsā€¦ā€ repeatedly. I believe this is only for live video, so shouldn’t stop the devices coming online?

OK restarting the Docker instance again has got them Online, but still the RTSP error.

I’ve had issues with the Things showing ā€œunknownā€ or ā€œofflineā€, I think it’s a quirk in how openHAB is interpreting that MQTT topic or something. All of my Things continue to update their channels though no matter what OH says the state is so I just ignore it. I’m not sure on the RTSP issue, according to the docs here it’s only supposed to be starting the server on port 8554. Are you sure your docker container is set up correctly? Here’s all I have for mine (docker compose format), running on a pi

version: "2.1"
services:
  ring-mqtt:
    image: tsightler/ring-mqtt:latest
    container_name: ring-mqtt
    environment:
      - ENABLECAMERAS=true
      - RINGLOCATIONIDS=MyLocationID
      - RINGTOKEN=MySuperSecretToken
      - SNAPSHOTMODE=all
    restart: unless-stopped
    volumes:
      - /opt/openhab/ring-mqtt:/data
    ports:
      - 8554:8554

Out of my depth here, but looking at the RSTP Simple Server YAML, it looks like this API setup that’s causing the error. This is the Port error in the original screenshot:

I’m able to detect Ding and Motion successfully, just no Channels for Live Video, and I’m guessing it won’t work anyway as the RTSP process keeps failing in Docker.

I’ve actually never been able to get the live video to work as an item or widget since I don’t know how to get OH to display a rtsp stream (I would love to know if you do though). It looks like the only channels for live stream are switches to turn on and off the live stream service though, you would then have to have a widget or something pointing to rtsp://<ip_or_hostname>/<camera_id>_live if I understand how it works correctly. I did see that last night he released a new version that uses go2rtc instead of rstp-simple-server so you might want to try that version and see if it works better for you.

Thanks - with regards to trying the new version - is it just a case of pulling the new Docker image?

Yeah, at least that’s all it was for me