hi Pycom - I have a large project depending on this working - we want to do species call identification using AI in the field - but first of all the mesh needs to work. I am super frustrated as I have been asking about this now for 2 months and there has been no solution or even communication with you to assist me get this working. I have posted details in the support ticket showing that the mesh license is not installed when the device is being setup. Please can you give us some support to make this work very soon. thanks, Garth

hi peeps I am super frustrated as Pycom is not responding to any messages about the problems of getting PyMesh running. Has anyone had success with this in recent weeks? I really need to get this running and Pycom have been essential silent in response to my questions for the last 2 months. I would really love some help from someone who has got this running - we want to train it to do species call recognition in the field. thanks in advance Garth

i have the same problem, did u find a solution ?

@Manuel-Espinosa Thanks, I guess I'll need to wait a bit

Ok tried it via the AP, had to use the Laptop with Wifi, now, see what happens I (2285978) [PyGo-Firmware Updater]: Receiving firmware image ... I (2285978) [PyGo-Firmware Updater]: Remaining 00227A50 I (2350078) [PyGo-Firmware Updater]: Binary Firmware image file received! I (2350078) [PyGo-Firmware Updater]: Length 2259536 bytes I (2374468) [PyGo-Firmware Updater]: Found header => FW-Header-1: ota-finish I (2374468) [PyGo-Firmware Updater]: Performing OTA-FINISH I (2418928) [PyGo-Firmware Updater]: Found header => FW-Header-1: ota-verify I (2418928) [PyGo-Firmware Updater]: Performing OTA-VERIFY E (2418958) esp_image: image at 0x110000 has invalid magic byte W (2418958) esp_image: image at 0x110000 has invalid SPI mode 68 This looksl ike the firmware image firmware_pygo1_1.20.4.r4-pylife.bin does not fit, or what?

The LoPy4 Pin-Out does not show other connections, but these may exist on an expansion board, like the VBatt divider at P16, the User Button at P14 and the Accelerator IRQ at P13. @robert-hh thanks for this reminder; it solved my troubles eventually. One of the LoPy seems to be defective, but on all others, everything is fine now after moving around some pins. Thanks!

@Jakob-Rosenberg-0 Hello Jakob, Thanks for reply. I'm using firmware 1.20.2r4. I've tried to upgrade to Pymakr v2.22.2 and it's fixed the issue. the terminal can detect my Lopy4. [image: 1660294421486-5cd2e9e5-59e9-4a48-8204-376f25d34b38-image.png] and now I'm still adapting to new UI in v2.22.2, looks different than previous version. thank you