I am still having a similar problem as @randyth, the Network Resource works as expected in ISY994, but not on ISY on Polisy.  I'm on isy-5.2.0_58.

Error log:

Quote

Mon 1900/01/01 12:00:00 AM    System    -170001    <s:Envelope><s:Body><u:ResetReport xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:ResetReport></s:Body></s:Envelope>
Mon 2021/12/06 11:40:32 AM    0    -170001    <s:Envelope><s:Body><u:TestNetResource xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><id>1</id><flag>1</flag></u:TestNetResource></s:Body></s:Envelope>
Mon 2021/12/06 11:40:32 AM    0    -140008    Net Module Rule: 1:400
Mon 2021/12/06 11:40:32 AM    0    -170001    <s:Envelope><s:Body><u:GetLastError xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetLastError></s:Body></s:Envelope>
Mon 2021/12/06 11:40:32 AM    0    -170001    <s:Envelope><s:Body><u:ClearLastError xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:ClearLastError></s:Body></s:Envelope>

NR:

What am I missing?

I am still having a similar problem as@randyth, the Network Resource works as expected in ISY994, but not on ISY on Polisy.  I'm on isy-5.2.0_58.
Error log:

Mon 1900/01/01 12:00:00 AM    System    -170001    
Mon 2021/12/06 11:40:32 AM    0    -170001    11
Mon 2021/12/06 11:40:32 AM    0    -140008    Net Module Rule: 1:400
Mon 2021/12/06 11:40:32 AM    0    -170001    
Mon 2021/12/06 11:40:32 AM    0    -170001    

NR:

What am I missing?
If you did a restore from your ISY backup each NR needs to be loaded and saved again or it isn't linked into the system yet.

Sent from my SM-G781W using Tapatalk

1 minute ago, larryllix said:

If you did a restore from your ISY backup each NR needs to be loaded and saved again or it isn't linked into the system yet.

Sent from my SM-G781W using Tapatalk
 

No, it was manually entered in the AC for the ISY on Polisy.

28 minutes ago, glarsen said:

What am I missing?

Hmm, that all looks good to me.

Because I can't see the end of the body text, all I can think of is to make sure the accessCode is correct and perhaps run your JSON through a checker to test for typos.

45 minutes ago, randyth said:

Hmm, that all looks good to me.

Because I can't see the end of the body text, all I can think of is to make sure the accessCode is correct and perhaps run your JSON through a checker to test for typos.

Thanks.  I'll double check, but really I just copy and pasted from the other AC where the same code works.  And it works with curl.

Edited December 6, 20213 yr by glarsen

Fixed.  The clue was in the order of the headers.  For some reason the first one had host first, then POST.  Comparing it to the original and @Randyth's, they are reversed.  Created a new resource and started over, the POST was first and then host, and all works ok.  Don't have any idea why the first one was reversed.

 

Edited December 6, 20213 yr by glarsen