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
We'll also have a peerDependency declared on @u4/adbkit (though I'm considering publishing our own fork, since my PR has not gotten any attention). If adbkit is present, consumers of our library will also be able to discover Control Hubs connected via USB, and not just Wi-Fi.
Speaking of which, Control Hubs connected over Wi-Fi can be found at http://192.168.43.1:8080 and ws://192.168.43.1:8081.
The text was updated successfully, but these errors were encountered:
Based on the .1, I would assume this is when a control hub is hosting the network. Do we plan to support the ability to connect a control hub to an existing network? If so, what happens if multiple control hubs are connected to the same network?
Depend on https://github.com/heineiuo/isomorphic-ws for WebSocket functionality. To use the Control Hub library from node.js, applications will also need to depend on https://github.com/websockets/ws.
We'll also have a
peerDependency
declared on@u4/adbkit
(though I'm considering publishing our own fork, since my PR has not gotten any attention). If adbkit is present, consumers of our library will also be able to discover Control Hubs connected via USB, and not just Wi-Fi.Speaking of which, Control Hubs connected over Wi-Fi can be found at
http://192.168.43.1:8080
andws://192.168.43.1:8081
.The text was updated successfully, but these errors were encountered: