I also tried using my phone hotspot and this is what i got.

> ota
TCP server stopped
[2019-11-22 | 13:57:21: Disassociated]
Connecting to network
Security type from probe: WPA2-AES
Request POST /ota/0641304100000000630033000351353034373336/0
Connecting (https): ota.ack.me:443
Starting TLS
Failed to retrieve fw bundle manifest
OTA failed to update firmware
[Ready]

Hi Ayman,

I am located in Calgary, Alberta, Canada.

An older module (not part of the 35 modules order)  which i had updated to Zentrios works on the same Network with the 'ota' command.

> version
ZENTRI-AMW006-3.6.3.0, 2018-09-13T04:57:09Z, ZentriOS-W-3.6.3.0, Board:AMW006-A1W.2

> ota
TCP server stopped
[2019-11-18 | 14:42:14: Disassociated]
UUID: 0641304100000000410035001351353033363530
Connecting to network
Request POST /ota
Connecting (https): ota.zentri.com:443
Starting TLS
Bundle size: 0, Free space: 819200, Core size: 0
Firmware already up-to-date
[Ready]
 

I found my password ( also able to login to dms.zentri.com using that login and password). 

I run the command : ota <dms_username> <dms_password>

and got the following:

> ota -a dms_username dms_password
Request POST /ota/register
Connecting (https): ota.ack.me:443
Starting TLS
HTTP response: 200
Success

I noticed that the device now appeared in my list of devices on 'dms.zentri.com"

However when i run "ota" I get the following

> ota
[2019-11-15 | 13:28:57: Disassociated]
Connecting to network
Security type from probe: WPA2-AES
Request POST /ota/0641304100000000110049000251353034373336/0
Connecting (https): ota.ack.me:443
Starting TLS
Failed to retrieve fw bundle manifest
OTA failed to update firmware
[Ready]

Using  the  ota -a .... failed with :

> ota -a USERNAME PASSWORD
[Associating to MYSSID]
Security type from probe: WPA2-AES
Obtaining IPv4 address via DHCP
IPv4 address: 10.9.1.3
[Associated]
Request POST /ota/register
Connecting (https): ota.ack.me:443
Starting TLS
HTTP response: 400
HTTP error: 400
Command failed
>

Using 'ota' alone, i get :

> ota
[Disassociated]
Connecting to network
Security type from probe: WPA2-AES
Request POST /ota/0641304100000000330061000251353034373336/0
Connecting (https): ota.ack.me:443
Starting TLS
HTTP response: 500
HTTP error: 500
Failed to retrieve fw bundle manifest
OTA failed to update firmware
[Ready]
>

Using  the  ota -a .... failed with :

> ota -a USERNAME PASSWORD
[Associating to MYSSID]
Security type from probe: WPA2-AES
Obtaining IPv4 address via DHCP
IPv4 address: 10.9.1.3
[Associated]
Request POST /ota/register
Connecting (https): ota.ack.me:443
Starting TLS
HTTP response: 400
HTTP error: 400
Command failed
>

Using 'ota' alone, i get :

> ota
[Disassociated]
Connecting to network
Security type from probe: WPA2-AES
Request POST /ota/0641304100000000330061000251353034373336/0
Connecting (https): ota.ack.me:443
Starting TLS
HTTP response: 500
HTTP error: 500
Failed to retrieve fw bundle manifest
OTA failed to update firmware
[Ready]
>

We ordered a first batch of 35 from Mouser (1-2 montsh ago). And the recent set of 5 from them about a week ago. This is what i get from one of the first 35:

> get system.uuid
0641304100000000330061000251353034373336

When i run the ota command: i now get"

> ota -a USERNAME PASSWORD
Request POST /ota/register
Connecting (https): ota.ack.me:443
Starting TLS
TLS malloc failed
Error with TLS handshake: 5035
Command failed
>

Got a batch of new AMW006 boards with FW 2.3.2 I would like to claim and update.

I was unable to get it working at my Workplace so brought it home, factory reset the device, connected to my home wifi network, and tried again, but still not working. 

Below is what i get. Please note 'MYSSID' , USERNAME and PASSWORD in bold font actually had my actual router SSID, my correct username and passwords.

I used the similar approach for AMW006 devices i obtained earlier this year with no issues.

***************************

Rebooting
[2019-11-13 | 12:29:49: Disassociated]
WiConnect-2.3.2.0, Built:2015-08-06 10:03:28 for AMW006.5, Board:AMW006-A1U.2
[Ready]
[Associating to MYSSID]
> > Security type from probe: WPA2-AES
Obtaining IPv4 address via DHCP
IPv4 address: 192.168.0.251
[Associated]
> ota -a USERNAME   PASSWORD
Request POST /ota/register
Connecting (https): ota.ack.me:443
Starting TLS
HTTP response: 400
HTTP error: 400
Command failed
>

***********************

For setting up, i use the Marlin AAE001.4 board .  

I also notice that with these new batches of AMW006 devices, when the device is connected to the network, both the middle yellow led  and the green leds flash slowly unlike the previous batch i had where only the middle yellow led flashes slowly.

I have a microcontroller system with a uart based connection to an AMW006 configured as a TCP Server on port 3000. Currently my PC client program is set up to send commands  and retrieve microcontroller data via the AMW006 wifi tcp server and then exit at predetermined intervals ( 1 minute).

Is it possible to create an additional executable (in addition to the currently running one) which is constantly connected to the TCP server and listening (even though the other one is running at predetermined intervals).

The idea is so that there is always a 'listener' tcp client to process certain alarm conditions which might occur on the microcontroller system .

I have been using a Lantronix xport-05 (Ethernet to uart) device for our network communications with our microntroller system and want to migrate to the AMW006-A1W but have not been successful. 

With the lantronics xport, my C TCP client program running under linux communicates via  the xport IP and port number. Any bytes i send to the xport from my client program are automatically received through the uart port via our microcontroller (we do not need to send any other specific characters/bytes). The microcontroller reads the bytes and acts on the command.

As an example, i send the bytes 0xAA 0xCC (  0xCC is used as a termination character for my byte  command 0xAA).  The micro then sends about a 50 byte response which the client  software translates to proper english (e.g. rtc time, sensor temperatures etc).

I replaced the lantronix xport-05 module with a Digi Xbee s6B wifi module. Connected it to a wifi network, set it up in what they term the transparent mode.  I then used the default port 9750 and my unix client program works with no changes.

Can i have some help on setting this AMW006-A1W wifi module up correctly to work in this 'transparent mode'?

My progress so far:

I currently have a AMW006-A1W module and a AAE001.4 evaluation module.

This is what i have done so far. I updated the firmware from WiConnect to the latest Zentri OS. On my wifi network, the wifi module 

has been assigned an IP of 172.16.20.106. I modified the uart mode to  9600N81. I also performed the following in command mode.

>set bus.mode stream

>set wlan.auto_join.enabled  1          

> set tcp.server.auto_start     1          

>  set tcp.server.port  3000         

> save

> reboot

When i run my client program to the IP 172.16.20.106, and port 3000, it connects and sends the 2 hex bytes AA and CC, However, i do not get any response on the computer client program. Looking at the micro uart receive buffer, what it read from the AMW006, are the bytes i  previously tried to send.

Can i have some help on setting this Wifi module up correctly to work in this 'transparent mode'?