What's New

Today we fixed a bug that prevented blocking clients - in fact, only the first client on the list was blocked. Should work fine now.

From now on you can globally (per network) disable the LEDs on APs. Just turn off the Configure > Advanced settings > Enable AP LEDs.
Requires firmware 0.0.237 or later.

From now on, if you turn the Enable Mesh in Configure > Advanced Settings off, the nodes will stop transmitting the altiwi_orphaned SSID which mignt be bothering or confusing.
The SSID is needed only when mesh is used (you are using repeater nodes) to allow checkin for orphaned devices to pickup network configuration prior the mesh is established.
If you already have your network set to disable mesh and want to get rid off this SSID you can either reboot the devices or click Force config update yellow button at the bottom of the main screen. No firmware update for this update is necessary.

With a transition to underlying OpenWrt 19.07 operating system there was introduced a bug that affected the stability of wireless operation on 5GHz band, namely with modern 802.11ac capable devices. This has been fixed in firmware 0.0.234.

As of version 0.0.234 the devices' firmware was upgraded to OpenWrt 19.07.1, which is latest stable release version of OpenWrt.

All access points now have unique hostname in the form ap-macaddress. Earlier the hostname was always set to OpenWrt which could confuse administrators and polute dns namespace.
Requires firmware 0.0.232 or later.

From now on, the e-mail notification is sent not only to the first user of the netowrk but to all, who have acces. Also, you can enter a comma delimited list, if you want to use completely different set of e-mail addresses for notifications.

Just implemented the e-mail notifications when your node goes down (and also when it goes up). To get the notifications for your network, just check the "Send notifications" in Configure > Network. Notifications will be sent to your e-mail address (if the e-mail filed is left empty) or you can choose any other address you want, for example to notify your NOC.

Form now on you can show the printable page with wifi name and password along with a QRCode for mobile device users to easily connect to your WiFi.
Just click the Print QR button next to Secure or Internet WiFis. For Captive and Enterprise network it is not provided as it makes no sense.

From now on you can easily see whether your access point is online or disconnected from console and also the re is an clear indication of mode .
Gateway - node is wired and meshing for this network is turned on
Repeater - node is connected wirelessly via mesh, number shows number of hops
No mesh - node is wired and meshing is turned off for this network

From now on you can delegate access to your dashboard to other Altiwi user. Just use his (registered) e-mail address in Configure > User access.

The LED are now showing the connection status of the device. In general RED means no connection to the dashboard, green - connected as gateway, orange, connected as repeater. Furter improvements will come up shortly.
Requires fw 0.0.228 or later

As of 0.0.228 there has been a number of improvements of overal connection stability. The devices are able to recover from most of the dashboard connection issues. Note - there are some issues in the meshing scenarios, we advice you to turn off meshing if not necessary in Advanced > enable mesh, tick off

Another attempt to fix the negative traffic graphs :-) Requires firmware 0.0.211.

As of firmware 0.0.209 or later, we are using the new up-to-date OpenWrt 19.07 RC2. Please report any unexpected changes that may arise.

Starting with firmware 0.0.210, the noder require pairing with the dashboard. Without pairing the AP will not receive any configuration changes. The pairing shall be performed only once and then just in a case of manual firmware update. Just use the "Pair" or "Pair all" button next to the access point.

By selecting the Access Point and clicking Debug button, you can now click Get logread or Get dmesg to receive the logging from the access point directly to your console. By clicking the aquisition date you can even download it as a text file to your machine for further analysis. To see your logs, wait some 10 seconds and then press refresh in your browser to see results.

As of 0.0.182 there should be fixed an overflow bug where traffic graphs shown negative numbers when total traffic exceeded 2GB. This update also contains minor updates in logging and DHCP issues.

In some circumstances, clients connected to Internet only wifi did not get the IP address. This has been fixed in fw 0.0.162.

When changing password on inet only wifi the affected wifi was changed to "secure". This bug has been fixed.

In rare cases when the devices missed the configuration update opportunity, it would be fine to have the trigger to force them to update its config regardless of their knowledge if they should or should not update. From now on there is a button called Force config update at the bottom of the main dashboard which does exactly this - forces the devices to reload their config.

