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
{{ message }}
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
My new DSL router is handing out a different dynamic IP to the bridge each time the router reboots (contrary to the previous behavior) and there appears to be no way to assign a consistent DHCP address to a device. This means that the SDK can no longer establish a connection to the bridge. Currently this forces me to pushlink each time the router reboots. Thanks Verizon. Is there any alternative to this? Is there some way that when I call enableLocalConnection the bridge can be discovered?
Thanks,
Cliff
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
My new DSL router is handing out a different dynamic IP to the bridge each time the router reboots (contrary to the previous behavior) and there appears to be no way to assign a consistent DHCP address to a device. This means that the SDK can no longer establish a connection to the bridge. Currently this forces me to pushlink each time the router reboots. Thanks Verizon. Is there any alternative to this? Is there some way that when I call enableLocalConnection the bridge can be discovered?
Thanks,
Cliff
The text was updated successfully, but these errors were encountered: