👋 Have tried and succeeded in flashing a handful of ESP32 devices (D, E and a GPy 1.0). The problem that I am facing with all of them is that I cannot interact with them over WiFi without manually setting the ip with the -d flag. Version: v1.31.0 SDK version: v2.0.0-alpha.143 When I run

jag run x.toit

, I get:

Error: didn't find any Jaguar devices.
Perhaps you need to be on the same wifi as the device.
You can also specify the IP address of the device

I opened the console.toit.io instead and tried provisioning and claiming the device there instead. It failed to claim the device. This was the same case for all of the devices that I tried with. Tried both with a 2.4 GHz WPA3 network and a personal hotspot from my iPhone. No spaces in the SSID and with Maximise Compatibility enabled. Next thing I will try, if you dont have any other suggestions, is to create an IoT network with another router.

The problem you are facing is likely that your computer and the ESP32 aren't on the same network. Jaguar is designed to be run in a local network, and uses UDP broadcast packages to announce the presence of the devices. Those are often not routed from one network to another. If the device is still reachable through IP addresses, then giving the IP address to Jaguar can still make it work. Typically we would do this as a scan step. For example:

jag scan 192.168.1.47

This can be necessary if the ESP and the dev-PC aren't in the same network, but is also sometimes required when a Windows firewall is a bit too conservative. If you want to access your devices outside of your home network, then Jaguar isn't really designed for that (it's a dev tool). We recommend to use Artemis (https://docs.toit.io/getstarted/fleet) instead. The Toit console is deprecated and should only be used for legacy devices.

Hi Florian Thanks for your reply. They are on the same network. I get this from monitor: https://cdn.discordapp.com/attachments/1221408099240509500/1221430249309470760/image.png?ex=66128c90&is=66001790&hm=1c088307878fd17a036599844c769ffd96e8331210fccc82be7a5fcde5b1c6ad&

jag scan 192.168.0.20

should set the default device to that address.

Great. Thanks Florian. Now I can start building

Jaguar doesn't remember name associations. So doing a

jag run -d foobar

would make it do a new scan. And since scans don't work in your setup things break...

👍 Thought something else was wrong, because I followed the guide to the letter: https://docs.toit.io/getstarted/device

It assumes that the UDP packets make it to the desktop.