Under Edit Access point > Debug there is now a possibility to send the content of the logs located on the device to the console. The Send logread and Send dmesg button will send the logging to the console for further investigation.
Initially, you will not have access to the logging but the plan is to have this log available for you, so stay tuned!

From fw 0.0.142 there is a change in collecting traffic charts that reflects for the new WebSocket node connections. The traffic data are now hold by the devices and are reported only if you connect to the dashboard, so you can see last 24 hours of traffic data.
Please note that the traffic data are held in access point's memory only, so in case of device restart, it's traffic data are gone. It is intended behaviour.

It may be difficult to read the MAC address from the small sticker on the back of the device.
From now on, you can add UBNT AC LR devices to the dashboard just by scanning their QR code from your phone. Please allow browser to use your camera :-)

As we strive for keeping the service as a one-time-fee license, we need to keep the costs down. This is the first of iterations that will help us to drive the cost favorable levels. The prototype (beta) firmwares simply hammered our servers each 10 seconds with all the available data, which, simply put, is not sustainable.
During our iterations, there might some inconveniences occur. Righ now you can expact following:
1. The stats chart will miss large chunks of data
2. after login, you can see last contact time from APs a very long ago. This should be OK on subsequent page loads.

Both above mentioned issues are known behavior and will be addressed soon :-)

Firmware 0.0.126 and above.

Fom now on, there is an "Band" column in the Client list which indicates whether the client is connected to a 2.4 GHz or 5 GHz band.

Cloudtrax import crashed when there was no network defined yet. This has been fixed now.

When there was long-enough internet outage, APs may stuck in transmitting only altiwi_orphaned ssid until a change in configuration or reboot the ap happened. This has now been fixed.

There was a bug when dashboard crashed when created network with no location data nor time zone info. This stupid bug has been fixed.

On certain circumstances, the AP could brick itself when turned on prior adding it to the console. This would imply the need to manually reflash the device. The condition has been removed in firmware 0.0.124 which fixes the issue.

If you encountered the issue when your OMP2-XX device checked in correctly but did not show any wireless, just remove the access point and re-add it. This will fix the issue. Was caused by wrong hardware type used on device creation.

Automatic traffic chart refresh has been turned off to conserve server resources. The chart is reload on each page load, formerly it was each 10 minutes.

Firmware updates can be now performed automatically during Maintenance window.

Timezone setting has not been populated, if the correct TZ could not be derived from street address of your network. Correct behaviour is that if you provide correct Street Address, TZ is populated automatically but in case the Street Address does not geocode correctly, the drop down menu value of Time zone in Network settings should be used. This has now been fixed.

In Config > Maintenance you can set the maintenance window, which will be used for maintenance tasks such as firmware upgrades, survey scans, channel optimisations etc. You will be notified if your Time Zone is not set. It might happen either if you did not set the TZ during the Network creation, or the system was unable to determine the TZ from your street address. Timezone is important, as it affects the actual time in tour TZ, when the maintenance is performed and might shift network disruptions to unwanted period. So please make sure that your TZ is set correctly, if not, UTC will be assumed.

There was a long standing bug that prevented the repeater nodes to check in after firmware upgrade until the did not connect to a wired internet for the first time. This has now been fixed in FW 0.0.112.

Note - the issue background causes that even if you upgrade the firmware to a correct one, the node will need to connect via ethernet cable. But all subsequent upgrades should work as expected. We created two firmwares - 0.0.112 and 0.0.113 which are essentially the same, only the version number differs. After upgrading to FW 0.0.112, wired connection is necessary, but when you place a node with FW 0.0.112 firmware into the repeater mode and do an upgrade to FW 0.0.113, it should check in, after some 10 - 15 minutes.

We added the capability to restart the dashboard checkin process shall it stale. From FW 0.0.112 if there is no answer within 5 minutes from the checkin process, it is restarted automatically. This should solve the issue when the device stops checkin-in which is mostly (but not solely) caused by transient network errors.

Edit Access Point now shows correct fw version - was broken after checkin update.

If you click to edit an access point, you can now see the traffic stats per last 24 hours for this node individually.

- requires FW 0.0.95 or higher

From now on there are information about performance of each connected access point. You can see uptime, free memory, load and number of connected clients.

- requires FW 0.0.95 or higher

Next to the traffic graph you can find a simple chart showing currently connected clients vs theoretical maximum. This maximum is counted as a sum of capacities of each node and it is by no means a "hard" limit.

