Getting Started: WebSocket Not Working

[IanSC]

I had some trouble but got it to run, so I am just verifying if the solution is correct, and it might help others too.

When this repo is run, I get message on the browser "Connection to device lost". Toggling the light using REST is working. Socket is not working.

I tried this solution and it solves the web socket issue: https://stackoverflow.com/questions/69350342/svelte-sveltekit-and-socket-io-client-not-working-in-dev-works-in-preview

It says to add to svelte.config.js

const config = {
  kit: {
    vite: {
      resolve: {
        alias: {
          "xmlhttprequest-ssl": "./node_modules/engine.io-client/lib/xmlhttprequest.js",
        },
      },
    },
  },
};

Is this the recommended solution?

Thank you for the great lib.

[theelims]

Can you please elaborate your setup a little bit? Which browser, are you using the vite proxy, which versions, ...

There are known issues with opera and edge #52

[IanSC]

My bad. I retested and it works without adding anything, but not consistently.

For the test, I connect directly to Wifi of esp32. I disabled FT_SECURITY in features.ini to save time.

Windows: Chrome and Edge, rest/socket working, both browser used same time Mac: Chrome and Safari, rest/socket working, both browser used same time Android Phone: Chrome, rest/socket working Mac: Brave Browser v1.65.126, rest working, websocket NOT working

It usually works, but if disconnected and reconnected, I encoountered:

• page load failing or too long
• had to trigger the REST test before websocket will work

Example:

• reboot esp32 connect to esp32
• captured portal keeps showing "Connection to device lost" repeatedly rest working, socket NOT working close capture portal
• connect to another wifi then connect to esp32
• captured portal: appears with same problem close captured portal
• use chrome connect to device: rest/socket working
• connect to another wifi then connect to esp32 captured portal: appears with blank only do not close captured portal
• go back to chrome: rest NOT working, socket working
• close captured portal
• chrome both working (usually)

Scenario 2

• reboot
• connect to esp32, close captured portal
• safari rest/socket working
• change wifi connection then connect to esp32 again
• captured portal: appears but blank
• safari rest NOT working / socket working
• close captured portal
• safari rest working / socket NOT working

The actual result keeps changing, but these are some of the results I've encountered.

For straight use, it is working fine.