Closed omgmog closed 8 years ago
Hey @omgmog - thanks for the report. Sometimes I've noticed that rebooting Tide can solve discovery problems like this when there's a network change, did you try that?
I also think it would be useful for advanced users like yourself to enter an IP address manually, which would be a good workaround this problem if we can't solve it in all cases.
Hi @joerick yeah I tried both restarting Tide and rebooting the Tingbot, in various orders.
I'll switch to a manual IP address a bit later and see if that works. Cheers.
Sorry I meant that you could enter your DHCP-assigned IP address into Tide, to skip the discovery process entirely. But that feature doesn't exist yet.
In the meantime, here's a workaround...
window.vueInstance.$children[0].$children[0].devices.push({name:'192.168.2.13',target:'192.168.2.13'})
That works perfectly, and is a good enough solution for me in the odd case that I'm connected this way.
Cheers!
yeah this works for me too... thanks :)
Tide version: 0.3.5 (0.3.5.99) OS X
Had it connected to my regular WiFi at home without any problems.
Now at my office I've got it connected to the "Internet Sharing" WiFi on my Mac, and Tide can't find the Tingbot.
As you can see it's connected:
But Tide doesn't recognise that it's available: