Opera Devices -> Vewd Core

In the Smart TV ecosystem, many devices include an "OMI" string in their User Agents.

In browser.yaml file you define this keyword as 'Opera Devices'
- regex: 'OMI/(\d+[\.\d]+)' name: 'Opera Devices' version: '$1' engine: default: 'Blink'

I actually don't know what "OMI" stands for but Opera TV was acquired by Vewd in 2017.
Source: https://www.streamtvinsider.com/broadcasting/opera-tv-rebrands-as-vewd

Then Vewd was acquired by Xperi (TiVo) in 2022.
Source: https://investor.xperi.com/news/news-details/2022/Xperi-Acquires-Vewd-Software/default.aspx

After the Opera TV acquisition by Vewd, the system (not sure about the terminology) is called Vewd Core.
The Official Page of Vewd Core:
https://business.tivo.com/products-solutions/smart-tv/vewd-core

The documentation of Vewd Core (version 4.8 to version 4.23)
https://integration.tvstore.opera.com/

The documentation of Vewd Core (version 4.24)
https://developers.tivo.com/smart-tv/core-developer-guide.html#revision-history
https://developers.tivo.com/smart-tv/core-developer-guide.html#user-agent-string

The documentation says "OMI" stands for The Vewd Core:

Another documentation about that references "OMI" and "Vewd Core":
https://partner.zeasn.com/partnerportal/HowtoIdentifyaSmartTVplatform/index.jhtml

As I said before, I am not sure about the terminology but using "Vewd Core" instead of "Opera Devices" seems more accurate based on the references that I shared.

Start with the OMI regex entry in browser.yaml and review how its current name, "Opera Devices," is reported. Update the detected name to "Vewd Core" if the referenced documentation supports that terminology, then verify that the OMI user-agent pattern still produces the expected version and engine values.