Known Issues & Limitations
Wi-Fi Client scanning function only works when in Wi-Fi Client mode. If you are switching the mode from AP to Client, save the configuration before clicking the SCAN button.
In the Wi-Fi Client mode, you might not be able to see all the status changes if there are more than two AP profiles in the AP list.
The "Go to edit" link is displayed in *Network Overview even when the user doesn't have permissions.
macOS users can't login to Web GUI via Wi-Fi interfaces.
When the IP is changed, the certificate for HTTPS will be re-generated. As a result, users will be required to refresh their browser and bypass the certificate warning message again.
Web GUI: Auto logout function does not work properly if users use Web GUI via IPv6.
Modbus Master: RTU doesn't support baud rate < 9600.
Dashboard: Network Overview won't be available for a while after the mode is changed to Wi-Fi.
Dashboard: Hitting the refresh button will always select the first interface instead of the current selection.
Modbus Master: If a command on the device fails, the device will go offline.
Web GUI: When a system clock skew is detected (criteria: over 5 minutes), the backend API calls will always return status code 504 and the API session authentication expiration function will not work properly (the later one will only happen if the system time is changed to a time that is in the past). The issue can be fixed by refreshing the web page and rebooting the device.
Dashboard: Wi-Fi interface will be shown as 2 entries "Wi-Fi (Wi-Fi1)" & "Ethernet(Wi-Fi1)"
ThingsPro Proxy: Only supports LAN1; Wi-Fi client needs to be disabled.
Azure IoT Edge: Every hour the edge agent will re-establish the connection for renewing the authentication information. Users can ignore the connect/disconnect entries in the event log.
Last updated on 2022-05-31 by Aeluin Chen (陳映攸)