ISY-99i/ISY-26 INSTEON:Errors And Error Messages
Viewing the Log file
Viewing the log file from the ISY is best done using a database program. By default the ISY produces a file for use in Excel. However, any database program that can read comma separated values (.csv) files can be used to view the log.
From the ISY Administrative Console select the Menu item Tools | Log. A requester will open asking if you wish to view the log in Excel. Selecting Yes will produce a file and open Excel. Selecting No will open a file requester allowing you to save the file to a location of your choice. Start your database program and open the saved log file.
- When opening the log in Excel you will be requested to allow macros to run. You must select OK for the macro to run and to have access to the log file. The log file contains the date and category intersections for all the devices linked to ISY.
- If your log file is empty you probably don’t have macros enabled. To enable macros:
- Click on the Tools menu
- Select Macros
- Select Security and choose Medium for level
The 6 columns provided are
INSTEON Device: The name of the device
Control: The property on the device that changed
Value: The value of the property
Time: The time of the event
User: The initiating party (Web, Program, ELK, System)
Log Type: The type of entry (Start, Log, Error Code in case of error)
The error codes are contained in column 6, Log Type.
Sorting can be applied as your database program allows.
Log size can be configured using the ISY shell. See Configure_Maximum_Log_Size
The log can be cleared using the menu item Tools | Clear Log.
Outputting the Errors
The ISY error messages are output in the java console, but the output is not enabled by default. You will need to enable them using the ISY Telnet interface. See Debug in the Advanced_Configuration_Guide.
- Use the "Logon to My INSTEON ISY Now!" weblink, enter your user name and password when prompted to log in.
- At the bottom right, in System tray, on your computer screen right mouse click the Java icon and "Show Console" or "Open Console".
You should be able to see ISY messages in the Java Console.
Error Messages
System Errors
Number | Error | Message |
-1 | REQUEST_FAILED_ERROR | |
-2 | DEVICE COMMUNICATION ERROR | timed out waiting for the device to respond or got a NACK |
-3 | DEVICE RETURNED INVALID NODE | an address that we don't have in our nodemap |
-4 | DEVICE RETURNED INVALID ADDRESS | communication error |
-10 | UNEXPECTED DEVICE RESPONSE | |
-20 | MAIN LOCAL DEVICE BLANK | |
-500 | HAML DRIVER LISTENER NOT REGISTERED | the listener has not been registered |
-1000 | HAML PARSER UNDEFINED ELEMENT | |
-1001 | HAML PARSER ONDATA | |
-5001 | UPNP DRIVER NO DEVICES CONFIGURED | |
-5002 | UPNP DRIVER SERIAL READER FAILED | |
-5003 | UPNP DRIVER MAX DEVICES | |
-5004 | UPNP SERVICE TYPE SEARCH NS | we don't support service type search requests yet |
-5005 | UPNP SUBSCRIPTION NOT FOUND FOR RENEWAL | |
-5006 | UPNP SUBSCRIPTION NOT FOUND FOR CANCELATION | |
-5007 | UPNP INVALID SUBSCRIPTION URL | |
-5008 | UPNP INVALID SUBSCRIPTION CALLBACK | |
-5009 | UPNP MAX SUBSCRIBERS | |
-5010 | UPNP SUBSCRIBER TCP CONNECT FAILURE | tried to connect to the subscriber's ip/port but timed out |
-5011 | PROCESS DEVICE STATE CHANGE SID NOT FOUND | |
-5012 | UPNP SUBSCRIBER NOREPLY TO EVENT 1 | subscriber didn't reply to the event:couldn't write header |
-5013 | UPNP SUBSCRIBER NOREPLY TO EVENT 2 | subscriber didn't reply to the event:couldn't write body |
-5014 | UPNP SUBSCRIBER NOREPLY TO EVENT 3 | subscriber didn't reply to the event:read time out |
-5015 | UPNP CONTROL MALFORMED SOAP REQUEST 1 | missing body; we got a malformed control request |
-5016 | UPNP CONTROL MALFORMED SOAP REQUEST 2 | chopped off URL |
-5017 | UPNP_CONTROL_MALFORMED_SOAP_REQUEST_3 | missing node |
-6000 | OS DUPLICATE TASK PRIORITY | |
-6001 | OS OPEN SERIAL FAILED | |
-7000 | D2D SUBSCRIBE TCP CONNECT FAILURE | could not connect to the xternal device to subscribe to its events |
-7001 | D2D MAX REMOTE LISTENER THREADS | |
-7002 | D2D FACTORY FILE NOT FOUND | tried to use a static d2d file but it doesn't exist |
-7003 | D2D MALFORMED RULE MISSING SENSE TAG | the <Sense> tag is missing |
-7004 | D2D MALFORMED RULE MISSING SENSE ID ATTR | missing the id attribute in the sense tag |
-7005 | D2D MALFORMED RULE UNDEFINED TAG | missing the condition tag |
-7008 | D2D MALFORMED RULE MISSING RESPOND TAG | missing the <Respond> tag |
-7009 | D2D EVENT MISSING SOAP BODY | missing soap body for the received event |
-7010 | D2D UNKNOWN CONDITION OPERATION | operations could be either of =<or> |
-7011 | D2D EVENT MISSING PROPERTY TAG | missing <e:property tag in the received event |
-7012 | D2D SUBSCRIPTION REMOTE DEVICE NOT FOUND | tried to subscribe to the remote device but couldn't find it |
-7013 | D2D SUBSCRIPTION FAILED NO REPLY | although made a connection but the device didn't reply back |
-7014 | D2D SUBSCRIPTION FAILED NO SID RETURNED | subscribed to the external device but it didn't return an sid |
-7015 | D2D DESCRIPTION MALFORMED URL | the url to the device is malformed |
-7016 | D2D UNSUBSCRIPTION FAILED NO REPLY | tried unsubscribing but no reply from the device |
-7017 | D2D REQUEST FAILED NO ACTION | a request was sent but it didn't have an action |
-7018 | D2D CONDITION CHECK FAILED NO ACTION | |
-7019 | D2D PARSER ERROR SENSE NOT FOUND | |
-7020 | D2D PARSER ERROR | |
-7021 | D2D FACTORY SUBSCRIBE URL FAILURE | couldn't open a socket connection to the d2d factory url |
-7022 | D2D FACTORY SUBSCRIBE NO REPLY | although subscribed to the factory default no reply was returned |
-7023 | D2D COMPRESSION FAILED | tried to compress the d2d rules but failed |
-7024 | D2D DECOMPRESS FAILED | tried to decompress the d2d rules but failed |
-7025 | D2D RETRIEVE INITIALIZE FAILED | after decompressing tried intializing the d2d but failed |
-7026 | NOTIFICATIONS DNS ERROR | |
-7027 | NOTIFICATIONS MAIL SERVER NOT SETUP | |
-7029 | NOTIFICATIONS MAIL TO ADDRESS REQUIRED | |
-7030 | NOTIFICATIONS SEND MAIL FAILED | |
-7050 | D2D EXPECTED D2D TAG | Expected D2D tag but got something different |
-7051 | D2D UNEXPECTED TAG IN SENSE | Found an unexpected tag in the XML stream |
-7052 | D2D UNEXPECTED TAG IN CONDITION | Found an unexpected tag in the XML stream |
-7053 | D2D UNEXPECTED TAG IN RESPOND | Found an unexpected tag in the XML stream |
-7501 | DIAG PARSER ERROR | Error in UPBDiagParser |
-7601 | LINK PARSER ERROR | Error in UPBLinkDevices |
-9000 | SYSTEM NOT INITIALIZED POST FAILED | system is not intialized yet while trying to post |
-9001 | SYSTEM NOT INITIALIZED PUBSUB FAILED | |
-10001 | RANDOM GEN START ERROR | |
-10002 | RANDOM GEN READY ERROR | |
-10003 | RANDOM GEN ADD ENTROPY ERROR | |
-10004 | CTR START ERROR | |
-10005 | CTR ENCRYPT ERROR | |
-10006 | CTR SET IV ERROR | |
-10007 | CTR DECRYPT ERROR | |
-10008 | RSA KEY GENERATION FAILED | |
-10009 | RSA PUBLIC KEY IMPORT FAILED | |
-10010 | RSA PRIVATE KEY IMPORT FAILED | |
-10011 | RSA REIMPORT KEYS FAILED | |
-10012 | RSA EXPORT PUBLIC KEY FAILED | |
-10013 | RSA EXPORT PRIVATE KEY FAILED | |
-10014 | RSA MODULUS CONVERSION TO CHAR FAILED | |
-10015 | RSA EXPONENT CONVERSION TO CHAR FAILED | |
-10016 | RSA MODULUS ENCODING TO BASE 64 FAILED | |
-10017 | RSA EXPONENT ENCODING TO BASE 64 FAILED | |
-10018 | LIFETIME SEQUENCE ENCODING TO BASE 64 FAILED | |
-10019 | SET SESSION BASE64 DECODE FAILED | |
-10020 | SET SESSION RSA DECRYPT FAILED | |
-10021 | SET SESSION KEY PARSER FAILED | |
-10022 | SET SESSION KEY UNSUPPORTED BULK ALGORITHM | |
-10023 | BULK KEY INITIALIZATION FAILED WRONG KEY LENGTH | the vector sent to initialize a bulk key is too long |
-10024 | BULK KEY INITIALIZATION FAILED WRONG IV LENGTH | |
-10025 | BULK KEY INITIALIZATION FAILED WRONG KEY IV LENGTH | |
-10028 | SET SESSION INVALID BULK KEY | |
-10029 | SET SESSION AES INIT FAILED | |
-10030 | SET SESSION AES DECRYPT FAILED | |
-10031 | SET SESSION CIPHER TEXT BASE64 DECODE FAILED | |
-10032 | SET SESSION CIPHER TEXT PARSER FAILED | |
-10033 | SET SESSION KEY UNSUPPORTED BULK ENC ALGORITHM | |
-10034 | SET SESSION KEY UNSUPPORTED SIGN ALGORITHM | |
-10035 | SET SESSION CIPHER TEXT ENC KEY TO DEVICE BASE64 DECODE FAILED | |
-10036 | SET SESSION CIPHER TEXT ENC KEY FROM DEVICE BASE64 DECODE FAILED | |
-10037 | SET SESSION CIPHER TEXT SIGN KEY TO DEVICE BASE64 DECODE FAILED | |
-10038 | SET SESSION CIPHER TEXT SIGN KEY FROM DEVICE BASE64 DECODE FAILED | |
-10039 | SET SESSION ENCRYPT KEY TO DEVICE ASSIGNMENT FAILED | |
-10040 | SET SESSION ENCRYPT KEY FROM DEVICE ASSIGNMENT FAILED | |
-10041 | SET SESSION SIGN KEY TO DEVICE ASSIGNMENT FAILED | |
-10042 | SET SESSION SIGN KEY FROM DEVICE ASSIGNMENT FAILED | |
-10043 | SET SESSION CIPHER TEXT BLANK ENC KEY TO DEVICE | |
-10044 | SET SESSION CIPHER TEXT BLANK ENC KEY FROM DEVICE | |
-10045 | SET SESSION CIPHER TEXT BLANK SIGN KEY TO DEVICE | |
-10046 | SET SESSION CIPHER TEXT BLANK SIGN KEY FROM DEVICE | |
-10047 | SET SESSION KEY MISSING CP RSA KEY | |
-10048 | SET SESSION CP RSA MOD BASE64 DECODE FAILED | |
-10049 | SET SESSION CP RSA EXP BASE64 DECODE FAILED | |
-10050 | SET SESSION CP RSA KEY INIT FAILED | |
-10051 | SET SESSION CP RSA MOD CREATION FAILED | |
-10052 | SET SESSION CP RSA EXP CREATION FAILED | |
-10053 | SET SESSION MISSING SIGNATURE | |
-10054 | SET SESSION SIGNATURE HASH FAILED | |
-10055 | SET SESSION MISSING SIGNATURE VALUE | |
-10056 | SET SESSION SIGNATURE VALUE BASE64 DECODE FAILED | |
-10057 | SET SESSION SIGNATURE VERIFICATION FAILED | |
-10058 | MISSING SEQUENCE BASE | |
-10059 | INVALID SEQUENCE BASE | |
-10060 | EXPIRE SESSION PARSE ERROR | |
-10061 | EXPIRE SESSION SESSION NOT FOUND | |
-10062 | VERIFY HMAC SIGNATURE VALUE BASE64 DECODE FAILED | |
-10063 | VERIFY HMAC MISSING SIGNATURE | |
-10064 | VERIFY HMAC PROCESS FAILED | |
-10065 | VERIFY HMAC SIGNATURE FAILED | |
-10066 | VERIFY UPNP SECURITY INFO INVALID SEQUENCE NUMBER | |
-10067 | DECRYPT AND EXECUTE SESSION DOES NOT EXIST | |
-10068 | DECRYPT AND EXECUTE MISSING REQUEST TAG | |
-10069 | DECRYPT AND EXECUTE MISSING IN IV | |
-10070 | DECRYPT AND EXECUTE BASE64 DECODE FAILED | |
-10071 | DECRYPT AND EXECUTE EXPIRED SESSION | |
-10072 | DECRYPT AND EXECUTE SET IV FAILED | |
-10073 | DECRYPT AND EXECUTE DECRYPTION FAILED | |
-10074 | DECRYPT AND EXECUTE IV BASE 64 DECODE FAILED | |
-10001 | SSL DECODING LENGTHS FAILED | |
-10002 | SSL DECODING PMOD FAILED | |
-10003 | SSL DECODING PEXP FAILED | |
-10004 | SSL DECODING PRI EXP FAILED | |
-10005 | SSL DECODING PRI P FAILED | |
-10006 | SSL DECODING PRI Q FAILED | |
-10007 | SSL DECODING PRI X1 FAILED | |
-10008 | SSL DECODING PRI X2 FAILED | |
-10009 | SSL DECODING PRI COEFF FAILED | |
-10010 | SSL DECODING CERT FAILED | |
-10011 | SSL REQUEST NOT AUTHENTICATED | |
-10012 | SSL NO SUCH SERVICE | A call was made to a service end point that does not exist |
-10026 | SECURE SESSION DOES NOT EXIST | a secure session was requested that does not exist |
-10027 | SECURE SESSIONS EXHAUSTED | no more secure sessions available |
-10100 | AUTHENTICATION UPNP SECURITY NOT VERIFIED | |
-10101 | AUTHENTICATION UNSUPPORTED UID LEN | |
-10102 | AUTHENTICATION UNSUPPORTED PWD LEN | |
-10103 | AUTHENTICATION USER ID DOES NOT EXIST | |
-10104 | AUTHENTICATION USER ID PWD NOT PRESENT | |
-10105 | AUTHENTICATION WRONG PASSWORD | |
-10106 | AUTHENTICATION FAILED | |
-10107 | COULD NOT DECODE THE AUTHETICATION HEADER | |
-11000 | SECURITY INITIALIZATION FAILED | |
-12000 | TIMED OUT WAITING FOR CRITICAL SECION | |
-12001 | ERROR LEAVING CRITICAL SECTION NOT OWNED | |
-12002 | BULK KEY ENCRYPTION FAILED CFB START | |
-12003 | BULK KEY ENCRYPTION FAILED ENCRYPT | |
-13000 | CONTENT LEN NOT EQUAL TO HEADER CONTENT LEN | |
-14001 | XML MALFORMED TAG | @05 |
-14002 | XML MALFORMED END TAG | @05 |
-14003 | XML NO START TAG | @05 |
-14004 | XML NO TAG NAME | @05 |
-14005 | XML START END NAME MISMATCH | @05 |
-14101 | UD_JSON_ERR_MAX_STRINGS_EXCEEDED | JSON Parsing Error (4.2.3+) |
-14102 | UD_JSON_ERR_MAX_NESTING_DEPTH_EXCEEDED | JSON Parsing Error (4.2.3+) |
-14103 | UD_JSON_ERR_UNEXPECTED_CLOSE_BRACKET | JSON Parsing Error (4.2.3+) |
-14104 | UD_JSON_MAX_TAG_AND_DATA_LENGTH_EXCEEDED | JSON Parsing Error (4.2.3+) |
-14105 | UD_JSON_ERR_UNEXPECTED_HEX4_LENGTH | JSON Parsing Error (4.2.3+) |
-14106 | UD_JSON_SUPPLIED_MAXLEN_TOO_LOW | JSON Parsing Error (4.2.3+) |
-14107 | UD_JSON_ERR_OBJECT_UNEXPECTED_CHAR | JSON Parsing Error (4.2.3+) |
-14108 | UD_JSON_ERR_OBJECT_NAME_UNEXPECTED_CHAR | JSON Parsing Error (4.2.3+) |
-14109 | UD_JSON_ERR_OBJECT_SEP_UNEXPECTED_CHAR | JSON Parsing Error (4.2.3+) |
-20000 | MALFORMED UPNP HEADERS | |
-30000 | COMPRESSION INIT FAILED | |
-40000 | SCHEDULE SAVE NODE INDEX NOT FOUND | |
-40001 | DECOMPRESS GLOBAL SCHEDULE FAILED | |
-40003 | DECOMPRESS NOTIFICATIONS CONFIGURATION FAILED | |
-50000 | MAIL SERVER CONNECT ERROR | |
-50001 | SMTP SERVER FAILURE | |
-50005 | MAIL SERVER CONNECT ERROR | |
-50006 | MAIL SERVER CONNECT ERROR | |
-50007 | MAIL SERVER NO HOST PARAM | |
-50008 | MAIL SERVER NO PORT PARAM | |
-50009 | MAIL SERVER NO PATH | */ |
-50010 | MAIL SERVER DNS ERROR | |
-50011 | MAIL MAX FROM LEN | |
-50012 | MAIL MAX SUBJECT LEN | |
-50013 | MAIL MAX TO LEN | |
-60000 | NTP CONFIG SERVER NO HOST PARAM | |
-60001 | NTP CONFIG SERVER ADDRESS RESOLUTION FAILED | |
-60002 | NTP CONFIG SERVER NO INTERVAL PARAM | |
-60004 | NTP SERVER ADDRESS RESOLUTION FAILED | |
-60006 | NTP SERVER NOT RESPONDING | |
-60007 | NTP SERVER CONNECT ERROR | |
-70000 | OUT OF MEMORY | |
-70001 | VECTOR MAX CAPCITY | |
-80000 | IGD FAILED PARSING DESCRIPTION URL | |
-80001 | IGD FAILED RETRIEVING DESCRIPTION FILE | |
-80002 | IGD FAILED RETRIEVING URL BASE | |
-80003 | IGD FAILED PARSING URL BASE | |
-80004 | IGD FAILED RETRIEVING WAN CONNECTION DEVICE | |
-80005 | IGD FAILED RETRIEVING CONTROL URL | |
-80006 | IGD FAILED PARSING CONTROL URL | |
-80007 | IGD FAILED RETRIEVING EXTERNAL IP | |
-80008 | IGD NO RESPONSE FROM GATEWAY | |
-80009 | IGD FAILED STRIPPING HTTP HEADERS | |
-80010 | IGD FAILED DELETING PORT FORWARD MAP | |
-80011 | IGD FAILED ADDING PORT FORWARD MAP | |
-80012 | IGD FAILED GETTING SPECIFIC ENTRY | |
-90001 | CRC INVALID ORDER | |
-90002 | CRC INVALID POLYNOM | |
-90003 | CRC INVALID CRC INIT | |
-90004 | CRC INVALID CRC XOR | |
-100000 | LOGGER DIRECTORY CREATION FAILED | |
-100001 | LOGGER SD IS NOT INSTALLED | |
-100002 | LOGGER LOG FILE OPEN FAILED | |
-100003 | LOGGER TEMP LOG FILE OPEN FAILED | |
-100004 | LOGGER MAKE ROOM LOG FILE OPEN FAILED | |
-100005 | LOGGER SEEK FREE LOG SIZE FAILED | |
-100006 | LOGGER SEEK END OF LINE FAILED | |
-100007 | LOGGER TEMP LOG FILE READ FAILED | |
-100008 | LOGGER TEMP LOG FILE WRITE FAILED | |
-110000 | FILE TO STRING OPEN FAILED | |
-110001 | FILE TO STRING MEM ALLOC FAILED | |
-110002 | SD DRIVE FORMAT FAILED 1 | format failed |
-110003 | SD DRIVE FORMAT FAILED 2 | couldn't write the config.ud file |
-110004 | SD DRIVE MOUNT FAILED 1 | mount after format failed |
-110005 | SD DRIVE MOUNT FAILED 2 | initial mount failed |
-110006 | SEND FILE OPEN FAILED | |
-110007 | SEND FILE READ FAILED | |
-110008 | RECEIVE FILE WRITE FAILED | |
-110009 | RECEIVE FILE OPEN FAILED | |
-110010 | SD DRIVE DIRECTORY CREATION FAILED | |
-110011 | SD DRIVE CONFIG FILE OPEN WRITE FAILED | |
-110012 | SD DRIVE CONFIG FILE OPEN READ FAILED | |
-110013 | SD DRIVE CONFIG WRITE FAILED | |
-110014 | SD DRIVE CONFIG READ FAILED | |
-110015 | STRING TO FILE OPEN FAILED | |
-110016 | STRING TO FILE WRITE FAILED | |
-110017 | FILE TO STRING READ FAILED | |
-110018 | REMOVE FILE FAILED | |
-110019 | REMOVE DIR FAILED | |
-110020 | FLUSH FILE FAILED | |
-110021 | CLOSE FILE FAILED | |
-110022 | OPEN FILE FAILED | |
-110023 | FLUSH FILE SYSTEM FAILED | |
-110024 | FILESYSTEM_INIT_FAILED | |
-120000 | FIRMWARE UPDATE OPEN FILE FAILED | |
-120001 | FIRMWARE UPDATE HEADER READ FAILED | |
-120002 | FIRMWARE UPDATE CHECKSUM FAILED | |
-120003 | FIRMWARE UPDATE MALLOC FAILED | |
-120004 | FIRMWARE UPDATE DATA READ FAILED | |
-130000 | ELK CONFIG PARSER ERROR | |
-140000 | HTTP_CLIENT_DNS_ERROR | |
-140001 | HTTP_CLIENT_BASE64_ENCRYPTION_FAILED | |
-140002 | HTTP_CLIENT_CONNECTION_TIMED_OUT | |
-140003 | HTTP_CLIENT_WRITE_HEADER_FAILED | |
-140004 | HTTP_CLIENT_WRITE_BODY_FAILED | |
-140005 | HTTP_CLIENT_READ_RESPONSE_FAILED | |
-140006 | HTTP_CLIENT_HEADER_NO_STATUS | |
-140007 | HTTP_CLIENT_RESOURCE_MOVED | |
-140008 | HTTP_CLIENT_REQUEST_FAILED | |
-150000 | TCP_CLIENT_WRITE_FAILED | |
-150100 | UDP CLIENT DNS ERROR | |
-160000 | PROTOCOL_READER_READ_ERROR | |
-160001 | PROTOCOL_READER_BUFFER_OVERFLOW | |
-160002 | PROTOCOL_READER_REOPEN_ERROR | |
-170000 | WEB_MODULE_NO_FREE_SPACE | |
-200000 | DRIVER | |
-251001 | UZW_MSGCODE_COMM_RXU_IGNORED | Z-Wave: Unsupported unsolicited response message ignored |
-251002 | UZW_DATABASE_NOT_FOUND | Z-Wave: Database for device not found. Ignored |
-251003 | UZW_NOT_ACTIVE_ZWAVE_NODE | Z-Wave: Not an active Z-Wave node. Ignored |
-251004 | UZW_USER_SCHEDULE_NOT_ENABLED | Z-Wave: Schedule to wake up not enabled |
-251005 | UZW_USER_SCHEDULE_NOT_DISABLED | Z-Wave: Schedule to wake up not disabled |
-251006 | UZW_COMMAND_FAILED | Z-Wave: Command failed |
-251007 | UZW_CORRUPT_RX_MSG | Z-Wave: Corrupted message received |
-251008 | UZW_ATTEMPTED_TO_DELETE_DEFAULT_DB | Z-Wave: Debug info |
-271001 | PORTAL_SECURITY_INVALID_UUID_ERROR | Tried to register an ISY with the portal but invalid UUID was provided |
-271002 | PORTAL_SECURITY_INVALID_ACCOUNT_ID_ERROR | Tried to register an ISY with the portal but invalid portal account was provided |
-271003 | PORTAL_SECURITY_INVALID_KEY_ERROR | Tried to register an ISY with the portal but invalid portal key was provided |
-271004 | PORTAL_SECURITY_GENERATE_KEY_FAILED_ERROR | Failed generating a random portal key |
-271005 | PORTAL_SECURITY_INVALID_COMMAND_ERROR | Invalid portal command was provided |
-271006 | PORTAL_SECURITY_KEY_EXPIRED_ERROR | Portal authorization failed since the key expired |
-271007 | PORTAL_SECURITY_INVALID_KEY_LENGTH_ERROR | Tried to register an ISY with the portal but invalid key length was received |
-271008 | PORTAL_SECURITY_KEY_VALIDATION_FAILED_ERROR | Tried to register an ISY with the portal but validation failed |
-281001 | RTC_READ_ERROR | Failed reading the RTC |
-281002 | RTC_READ_ERROR_ADJUST_DST | Failed reading the RTC to adjust DST |
-281003 | RTC_READ_ERROR_INVALID_TIME | Read the RTC but got invalid time |
-281004 | RTC_READ_ERROR_NO_CRIT | Failed reading RTC due to not being able to get a crit |
-281005 | RTC_WRITE_ERROR | Failed writing/updating the time in RTC |
-281006 | RTC_WRITE_ERROR_NO_CRIT | Failed writing/updating the time in RTC due to not being able to get a crit |
-281007 | RTC_WRITE_ERROR_REFRESH | Failed writing/updating the time in RTC during refreshing system clock |
-281008 | RTC_SYNCH_ERROR | Failed synching system clock with RTC |
. | . | . |
Web Services/SOAP Errors
Number | Error | Message |
200 | SOAP OK | Request Succeeded |
401 | Invalid Action | The HTTP Action header (SOAPAction) is invalid |
402 | Invalid Arguments | |
403 | Forbidden | |
500 | Internal Error | |
501 | SOAP Action Failed | Could not process the request SOAP message |
600 | Invalid Argument Value | Was expecting a different value for the given argument |
601 | Argument Value Out of Range | |
602 | Not Implemented | Returned when given SOAP Request is not implemented |
603 | Out of Memory | ISY is out of memory and might require reboot |
604 | Human Intervention Required | |
605 | String Argument Is Too Long | |
609 | Not Encrypted | Not used in 2.6.1 and above |
612 | Invalid Session | Not used in 2.6.1 and above |
701 | Not Authorized | Credentials are either wrong or not provided |
711 | Signature Failed | Not used in 2.6.1 and above |
712 | Signature Missing | Not used in 2.6.1 and above |
714 | Invalid Sequence | Not used in 2.6.1 and above |
715 | Invalid Control URL | Control URL is the location where SOAP messages are Posted to |
721 | Algorithm Not Supported | Not used in 2.6.1 and above |
781 | No Such Session | The requested session does not exist |
801 | Exhausted Secure Sessions | No more sessions are available. In some cases, this may require reboot |
802 | Deivce Error | Could not communicate with a device |
803 | Is In Linking Mode | When ISY is in Linking mode, most other operations fail returning this code |
810 | Subscription: Incompatible Headers | Subscriptions require headers as defined in the developers guide |
811 | Subscirption: Missing Callback | Need CALLBACK: URL in the HTTP Header. <URL> could be <REUSE_SOCKET> |
812 | Invalid NT | Not used in 2.6.1 and above |
813 | Subscription: SID Not Found | The Subscription for the given SID does not exist |
814 | Subscription: Invalid Callback URL | If <REUSE_SOCKET> is not used, the URL is pointing to a destination that is not reachable |
815 | Subscription: MAX Subscribers Reached | You can no longer subscribe |
816 | Disclaimer not available | You may ignore this error |
817 | Subscription: Already subscribed | You are already subscribed and there's no need to subscribe again |
SMTP Errors
These email errors are enumerated in the Control field (column 2) and are related to Error -50001 (SMTP_SERVER_FAILURE).
Number | Error | Message |
-2 | NETWORK_ERROR | |
-5 | SMTP_CONNECT_FAILED | |
-6 | SMTP_SERVER_NOT_RESPONDING | |
-7 | SMTP_EHLO_TIMEOUT | |
-10 | SMTP_FROM_TIMEOUT | |
-11 | SMTP_TO_TIMEOUT | |
-12 | SMTP_DATA_TIMEOUT | |
-13 | SMTP_BODY_TIMEOUT | |
-14 | SMTP_AUTH_LOGIN_NOT_ACCEPTED | |
-15 | SMTP_USERID_NOT_ACCEPTED | |
-16 | SMTP_PASSWORD_NOT_ACCEPTED | |
-17 | SMTP_STARTTLS_NOT_ACCEPTED | |
-18 | SMTP_TLS_NEGOTIATIONS_FAILED | |
-19 | SMTP_WRITE_FAILED | |
-20 | SMTP_UNSUPPORTED_AUTH_METHOD |
Driver Errors
These sub errors are enumerated in the Control field (column 2) and are related to errors -200xxx.
Number | Error | Message |
-1 | Failed writing the highwater mark | |
-2 | Failed writing PLM slave link | |
-3 | Failed writing PLM master link | |
-4 | Failed reading device memory | |
-41 | Falied writing device memory | |
-5 | Failed reading device link | |
-51 | Failed writing device link | |
-6 | Failed restoring device from file | |
-7 | Failed initializing node - continuing | |
-8 | Node not added - failed reading links | |
-9 | Node not added - failed removing links | |
-10 | Node not added - failed restoring device | |
-11 | Replace device incomplete | |
-12 | Add device incomplete | |
-13 | Remove device incomplete | |
-14 | Add scene incomplete | |
-15 | Remove scene incomplete | |
-16 | Failed removing PLM master link | |
-17 | Failed removing PLM slave link | |
-18 | Failed removing group link | |
-19 | Failed adding device to scene | |
-20 | Adding device to scene incomplete | |
-21 | Removing device from scene incomplete | |
-22 | Replace failed: failed renaming file | |
-23 | Replace failed: address is null | |
-24 | Restore failed: internal error | |
-25 | Failed removing remaining links | |
-26 | Node already exists | |
-27 | Node does not exist | |
-28 | Incompatible device/firmware types | |
-29 | Failed to fully replace device | |
-30 | Failed resetting the PLM | |
-31 | Failed to fully restore device | |
. | . | . |