If your Joan device is having trouble connecting to the Wi-Fi network, pairing it with your computer and running the Joan Configurator might give some insight as to what is exactly the issue in the form of an Error Code.
Joan 6 Error codes (CC3100 module)
Note: Newer Joan 6 models have CC3100 modules from Texas Instruments.
Most common error that could appear is:
E: Wifi Error: cannot connect to AP
If you encounter this error please makes sure:
- Is the entered SSID of the access point correct?
- Has the Joan device gone out of range?
- Is the provided password correct?
- Does the AP use WPA2-PSK encryption?
- Is the AP on a 2.4 GHz bandwidth?
For all the error codes, please follow this link here.
Joan 6 Error codes (Raspberry Pi modules)
Note: Due to a different Wi-Fi module, these codes will appear only for Joan devices manufactured and purchased in the period from 2016 until 2017.
The following list contains all the possible Error Codes that can appear in the Joan Configurator as well as a brief description of what they mean.
There are certain issues, such as Error Codes 0x0003, 0x0019, 0x0029, and 0x0041, which you can resolve on your own. Just make sure that your network meets the requirements of our Joan devices, the Wi-Fi information you provided is correct, etc.
Also, make sure to check out the most frequent causes of Wi-Fi connectivity problems in this article, where we also give tips on how to resolve them.
For other issues, we ask you to contact us at support@getjoan.com, let us know which code appears and we will do our best to help you resolve it.
List of all potential Error Codes:
Error Code | Error Description |
0x0031 | ARP Cache entry not found |
0x0002 |
Scan command issued while the module is already associated with an Access Point |
0x0003 | No AP found
|
0x0004 |
Wrong PSK is issued while the module client tries to join an Access Point with WEP security enabled |
0x0005 |
Invalid band |
0x0006 |
Association not done or in an unassociated state |
0x0008 |
Deauthentication received from AP
|
0x0009 |
Failed to associate to Access Point during “Join” |
0x000A |
Invalid channel |
0x000E |
1) Authentication failure during “Join” 2) Unable to find AP during join which was found during scan |
0x000F |
Missed beacon from AP during join |
0x0013 |
Non-existent MAC address supplied in “Disassociate” command |
0x0014 |
Wi-Fi Direct or EAP configuration is not done |
0x0015 |
Memory allocation failed or Store configuration checksum failed |
0x0016 |
Information is wrong or insufficient in Join command |
0x0018 |
Push button command given before the expiry of previous push button command. |
0x0019 |
1) Access Point not found 2) Rejoin failure
|
0x001A |
Frequency not supported |
0x001C |
EAP configuration failed |
0x001D |
P2P configuration failed |
0x001E |
Unable to start Group Owner Negotiation |
0x0020 |
Unable to join |
0x0021 |
Command given in incorrect state |
0x0022 |
Query GO parameters issued in incorrect operating mode |
0x0023 |
Unable to form Access Point |
0x0024 |
Wrong Scan input parameters supplied to “Scan” command |
0x0025 |
Command issued during re-join in progress |
0x0026 |
Wrong parameters the command request |
0x0028 |
PSK length less than 8 bytes or more than 63 bytes The PSK length is more than 31 characters.
|
0x0029 |
Failed to clear or to set the Enterprise Certificate (Set Certificate) |
0x002A |
Group Owner Negotiation failed in Wi-Fi Direct mode |
0x002B |
Association between nodes failed in Wi-Fi Direct mode/ WPS Failed due to timeout |
0x002C |
If a command is issued by the Host when the module is internally executing auto-join or auto-create |
0x002D |
WEP key is of wrong length |
0x002E |
ICMP request timeout error |
0x002F |
ICMP data size exceeds maximum limit |
0x0030 |
Send data packet exceeded the limit or length that is mentioned |
0x0032 |
UART command timeout happened |
0x0033 |
Fixed data rate is not supported by connecting AP. |
0x0037 |
Wrong WPS PIN |
0x0038 |
Wrong WPS PIN length |
0x0039 |
Wrong PMK length |
0x003a |
SSID not present for PMK generation |
0x003b |
SSID incorrect for PMK generation(more than 34 bytes) |
0x003C |
Band not supported |
0x003D |
User store configuration invalid length |
0x003E |
Error in length of the http command (Excceds number of characters in http command, that is mentioned in the PRM). |
0x003F |
Data packet dropped |
0x0040 |
WEP key not given |
0x0041 |
Wrong PSK length The PSK length is more than 31 characters.
|
0x0042 |
PSK or PMK not given |
0x0043 |
Security mode given in join command is invalid |
0x0044 |
Beacon miscount reaches max beacon miss count (deauth due to beacon miss ) |
0x0045 |
Deauth received from supplicant |
0x0046 |
Deauth received from AP after channel switching |
0x0047 |
Synchronization missed |
0x0048 |
Authentication timeout occurred |
0x0049 |
Association timeout |
0x004A |
BG scan in given channels is not allowed |
0x004B |
Scanned SSID and SSID given in Join are not matching |
0x004C |
Given number of clients exceeded max number of stations supported |
0x004D |
Given HT capabilities are not supported |
0x004E |
Uart Flow control not supported |
0x004F |
ZB/BT/BLE packet received and protocol is not enabled. |
0x0050 |
Parameters error |
0x0051 |
4-way handshake failure. |
0x0052 |
Power save support is not present for a given interface. |
0x00B1 |
Memory Error: No memory available. |
0x00B2 |
Invalid characters in JSON object |
0x00B3 |
Update Commands: No such key found. |
0x00B4 |
No such file found: Re-check filename |
0x00B5 |
No corresponding webpage exists with same filename |
0x00B6 |
Space unavailable for new file. |
0x00C1 |
Invalid input data, Re-check filename, lengths, etc. |
0x00C2 |
Space unavailable for new file |
0x00C3
|
Existing file overwrite: Exceeds size of previous file. Use erase and try again |
0x00C4 |
No such file found. Re-check filename. |
0x00C5 |
Memory Error: No memory available. |
0x00C6 |
Received more webpage data than the total length initially specified. |
0x00C7 |
Error in set region command |
0x00C8 |
Webpage current chunk length is incorrect |
0x00CA |
Error in Ap set region command |
0X00CB |
Error in AP set region command parameters |
0x00CC |
Region code not supported |
0x00F1 |
HTTP credentials maximum length exceeded. |
0x0100 |
SNMP internal error. |
0x0104 |
SNMP invalid IP protocol error |
0xBB01 |
No data received or receive timeout. |
0xBB0E |
Internal error. |
0xBB16 |
Entry not found for multicast IP address |
0xBB17 |
No more entries found for multicast |
0xBB21 |
IP address error |
0xBB22 |
Socket already bound. |
0xBB23 |
Port not available. |
0xBB27 |
Socket is not created |
0xBB29 |
ICMP request failed |
0xBB33 |
Maximum listen sockets reached. |
0xBB34 |
DHCP duplicate listen |
0xBB35 |
Port Not in close state. |
0xBB36 |
Socket is closed or in process of closing |
0xBB37 |
Process in progress |
0xBB38 |
Trying to connect non-existent TCP server socket. This error is issued when the module tries to connect to a non-existent TCP server socket on the remote side. The device cannot connect to your on-premises server. Check if the on-premises server (VM) can be accessed from the same network as Joan is connected to. You can do that by using the ping command inside a terminal (e.g. ping 10.0.1.139). If the server is accessible, also proceed to check if by any chance you are blocking the port 11113 on your firewall. |
0xBB42 |
Socket is still bound |
0xBB45 |
No free port |
0xBB46 |
Invalid port |
0xBB4B |
Feature not supported |
0xBB50 |
Socket is not in connected state. Disconnected from server. In case of FTP, user need to give destroy command after receiving this error |
0xBB9C |
DHCPv6 Handshake failure |
0xBBA1 |
No DNS server was specified |
0xBBA3 |
DNS query failed. |
0xBBA4 |
Bad DNS address |
0xBBA8 |
Parameter error |
0xBBAB |
Empty DNS server list. |
0xBBAF |
DNS duplicate entry. |
0xBBB3 |
DNS IPv6 not supported |
0xBBD1 |
SSL Context Create Failed. |
0xBBD2 |
SSL Handshake Failed. Socket will be closed. |
0xBBD3 |
SSL Max sockets reached. Or FTP client is not connected |
0xBBD4 |
FTP client is not disconnected |
0xBBD5 |
FTP file is not opened |
0xBBD6 |
FTP file is not closed |
0xBBD9 |
Expected 1XX response from FTP server but not received |
0xBBDA |
Expected 2XX response from FTP server but not received |
0xBBDB |
Expected 22X response from FTP server but not received |
0xBBDC |
Expected 23X response from FTP server but not received |
0xBBDD |
Expected 3XX response from FTP server but not received |
0xBBDE |
Expected 33X response from FTP server but not received |
0xBBE1 |
HTTP Timeout |
0xBBE2 |
HTTP Failed |
0xBBEB |
Authentication Error |
0xBBED |
Invalid packet length, content length and received data length is mismatching |
0xBBF0 |
HTTP/HTTPS password is too long |
0XFFFF |
Listening TCP socket in module is not connected to the remote peer, or the LTCP socket is not yet opened in the module |
0xFFFE |
Sockets not available. The error comes if the Host tries to open more than 10 sockets |
0xFFFC |
IP configuration failed |
0xFFF8 |
1) Invalid command (e.g. parameters insufficient or invalid in the command). 2) Invalid operation (e.g. power save command with the same mode given twice, accessing wrong socket, creating more than allowed sockets ) |
0XFFFA |
TCP socket is not connected |
0xFFC5 |
Station count exceeded max station supported |
0xFFC4 |
Unable to send tcp data |
0xFFBC |
Socket buffer too small |
0xFFBB |
Invalid content in the DNS response to the DNS Resolution query |
0xFFBA |
DNS Class error in the response to the DNS Resolution query |
0xFFB8 |
DNS count error in the response to the DNS Resolution query |
0xFFB7 |
DNS Return Code error in the response to the DNS Resolution query |
0xFFB6 |
DNS Opcode error in the response to the DNS Resolution query |
0xFFB5 |
DNS ID mismatch between DNS Resolution request and response |
0xFFAB |
Invalid input to the DNS Resolution query |
0xFF42 |
DNS response was timed out |
0xFFA1 |
ARP request failure |
0xFF9D |
DHCP lease time expired |
0xFF9C |
DHCP handshake failure
|
0xFF88 |
This error is issued when Websocket creation failed |
0xFF87 |
This error is issued when module tried to connect to a non-existent TCP server socket on the remote side This error is issued when the module tries to connect to a non-existent TCP server socket on the remote side. The device cannot connect to your on-premises server. Check if the on-premises server (VM) can be accessed from the same network as Joan is connected to. You can do that by using the ping command inside a terminal (e.g. ping 10.0.1.139). If the server is accessible, also proceed to check if by any chance you are blocking the port 11113 on your firewall. |
0xFF86 |
This error is issued when tried to close non-existent socket. |
0xFF85 |
Invalid socket parameters |
0xFF82 |
Feature not supported |
0xFF81 |
Socket already open |
0xFF80 |
Attempt to open more than the maximum allowed number of sockets |
0XFF7E |
Data length exceeds mss. |
0xFF74 |
Feature not enabled |
0xFF73 |
DHCP server not set in AP mode |
0xFF71 |
Error in AP set region command parameters |
0xFF70 |
SSL not supported |
0xFF6F |
JSON not supported |
0xFF6E |
Invalid operating mode |
0xFF6D |
Invalid socket configuration parameters |
0xFF6C |
Web socket creation timeout |
0xFF6B |
Parameter maximum allowed value is exceeded |
0xFF69 |
Invalid command in sequence |
0xFF42 |
DNS response timed out |
0xFF41 |
HTTP socket creation failed |
0xFF40 |
TCP socket close command is issued before getting the response of the previous close command |
0xFF36 |
Wait On Host feature not enabled |
0xFF35 |
Store configuration checksum validation failed |
0xFF33 |
TCP keep alive timed out |
0xFF2D |
TCP ACK failed for TCP SYN-ACK |
0xFF2C |
Memory limit exceeded in a given operating mode |
If you require any additional assistance, please contact support@getjoan.com.