Hey reMarkable Community! 👋 I’ve been using my reMarkable for streaming a while now, and one thing that started to get on my nerves was the constant need to check the device’s IP address just to launch a stream over Wifi (I use goMarkableStream).

I searched high and low for an easier way to access this information, but came up empty-handed. So, I decided to take matters into my own hands and create a utility to solve this issue.

🛠 Introducing the reMarkable IP QR Code Generator!

This little tool (currently experimental) is designed to streamline the process of accessing your reMarkable’s IP address. Here’s how it works:

  1. 📡 The utility constantly checks for changes in the reMarkable’s network.
  2. 🖨 If a change is detected, it generates a QR code containing the IP addresses and outputs it to a PDF file.
  3. 🖥 You can then display this PDF directly on your reMarkable.
  4. 📱 Simply scan the QR code with your mobile device to view and access the IP addresses. more info on the GitHub repository

Cheers and happy streaming! 🎉

Olivier

https://youtube.com/shorts/194ZKLPyEm0

  • rmhack@alien.topBEnglish
    1·
    1 year ago

    Neat – but also, reMarkable is configured with mDNS, and so you can probably just reach it with remarkable.local instead of an explicit IP.

    • owulveryck@alien.topOPBEnglish
      1·
      1 year ago

      Yes, on my local network it works. But when tethering with the phone or via a controlled Wi-Fi, it can help

    • kg4zow@alien.topBEnglish
      1·
      1 year ago

      I see a qmdns-responder process running on the tablet, and in the source code I see a function which sends mDNS messages.

      However, on a Linux server runing avahi, avahi-browse -ack doesn’t show anything involving “remarkable”, “rm2”, or RM110-xxx.xxxxx (the custom hostname I’m using on the tablet). (It does show all the other mDNS services running on my home , so it is working.)

      When I use tcpdump to sniff traffic from the tablet (both IPv4 and IPv6), it’s not showing anything on port 5353/udp.

      How did you make the name remarkable.local. resolve? Did you manually add a remarkable.local. hostname to your workstataion’s mDNS service database, or add a static entry in a local unicast DNS server maybe?