1.10.0beta2 is now in testing

KVM
1

Beta 2 firmware has been released for the RM1 and RM10. Firmware updates for the other models will follow over the next two weeks.

New Features

Video & Connectivity:

  1. Added WebRTC (Native) mode, implemented based on the Google WebRTC Library. It supports advanced capabilities such as automatic bitrate adjustment and FEC, improving the real-time streaming experience.

  2. Added HID transmission support for WebRTC (FEC) mode. When controlling keyboard and mouse through WebRTC / WebRTC FEC mode, HID data is transmitted through the WebRTC channel, significantly reducing keyboard and mouse latency in network environments where hole punching succeeds.

  3. Added a WebRTC data dashboard, displaying key metrics such as network latency, jitter, packet loss rate, bitrate, frame rate, and playback latency to help diagnose network and video performance.

Device Capabilities:

  1. Added Camera support for RM10, RM1PE, RM10RC, RM4PE, and RM1V2. This feature is currently marked as Beta.

  2. Added unified USB virtual device management for centralized management of related device capabilities.

Web Interface:

  1. Integrated the settings module into the Web interface and added configuration options including custom browser tab name, fullscreen toolbar visibility, and bottom status bar visibility controls.

Improvements

Startup Performance:

  1. Optimized the startup speed of RM1 / RMQ1, reducing device startup wait time.

Security & Authentication:

  1. Updated the initialization password requirements: passwords must now be at least 10 characters long and contain at least two different character types, improving initial setup security.

Bug Fixes

  1. Fixed the microphone popping noise issue reported by some users.

  2. Fixed an issue where the microphone could sometimes become unavailable.

Know issue

  1. Switching between WebRTC (Native) mode and other modes may cause the main application to crash, requiring a restart.

  2. WebRTC (FEC) mode may take longer to establish a connection.

image
image1014×820 219 KB

4 Likes
2

I like the new movement of the settings.

@minmie do you know when this issue gets resolved with ui?

Screenshot_2026-07-17-13-02-12-854_com.brave.browser
Screenshot_2026-07-17-13-02-12-854_com.brave.browser1220×2712 216 KB

The hamburger menu disappears on brave mobile once the keyboard was toggled, this becomes very unusable when someone tries to use the keyboard feature to use the arrow keys for grub, and then opening clipboard function for veracrypt boot screen.

Edit:
Also I did reset my kvm, because my atx controller does not want to follow signal since the updates, it still works, but the kvm does not report the system active or off, this is since 1.9.1 on comet pro.

But the password change is too restrictive.

Special characters: <> / miss.

3

RM1V2 is the version we will get if we buy from amazon or an the website? Confused on that. This is my result: bash-4.4# uname -m
armv7l

4

Are there any download links yet?

Also, how can one find out which RM1 version they have?

5

you have to update via OTA. login to comet, click update, toggle on beta (like in the screenshot in the main post) and then update.

6

RM4PE is listed as adding camera support but there is no OTA beta update nor is there a beta link on the download center.

7

you still didnt clarify what i rm1v2 is? Is that the release comets or the ones that are available on the store

8

Excited to see this. Can’t wait for it to be available for my RM1PE when it’s released!

9

Hi Minmie, replied to you on Discord.

Just had some feedback in there for you. Thanks!

10

Upgraded over tailscale with no issues (Dont recommend doing this if you are relying on this device for something)

Love the new settings section and the real time data stats.

Will test it out to see the performance!

Can we get an upgraded tailscale client? The one in this image was released in Jan 2026

Comet Pro 1.91 tailscale update
11

When using WebRTC(FTE), it does take longer to establish (per your notes), however, I lose all mouse/keyboard control. I just see the display screen.

12

In this version, we have modified the keyboard and mouse events to be transmitted via WebRTC by default. The advantage of this is that if your WebRTC hole punching succeeds, your keyboard and mouse latency should be significantly reduced. The downside is that if the WebRTC connection fails to establish properly, it may cause some issues.

Theoretically, if the WebRTC connection fails to establish, it should fall back to transmitting keyboard and mouse events via WebSocket.

13

It works for a few initial seconds and then quits completely. I DM my log

14

It only happen in WebRTC FEC mode or also happened in WebRTC/WEBRTC NATIVE mode?

15

Model information can be seen on the label on the bottom of the device and on its web page.

16

FEC mode it breaks and then is broken until reboot in any mode.

17

The user interface issues you mentioned on the Brave browser will be resolved in the next version.

3 Likes
18

Has anyone tested beta camera passthrough on M. Teams yet ? :slightly_smiling_face: How is it ? Any feedback would be greatly appreciated !

19

image
image2535×1415 484 KB

So far, it's working well with FaceTime.

1 Like
20

Im using Teams daily - sound and video through kvm works perfectly.
Im doing daily stand-ups via kvm and haven’t see any issues so far (setup is PC Laptop → GL-RM10 → Mac mini)

2 Likes