Adam Ant Posted February 22, 2023 Posted February 22, 2023 HI Everyone, I am getting quite a few of these errors in my error log. The error messages wiki page says it is a VECTOR MAX CAPCITY error. Anyone know what causes these? Does that mean a function was expecting a different number of parameters? Anything to worry about? Wed 2023/02/22 02:10:05 PM 0 -170001 <s:Envelope><s:Body><u:Subscribe xmlns:u="urn:udi-com:service:X_Insteon_Lighting_Service:1"><reportURL>REUSE_SOCKET</reportURL><duration>infinite</duration></u:Subscribe></s:Body></s:Envelope>
TSinclair Posted February 23, 2023 Posted February 23, 2023 I'll be curious as well as I get several hundred "-170001" errors a day. 1
Solution Geddy Posted February 23, 2023 Solution Posted February 23, 2023 19 hours ago, Adam Ant said: -170001 In prior posts this was classified as an "information only" type error. Indicating that it is not a real error and could be ignored. I am not sure if this has changed in Polisy/eisy era, but feel that if things are working well then it continues to be information only and could be ignored. You reference a -70001 as Vector error, but you seem to have just left out the first "1" from the actual error code. I also get a lot of the -170001 "errors" and don't worry about it. Quote Thu 2023/02/23 07:49:19 AM System -170001 <s:Envelope><s:Body><u:DeviceSpecific xmlns:u="urn:udi-com:service:X_Insteon_Lighting_Service:1"><command>G_BT</command><node>45 7A E6 1</node><option></option><flag>0</flag><CDATA></CDATA></u:DeviceSpecific></s:Body></s:Envelope> Thu 2023/02/23 08:31:11 AM System -170001 <s:Envelope><s:Body><u:GetCurrentSystemStatus xmlns:u="urn:udi-com:service:X_Insteon_Lighting_Service:1"><SID>uuid:0</SID></u:GetCurrentSystemStatus></s:Body></s:Envelope> Thu 2023/02/23 09:31:10 AM System -170001 <s:Envelope><s:Body><u:GetCurrentSystemStatus xmlns:u="urn:udi-com:service:X_Insteon_Lighting_Service:1"><SID>uuid:0</SID></u:GetCurrentSystemStatus></s:Body></s:Envelope> And that's just a small section of the error log from this morning.
Adam Ant Posted February 23, 2023 Author Posted February 23, 2023 32 minutes ago, Geddy said: In prior posts this was classified as an "information only" type error. Indicating that it is not a real error and could be ignored. I am not sure if this has changed in Polisy/eisy era, but feel that if things are working well then it continues to be information only and could be ignored. You reference a -70001 as Vector error, but you seem to have just left out the first "1" from the actual error code. I also get a lot of the -170001 "errors" and don't worry about it. And that's just a small section of the error log from this morning. Thank you! Proves every 1 matters 1
Recommended Posts