- requires FW 0.0.95 or higher

The console checkin backend has been completely rewamped. That means that all devices connected will look like there is no connection to the dashboard. To resolve this, please update to the latest firmware in Configure > Firmware update > Upgrade now.

- requires fw version 0.0.95 or later

Fixed (hopefully) issue, when inbuilt DHCP server did not serve the DHCP address for clients connected to Internet only SSIDs. This was happening only sporadically and the fix needs further testing.

From 0.0.84 the devices are based on the latest OpenWrt.

From now on you can perform a tcp dump directly from the web console! Just click on access point, click "Debug" button, optionally fill-in the interface (br-lan0 will be used as default if you leave it blank) and click "get tcpdump".
The process will let you wait until the device picks up the command, then it will notify you to perform the actions you want to debug (e.g. connecting troublesome device etc) and after one minute the dump will be stopped and uploaded to the console. You can then download standard PCAP file and open it in Wireshark or other packet analyser.
The UI will get some improvements like interface select from menu, but we believe it is highly valuable just now. We expect that this feature will get into the subscription based offering, but right now it is free for anybody.
Requires firmware 0.0.65 and higher.

From now on we support WPA Enterprise with external RADIUS server, so your users can use external authentication you might have in place.
Requires firmware 0.0.61 and above.

Creating of Captive portal ended-up with validation error on non-existent password. This has now been fixed.

Previously, the chart legend showed MBs but in fact the numbers were in bytes. Now works as expected.

Cloudtrax import crashed if too long Network notes has been filled in. This has now been fixed.

Traffic chart now shows total upload and download for last 24 hours

In some circumstances, data might be missing.

The units are now bad (we show bytes and mark them as megabytes) but it will be fixed soon. :-)
Requires fw 0.0.57 and higher.

Client list now show both IP and hostname for clients connected to Internet Only and Captive wifis. These information are intentionally not shown for bridged (Secure) wifis. This is by design. To see your bridged Clients IPs and hostnames, please consult your router DHCP table.
Requires firmware 0.0.55 and higher.

Bug resulted in showing incorrect IP address in some circumstances, eg, when client was previously connected to different wifi, interface might shown the former one. This has now been fixed.

Client list now shows IP address together with the time the station has been seen last. The Client list shows only stations which has been connected in the last 24 hours.
Requires firmware 0.0.53 and above.

Wifi your client was last connected to was broken (shown always different one). This has now been fixed. Also added time of last update.

From now on the VLAN settings per SSID are preserved during Cloudtrax import.

Secure wifis weren't imported from Cloudtrax correctly upon certain circumstances. (Import occured after introducing VLAN support) This has now been fixed.

Site survey now shows the interference strength in colors - red are most interfering (strongest) while green networks are OK. The tresholds will probably change in the future based on your feedback :-)

There was an issue when automatically reflashing OM5P-ACv2 from the web console. This has now been fixed.

The issue was caused by too short password on some of the wifis. PSK2 password must be between 8..63 characters and the UI did not validate the password length. This is now fixed. If you encounter the issue, please change your password accordingly. The side effect of the issue was that there were some ssids not visible, including the affected one.

Secure WiFis SSIDs can now be added to a VLAN. By default, Secure WiFi is bridged to LAN, but when you choose VLAN ID in the WiFi properties (WiFi > Edit or Add Secure WiFi), the SSID is bridged to a particular VLAN. Don't forget to set this VLAN as tagged on your switch port.

From now on you can turn on/off the meshing capability. Turning it off might be a good idea in complex networks (e.g. APs on different network segments), to prevent accident loops, when all nodes use wired connection.
Generally, it is not a good idea to have nodes on different L3 subnets and have meshing turned on, because the loop detection in mesh is done on L2 and would break eventually in such scenario.
The option can be found at Configure > Advanced settings > Enable Mesh

From now on each network has its own unique id and password for meshing. Formerly there was one common config.

Root password is now transferred upon network import.

Fixed bug that returned error when trying to create an Internet only wifi.

Global clients from Clients>Show, Blocked Clients are now propagated to devices' configuration, so basically, if you block/unblock client from UI, it now works as expected. Previously, only per WiFi manual MAC address block worked.

