Unimus forum

As per documentation, the correct sequence should be this: copy run start$[no-wait] $[enter] The $[no-wait] tells Unimus to not expect any known inputs (normally a prompt, or a y/n question, etc.), but to immediately proceed to next command. The behavior is fully documented here: https://wiki.unimus...

Not possible, sorry. RoMON is MikroTik proprietary, and it's not even IP-based on L3. To support it, we would have to completely reverse-engineer the protocol, which is just not possible due to time constrains, and also legal issue (it's MikroTik proprietary intellectual property).

Thank you for the report - this is now fixed and will be a part of the 2.0.11 release.

Please enable Debug Loging AND Device Ouput Logging (Zones > your_zone > Debug Mode), re-run Discovery, and create a Support Ticket on our Portal (and attach both the debug logs).

We we investigate further.

Thanks!

If you run a discovery and wait for it to fail, what is the discovery fail reason?
(click on the red job status indicator to the right of the device)

Definitely - happy to add support for these. Please create a Support Request on our Portal, and one of our devs will reach out with the data we need.

Hi,

2.0.10 is the latest stable version. 2.0.11 is currently nearing the end of it's development cycle, it should be released next week

Partial update: Config Push based on Tags will be released in 2.0.11.

Importers tagging devices is already designed and planned as well.
Likely to come in one of the point releases in 2.1.

Update: Config Push based on Tags will be released in 2.0.11.

Due to the recent security-related events in our industry, we have received multiple requests / questions on the security of the Unimus code-base, build pipeline and official releases. We have published a security-related blog that outlines the steps we took in the last months to validate the integr...