Ubiquiti publicly rolls out UNMS Beta
-
Breaking changes
- It has been recommended for a while to have at least 2GB RAM for UNMS. This version can utilize them and it's highly probable that this version will not work with 1 GB even if your instance is running with 1 GB now.
- It is important to use at least airMAX FW 8.4.3+ or 6.1.3+. UNMS discovery will require these versions because previous versions don't have reliable UNMS connector.
- UNMS 0.11.0 doesn't support attribute –ssl-cert-ca and it's necessary to generate one full-chain certificate.
Added
- Add AirCube dashboard screen.
- Add AirCube backups screen.
- Add AirCube clients screen.
- Add airMAX stations screen.
- Add support for OpenStreetMap.
- Add integration to UBNT FW API for automatic FW download.
- Add NGINX reverse proxy.
- Add support for unknown device type which represents devices in problematic state. These devices have refresh button which should fix connection problem or provide steps hot fix connection. This should replace necessity of any manual update of data in PostgreSQL DB.
- Add integration to UBNT news. It's possible to see important UBNT news in UNMS UI.
- Add Let's Encrypt certificate warning note to installation wizard.
- Add columns hostname, SSID and ram to devices list.
- Add EdgeSwitch IP to devices list.
- Add error to event log when SSL cert renewal fails.
Changed
- Completely new UNMS/devices communication layer which has a significantly better performance per one CPU core.
- Upgrade to uWebSockets, NodeJS 9.1 and it's new V8 engine.
- Upgrade communication profiles and add a new minimal communication profile for low data usage.
- Remove unnecessary country in an address autocomplete.
- Return HTTP code 401 for non-existing user.
- Extend help for device refresh action.
- Change EdgeRouter backup filetype extension to tar.gz.
- Change minimal support version for EdgeSwicth to 1.7.3.
- Fill in a default username ubnt to all login forms.
- Improve device deleted event log format.
- Don't download FW during UNMS installation.
- Don't allow blocking of switched ports.
- Hide elevation input in sites/clients form.
- Round ONU signal strength.
- Modify colour spectrum and range for signal mini graphs.
- Switch signal graph to line graph.
- Show device alias name in logs and outages if exists.
- Show only sites in clients panel.
- Show error message when auto backup before UNMS update fails.
- Show missing toaster message for backups.
- Change outages default value in filter to 48h.
- Change username minimal length from 4 to 1.
- Improve Google Maps API key documentation.
- Devices menu item name dynamically change by wireless mode Stations/AccessPoint.
- Rename endpoints to clients.
Fixed
- Fix airMAX signal statistics.
- Fix airMAX excessive backups creation.
- Fix airMAX model detection.
- Fix airMAX menu rendering.
- Fix airRouter HP model recognition.
- Fix AirCube in demo mode.
- Fix AirCube PoE tag.
- Fix OLT reconnection.
- Fix OLT interfaces rendering.
- Fix OLT PON filter.
- Fix ONU restart.
- Fix ONU upgrade.
- Fix ONU speed values.
- Fix EdgeSwitch reboot.
- Fix EdgeRouter DHCP configuration.
- Fix EdgeRouter switch configuration.
- Fix EdgeRouter OSPF configuration.
- Fix EdgeRouter interfaces rendering.
- Fix EdgeRouter bridge connection status.
- Fix EdgeRouter FW upgrade (removing old FW).
- Fix devices backups CRC computation.
- Fix rendering of last-seen attribute.
- Fix background UNMS tasks and improve their performance.
- Fix multiple bugs which could lead to server crash.
- Fix custom UNMS device settings.
- Fix support for R5T.
- Fix support fo EPS16.
- Fix FW update tasks.
- Fix unread counts in left menu.
- Fix selecting a period in logs filter.
- Fix google maps endpoints markers.
- Fix UNMS settings form (Device ping address, backup maintenance options, etc.).
- Fix site status synchronisation.
- Fix refreshing of tasks upgrade status.
- Fix rendering of discovery popups.
Known issues which will be fixed in 0.11.1
- UNMS 0.11.0 doesn't support attribute –ssl-cert-ca and it's necessary to generate one full-chain certificate for a custom certificate.
- Problems with SMTP configuration.
- EdgeSwitch in UNMS discovery doesn't have FW version.
- Support for airMAX FW 8.5.x+.
- UNMS show 127.0.0.1 address instead of real one for all radios without "default route" in routing table.
- Bad sorting by SSID.
-
So, no UniFi yet.
-
But it looks like EdgeSwitch is in now. I have one I can test with that.
-
Ah, EdgeSwitch firmware 1.7.3 is still in beta
Will not be able to test as the switch is in production.
-
@jaredbusch said in Ubiquiti officially rolls out UNMS:
Ah, EdgeSwitch firmware 1.7.3 is still in beta
Will not be able to test as the switch is in production.
Might install it tomorrow as it looks like I'm off due to snow and working from home. Might try the beta firmware on the switch under my desk and see what happens lol
-
@hobbit666 said in Ubiquiti officially rolls out UNMS:
@jaredbusch said in Ubiquiti officially rolls out UNMS:
Ah, EdgeSwitch firmware 1.7.3 is still in beta
Will not be able to test as the switch is in production.
Might install it tomorrow as it looks like I'm off due to snow and working from home. Might try the beta firmware on the switch under my desk and see what happens lol
I have never had the beta firmware for any of the routers or switches cause a fail, but it is still not something I would do in production.
-
@jaredbusch it only powers my pc and other pc so it's ok to risk.
-
Website still show as beta?
Might leave it now until support for EdgeSwitch and Unifi came aboard. -
@hobbit666 said in Ubiquiti officially rolls out UNMS:
Website still show as beta?
No one ever said it was not beta. I said officially rolls out.
-
-
@jaredbusch said in Ubiquiti officially rolls out UNMS:
@hobbit666 said in Ubiquiti officially rolls out UNMS:
Website still show as beta?
No one ever said it was not beta. I said officially rolls out.
To normal people, officially released (or rolled out) means past beta. A beta release being "not released yet." The beta is released to the public, but the product is not. So you could say "UNMS Beta Officially Rolled Out", but not that "UNMS Officially Rolled Out".
If it was me having said it, you'd call it a term from "Scottland". People definitely universally use the term released to mean... well released. That the vendor sees the final product as now on the market.
-
@scottalanmiller said in Ubiquiti officially rolls out UNMS:
@jaredbusch said in Ubiquiti officially rolls out UNMS:
@hobbit666 said in Ubiquiti officially rolls out UNMS:
Website still show as beta?
No one ever said it was not beta. I said officially rolls out.
To normal people, officially released (or rolled out) means past beta. A beta release being "not released yet." The beta is released to the public, but the product is not. So you could say "UNMS Beta Officially Rolled Out", but not that "UNMS Officially Rolled Out".
If it was me having said it, you'd call it a term from "Scottland". People definitely universally use the term released to mean... well released. That the vendor sees the final product as now on the market.
The "public beta" state is a commonly accepted officially rolled out state for software products.
Many software products never leave "beta" and are officially out for years.
-
Title updated to make @scottalanmiller happy.
-
@jaredbusch said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti officially rolls out UNMS:
@jaredbusch said in Ubiquiti officially rolls out UNMS:
@hobbit666 said in Ubiquiti officially rolls out UNMS:
Website still show as beta?
No one ever said it was not beta. I said officially rolls out.
To normal people, officially released (or rolled out) means past beta. A beta release being "not released yet." The beta is released to the public, but the product is not. So you could say "UNMS Beta Officially Rolled Out", but not that "UNMS Officially Rolled Out".
If it was me having said it, you'd call it a term from "Scottland". People definitely universally use the term released to mean... well released. That the vendor sees the final product as now on the market.
The "public beta" state is a commonly accepted officially rolled out state for software products.
Many software products never leave "beta" and are officially out for years.
I don't know any product of that sort or anyone who uses that term. Do you have an example? And, I can tell you, if you show something in beta, it means it isn't released. So it's confusing to say that there is released beta products. They are competing terms. Released meaning "released" and beta meaning "not released." Public beta literally means an unreleased product that the public can test to see if they want it once released.
-
@jaredbusch said in Ubiquiti publicly rolls out UNMS Beta:
@scottalanmiller said in Ubiquiti officially rolls out UNMS:
@jaredbusch said in Ubiquiti officially rolls out UNMS:
@hobbit666 said in Ubiquiti officially rolls out UNMS:
Website still show as beta?
No one ever said it was not beta. I said officially rolls out.
To normal people, officially released (or rolled out) means past beta. A beta release being "not released yet." The beta is released to the public, but the product is not. So you could say "UNMS Beta Officially Rolled Out", but not that "UNMS Officially Rolled Out".
If it was me having said it, you'd call it a term from "Scottland". People definitely universally use the term released to mean... well released. That the vendor sees the final product as now on the market.
The "public beta" state is a commonly accepted officially rolled out state for software products.
Many software products never leave "beta" and are officially out for years.
If it's out and maintained for years - is it really beta at that point?
Frankly - what's the line in the sand that changes something from Beta to not Beta?
-
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
Frankly - what's the line in the sand that changes something from Beta to not Beta?
The developer removing the word Beta.
-
https://en.wikipedia.org/wiki/Software_release_life_cycle
Beta literally means it's not reached candidacy for release yet. RC is still not released, but is what they might consider for release once tested. Notice Beta is in the middle of the "non-released" period.
These are as the terms have always been used, even going back to the early 1980s and, I assume, long before that. Release being such a structured term that it is nearly impossible to define released without using the term released itself.
-
@jaredbusch said in Ubiquiti publicly rolls out UNMS Beta:
@dashrender said in Ubiquiti publicly rolls out UNMS Beta:
Frankly - what's the line in the sand that changes something from Beta to not Beta?
The developer removing the word Beta.
Right. Same with anything. The vendor deciding that it is ready to be released and officially releasing it. As long as they keep the term beta, they are clarifying that it's not released.
-
Beta is important because it means if you do use it, and something breaks or changes on you, you have zero recourse. You could never, ever go after a vendor that didn't support it, didn't maintain it, just changed formats, dropped it, or whatever. In any contract or legal dispute, or just trying to go after them publicly, they'd point out that you had acknowledged that you weren't using a finished product and were just looking at a preview that they were playing around with for testing and that you could not have had those expectations of it.
Like how the Spice points on SW are still in beta and can be removed or changed at any time
-
This matters a lot for the other thread where someone was upset that Ubiquiti wasn't supporting the product that he bought. But it was a beta and not a product made yet by the vendor. So hard to understand how he expected support on something that doesn't even exist yet. No matter how much he complained, it didn't change the fact that the vendor (the same one as here) had not yet made the product that he was claiming that they owed him support on.