From now on there is a possibility to add a MAC address to a blocked list on captive portal to prevent access and also to add a MAC addresses to Trusted MAC list to avoid showing the splash page and let trusted device in.

When importing from Cloudtrax, there was an issue that prevented the transmit power to be set properly in case that there was "Use country default" setting. This has now been fixed.

Earlier the images uploaded into the Splash page editor did not show correctly when they were actually used by accessing the splash page from client device. This is now fixed, but keep in mind that you need to remove the captive portal wifi and re-add it to make the feature work.
Images can be added just by drag and drop from your computer disk.

For Secure and Internet-Only wifis you can now set MAC a list of MAC addresses to be blocked from wifi access. Captive portal uses different mechanism and will be added later.

From now on the imported networks correctly recognises public networks and sets them correctly as Internet-Only.

WiFis (SSIDs) now have color-coded badges to quickly distinguish WiFi type as Secure, Internet-Only or Captive.

When you create a new network, system will try to find a country from your location and if it succeeds, the country will be used as default country for any new radios you will add (Configure > Radio Settings > Country) instead of the default US.
This setting is populated just once upon network creation, if you want to change the country settings (used for wifi regulatory requirements) later, you should change the Radio settings, not the location.

Importing of Cloudtrax legacy networks (those using fw like ng481) is not and probably will not be supported. But if your account possesses one, it crashed during import. This is now fixed by ignoring those networks.

Up to now, the access points imported from the Cloudtrax used network default channel settings. From now on, custom channels, channel widths and transmit powers are imported and applied to the corresponding access point.

We are happy to announce, that we added preliminary support for device flashing after successful synchronization from Cloudtrax. The idea is following:
You can synchronize your networks from your Cloudtrax dashboard by pressing the green Synchronize... button in Cloudtrax > Import config... This step will copy all current data from Cloudtrax to Meshrobot, but will not create those networks in the dashboard. To do so, please select the network you want to import and click the grey Import button on the right side.
When you click the button, settings for this particular network will be transferred to dashboard and new network will appear in your Networks list. Please note, that if you had already added network with the same name, the network will be duplicated and the settings will be transferred to duplicate network, rather than to overwrite your current settings. This may lead to a situation when not all of your access points would be transferred, as those with already already added MAC addresses will be skipped.
After successful import a new red button will be shown labeled Reflash. When you click it, we will instruct Cloudtrax to re-flash the firmware in all nodes that belong to this network to new firmware. After successful refresh, the devices will stop checking in to the Cloudtrax console and will start to check in to Cloudrobot dashboard after some 10-15 minutes. Please note, that there is not an automated way how to revert the firmware back to Open-Mesh one other than manual reflash process as described in their support website.

Known limitations:
- The process does not work for A40/A60 devices but will be aded soon.
- Although the all network import from the Cloudtrax transfers all the configuration data, there is a bunch of limitations when importing actual network to a Cloudrobot dashboard. Only some basic settings will be transferred now, but we are working on improving the feature set.
- The flashing process seems not working with meshing nodes. This will be addressed later, now we recommend to try this feature only on All-wired networks.

Updated Clients > Show to display WiFi (SSID) on which particular client is connected.

Under Configure > Advanced settings was added the possibility to set root password for device CLI access.

Requires firmware 0.0.47 or newer.

The Clients > Show feature got first preliminary support. It means that you can see devices connected to your network.
As of now, it has many limitations:
* there is no time limit, if device has been seen once, it is on the list forever
* hostname and IP addres is not populated
* the Wifi (SSID) on which the device is connected is not displayed properly. Regardless the SSID used, always the first Wifi is reported, even though we have the information.

Requires firmware 0.0.42 or newer. You can upgrade your access points by selecting Configure > Firmware upgrade > Select firmware > Upgrade now

Site Survey feature has been added. You can find it at Configure > Site Survey. After triggering the scan via "Scan now" button, you can see all adjacent wireless networks sorted by strongest signal seen by particular AP.
That said, you can see the same SSID multiple times with signal strength as your particular access point sees the network.
When dealing with the interference, you should resolve the strongest signals first.
For your convenience, there is a possibility to hide your own networks by clicking the "Hide my own Wifis".

Requires firmware 0.0.40 and above.

You can reboot your device by clicking on the Reboot button.