Cannot Control WebControl8 from ISY via Nodelink

[richroed]

I have added a WebControl8 to my Nodelink server running on Windows.  It appears to have properly enumerated within the ISY, and the ISY receives status changes from the WebControl8.  Unfortunately when I try to control the WebControl8 outputs from the ISY, I receive a Request Failed error dialog on the ISY.

Can someone help me resolve this?

I do NOT have authentication active on Nodelink. 
I have set the the WebControl8 login to the default: admin/password.

Any help is greatly appreciated.

ISY-Events-Log.v5.0.9__Sun 2019.06.09 12.48.24 PM.txt

[io_guy]

If you don't see a message in NodeLink I suspect the commend isn't getting there from the ISY.  Enable debug on the "Main" log window and on the "System Config" pages of NodeLink.

When you try a command from ISY after that you should see the request in NodeLink.  Do you?

What happens when you try to set the WC8 from a web browser?:
http://address/api/setttloutput.cgi?output=1&state=1 for example

[richroed]

 

http://address/api/setttloutput.cgi?output=1&state=1 works fine - no problems at all turning on/off an output as confirmed by the WebControl8 Web UI.

Here is the Log, is the first ISY  Send/Receive the command sent by nodelink to the webcontrol?  Regardless, I still get the error during this test/capture.

The highlighted row is what I used as a marker to find new records in the debug log once I send the command from the ISY Admin UI.  I attempted to turn on Output 1.

R.

[io_guy]

The request is not getting through.  You'd see a web request log item for webcontrol mentioning a GV variable.  

Verify NodeLink config in ISY and any firewall issues.  

You mentioned you have DSC as well.  Send a DSC command from the ISY and you should see a web request in the log.  

The highlighted text is NodeLink setting the heartbeat in the ISY.  Not related.  

[richroed]

Thanks, it was the Windows 10 Firewall.  

I went into Windows 10 firewall Advanced Settings, created a New "Port" based Inbound Rule on TCP for port 8090 for all Profiles (Domain/Private/Public).  Screenshot attached.

Thanks again for your help with this, much appreciated.

R.