Discovery is currently implemented as a broadcast. On some networks broadcasts are not propagated. That effectively means Twinkly devices cannot be found. Unicast connections work just fine (e.g. because they are forwarded across networks).
Twinkly app falls back to unicast for each address on the network. It does this only once - when new device is added to the app and then stores information about the device and addresses it directly.
Doing unicast discovery by CLI would be too expensive.
I'd like to mitigate this by ability to skip discovery - probably implicitly when --hostname is specified.
Skip of discovery might require #59.
Discovery is currently implemented as a broadcast. On some networks broadcasts are not propagated. That effectively means Twinkly devices cannot be found. Unicast connections work just fine (e.g. because they are forwarded across networks).
Twinkly app falls back to unicast for each address on the network. It does this only once - when new device is added to the app and then stores information about the device and addresses it directly.
Doing unicast discovery by CLI would be too expensive.
I'd like to mitigate this by ability to skip discovery - probably implicitly when
--hostnameis specified.Skip of discovery might require #59.