You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great app. Would like an option to connect to two (local) UniFi controllers. Now only one IP adress is accepted.
The scenario is two cloudkeys residing on different subnets (intentionally separated). The Homey is on a separate (IoT) subnet but have access to both.
The preferred solution would give me an option to point to two different IP:s. Having different passwords for login is not critical/important (nice to have). Would be quite OK to have the app alternating between the two cloud controllers. Only need to know if the client is present (or not).
More on the scenario: The same client might connect to any of the APs handled by either one of the cloudkeys (thus having the same MAC, but different IP dependent on the connected network). The client user names (as seen on the UniFi controller) are usually the same on both the cloudkeys and can be changed if needed to be uniq (don't know if that is relevant information). It would be nice to know what cloudkey (network) the user is connected to, but that is not critical/important. Only need to know if the client are present or not. Only need to know if the client is present (or not).
The text was updated successfully, but these errors were encountered:
Great app. Would like an option to connect to two (local) UniFi controllers. Now only one IP adress is accepted.
The scenario is two cloudkeys residing on different subnets (intentionally separated). The Homey is on a separate (IoT) subnet but have access to both.
The preferred solution would give me an option to point to two different IP:s. Having different passwords for login is not critical/important (nice to have). Would be quite OK to have the app alternating between the two cloud controllers. Only need to know if the client is present (or not).
More on the scenario: The same client might connect to any of the APs handled by either one of the cloudkeys (thus having the same MAC, but different IP dependent on the connected network). The client user names (as seen on the UniFi controller) are usually the same on both the cloudkeys and can be changed if needed to be uniq (don't know if that is relevant information). It would be nice to know what cloudkey (network) the user is connected to, but that is not critical/important. Only need to know if the client are present or not. Only need to know if the client is present (or not).
The text was updated successfully, but these errors were encountered: