WebSocket connection to 'ws://<ip>/ws' failed using M5STACK Stamp S3 about espresense

[DTTerastar]

C3 is different from S3. You've got to be using an s3 based on your serial output:

ESP-ROM:esp32s3-20210327

Cdc is for the ones that say cdc in this chart:

[DTTerastar]

Can you capture the serial output when you do this?

[ee02217]

Nothing comes out.
This is the only log from Serial:

ESP-ROM:esp32s3-20210327 Build:Mar 27 2021 rst:0x15 (USB_UART_CHIP_RESET),boot:0x28 (SPI_FAST_FLASH_BOOT) Saved PC:0x4206c1fd SPIWP:0xee mode:DIO, clock div:1 load:0x3fce3808,len:0x128 load:0x403c9700,len:0xb9c load:0x403cc700,len:0x2878 entry 0x403c98bc

[ee02217]

I was able to use other esp32 boards and enroll devices. So overall, the system is working fine.
Only enrollment in the M5 Stack doesn't work.

[DTTerastar]

That's an s3, it looks like you need the Cdc build to get serial output.

[DTTerastar]

I just tested w/ my AtomS3 Lite (http://docs.m5stack.com/en/core/AtomS3%20Lite) and it worked. Still need more info to reproduce.

[ee02217]

What is the CDC build?
I'm using this one: http://docs.m5stack.com/en/core/stamp_c3

[ee02217]

This is the log when enrolling with the new build:

Connected to: 4f:d5:8f:d4:b1:13
MTU updated: 23 for connection ID: 2
0x2a29: onRead(), value: ESPresense
0x2a24: onRead(), value: office
Client ID: 2 Address: 4f:d5:8f:d4:b1:13 Subscribed to notfications for 0x2a37

[DTTerastar]

That looks like success. So the mcu doesn't crash, but the UI seems to give up early?

[ee02217]

That's correct. The countdown hangs and I can see the error reported initially in the console.