Jump to content

Can't control DSC from ISY

sorka

By sorka
in NodeLink

Recommended Posts

sorka Advanced

sorka

Posted
Posted

I kept getting a subscriber did not respond error when I tried to arm my dsc from partition1. I then enabled "repeater" on the nodelink dsc page and it started working.

 

Then I rebooted the ISY and it isn't working again. Same error. When I restart nodelink, the log looks fine:

 

2019-03-04 09:19:11 - ISY NodeLink Server v0.9.28 started
2019-03-04 09:19:11 - OS: Linux apnar-nodelink1 3.10.105 #23824 SMP Tue Dec 25 18:26:34 CST 2018 x86_64 GNU/Linux
2019-03-04 09:19:11 - Mono version: 5.16.0.179 (tarball Thu Oct  4 10:29:21 UTC 2018)
2019-03-04 09:19:11 - Web config server started (http://172.17.0.2:8090)
2019-03-04 09:19:12 - ISY resolved to 192.168.1.52 (5.0.14)
2019-03-04 09:19:12 - ISY Node Server config detected (profile 2)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Fireplace Remote)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Pendant A)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Pendant C)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Living Room Accent)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Front Garage)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Front Entry)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Pendant B)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Fireplace)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Dining Entry)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Pendant D)
2019-03-04 09:19:14 - ISY Warning: Duplicate node names exist on the ISY (Living Room Remote)
2019-03-04 09:19:15 - DSC: Repeater started on port 4025 [dsc1]
 

 

No amount of starting the ISY and nodelink seems to resolve the problem. Keep getting the same error. The log shows no activity when I press the arm butt on the partition1 device in ISY.

 

sorka Advanced

sorka

Posted
  • Author
Posted

When I set logging level for the DSC tab to debug, I get this every time I try to arm the partition:

 

2019-03-04 09:26:14 - DSC TCP: Polling DSC [dsc1]
2019-03-04 09:26:14 - DSC: 50000025[C][L] [dsc1]
2019-03-04 09:26:14 - DSC: 500 - Command Acknowledge (000) [dsc1]

sorka Advanced

sorka

Posted
  • Author
Posted

Restarting nodelink with full debug logging:

 

2019-03-04 10:10:36 - ISY NodeLink Server v0.9.28 started
2019-03-04 10:10:36 - OS: Linux apnar-nodelink1 3.10.105 #23824 SMP Tue Dec 25 18:26:34 CST 2018 x86_64 GNU/Linux
2019-03-04 10:10:36 - Mono version: 5.16.0.179 (tarball Thu Oct  4 10:29:21 UTC 2018)
2019-03-04 10:10:37 - Web config server started (http://172.17.0.2:8090)
2019-03-04 10:10:38 - ISY resolved to 192.168.1.52 (5.0.14)
2019-03-04 10:10:38 - ISY Node Server config detected (profile 2)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Fireplace Remote)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Pendant A)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Pendant C)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Living Room Accent)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Front Garage)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Front Entry)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Pendant B)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Fireplace)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Dining Entry)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Pendant D)
2019-03-04 10:10:39 - ISY Warning: Duplicate node names exist on the ISY (Living Room Remote)
2019-03-04 10:10:40 - DSC: Repeater started on port 4025 [dsc1]
2019-03-04 10:10:40 - DSC: Connected to 192.168.1.134 [dsc1]
2019-03-04 10:10:40 - DSC: 5053CD[C][L] [dsc1]
2019-03-04 10:10:40 - DSC: 505 - Login Interaction (Password Requested) [dsc1]
2019-03-04 10:10:40 - DSC: EVL User Login - Password Sent [dsc1]
2019-03-04 10:10:40 - DSC: 5000052A[C][L]5051CB[C][L] [dsc1]
2019-03-04 10:10:40 - DSC: 500 - Command Acknowledge (005) [dsc1]
2019-03-04 10:10:40 - DSC: 505 - Login Interaction (Password Correct, Session Established) [dsc1]
2019-03-04 10:10:40 - DSC: Status Request Sent [dsc1]
2019-03-04 10:10:40 - DSC: Data Sent - 00191 [dsc1]
2019-03-04 10:10:40 - DSC TCP: Polling DSC [dsc1]
2019-03-04 10:10:40 - DSC: 50000126[C][L]61000128[C][L]61000229[C][L]6100032A[C][L]6100042B[C][L]6100052C[C][L]6100062D[C][L]6100072E[C][L]6100082F[C][L]61000930[C][L]61001028[C][L]61001129[C][L]6100122A[C][L]6100132B[C][L]6100142C[C][L]6100152D[C][L]6100162E[C][L]60901737[C][L]60901838[C][L]60901939[C][L]60902031[C][L]60902132[C][L]6100222B[C][L]6100232C[C][L] [dsc1]
2019-03-04 10:10:40 - DSC: 500 - Command Acknowledge (001) [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 001) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 1 (DSC Front Door)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 002) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 2 (DSC Side Door House)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 003) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 3 (DSC Rear Garage Door)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 004) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 4 (DSC Office Half Bath Window)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 005) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 5 (DSC Kitchen Window East)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 006) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 6 (DSC Breakfast Nook Windows)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 007) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 7 (DSC Motion Hall)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 008) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 8 (DSC Motion Living Room)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 009) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 9 (DSC Sidedoor Garage)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 010) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 10 (DSC Living Room Doors Windows)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 011) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 11 (DSC Dining Room Windows)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 012) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 12 (DSC Piano Room Windows)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 013) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 13 (Bed 1)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 014) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 14 (Bed 2)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 015) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 15 (Bed 3)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 016) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 16 (DSC Master Bedroom Door Windo)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 609 - Zone Open (Zone 017) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 17 (Zone 17)  Opened [dsc1]
2019-03-04 10:10:40 - DSC: 609 - Zone Open (Zone 018) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 18 (Zone 18)  Opened [dsc1]
2019-03-04 10:10:40 - DSC: 609 - Zone Open (Zone 019) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 19 (Zone 19)  Opened [dsc1]
2019-03-04 10:10:40 - DSC: 609 - Zone Open (Zone 020) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 20 (Zone 20)  Opened [dsc1]
2019-03-04 10:10:40 - DSC: 609 - Zone Open (Zone 021) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 21 (Zone 21)  Opened [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 022) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 22 (DSC Motion Garage)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 610 - Zone Restored (Zone 023) [dsc1]
2019-03-04 10:10:40 - DSC: Zone 23 (Zone 23)  Closed [dsc1]
2019-03-04 10:10:40 - DSC: 50000025[C][L] [dsc1]
2019-03-04 10:10:40 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-03-04 10:10:41 - DSC: 6100242D[C][L]6100252E[C][L]6100262F[C][L]61002730[C][L]61002831[C][L]61002932[C][L]6100302A[C][L]6100312B[C][L]6100322C[C][L]6100332D[C][L]6100342E[C][L]6100352F[C][L]61003630[C][L]61003731[C][L]61003832[C][L]61003933[C][L]6100402B[C][L]6100412C[C][L]6100422D[C][L]6100432E[C][L]6100442F[C][L]61004530[C][L]61004631[C][L]61004732[C][L] [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 024) [dsc1]
2019-03-04 10:10:41 - DSC: Zone 24 (Zone 24)  Closed [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 025) [dsc1]
2019-03-04 10:10:41 - DSC: Zone 25 (Zone 25)  Closed [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 026) [dsc1]
2019-03-04 10:10:41 - DSC: Zone 26 (Zone 26)  Closed [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 027) [dsc1]
2019-03-04 10:10:41 - DSC: Zone 27 (Zone 27)  Closed [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 028) [dsc1]
2019-03-04 10:10:41 - DSC: Zone 28 (Zone 28)  Closed [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 029) [dsc1]
2019-03-04 10:10:41 - DSC: Zone 29 (Zone 29)  Closed [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 030) [dsc1]
2019-03-04 10:10:41 - DSC: Zone 30 (Zone 30)  Closed [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 031) [dsc1]
2019-03-04 10:10:41 - DSC: Zone 31 (Zone 31)  Closed [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 032) [dsc1]
2019-03-04 10:10:41 - DSC: Zone 32 (Zone 32)  Closed [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 033) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 034) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 035) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 036) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 037) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 038) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 039) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 040) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 041) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 042) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 043) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 044) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 045) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 046) [dsc1]
2019-03-04 10:10:41 - DSC: 610 - Zone Restored (Zone 047) [dsc1]
2019-03-04 10:10:42 - DSC: 61004833[C][L]61004934[C][L]6100502C[C][L]6100512D[C][L]6100522E[C][L]6100532F[C][L]61005430[C][L]61005531[C][L]61005632[C][L]61005733[C][L]61005834[C][L]61005935[C][L]6100602D[C][L]6100612E[C][L]6100622F[C][L]61006330[C][L]61006431[C][L]6531CF[C][L]6732D2[C][L]6733D3[C][L]6734D4[C][L]8411CE[C][L]8412CF[C][L]8413D0[C][L]8414D1[C][L]8415D2[C][L] [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 048) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 049) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 050) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 051) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 052) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 053) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 054) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 055) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 056) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 057) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 058) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 059) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 060) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 061) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 062) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 063) [dsc1]
2019-03-04 10:10:42 - DSC: 610 - Zone Restored (Zone 064) [dsc1]
2019-03-04 10:10:42 - DSC: 653 - Partition in Ready to Force Arm (Partition 1) [dsc1]
2019-03-04 10:10:42 - DSC: 673 - Partition Busy (Partition 2) [dsc1]
2019-03-04 10:10:42 - DSC: 673 - Partition Busy (Partition 3) [dsc1]
2019-03-04 10:10:42 - DSC: 673 - Partition Busy (Partition 4) [dsc1]
2019-03-04 10:10:42 - DSC: 841 - Trouble Status Restore (LED OFF) (Partition 1) [dsc1]
2019-03-04 10:10:42 - DSC: Panel OK [dsc1]
2019-03-04 10:10:42 - DSC: 841 - Trouble Status Restore (LED OFF) (Partition 2) [dsc1]
2019-03-04 10:10:42 - DSC: 841 - Trouble Status Restore (LED OFF) (Partition 3) [dsc1]
2019-03-04 10:10:42 - DSC: 841 - Trouble Status Restore (LED OFF) (Partition 4) [dsc1]
2019-03-04 10:10:42 - DSC: 841 - Trouble Status Restore (LED OFF) (Partition 5) [dsc1]
2019-03-04 10:10:42 - DSC: 8416D3[C][L]8417D4[C][L]8418D5[C][L]51081FF[C][L] [dsc1]
2019-03-04 10:10:42 - DSC: 841 - Trouble Status Restore (LED OFF) (Partition 6) [dsc1]
2019-03-04 10:10:42 - DSC: 841 - Trouble Status Restore (LED OFF) (Partition 7) [dsc1]
2019-03-04 10:10:42 - DSC: 841 - Trouble Status Restore (LED OFF) (Partition 8) [dsc1]
2019-03-04 10:10:42 - DSC: 510 - Full LED Status Update [dsc1]
 

sorka Advanced

sorka

Posted
  • Author
Posted

I occasionally got this error:

2019-03-04 09:01:07 - ISY Error: Connection refused (ns/2/nodes/n002_dsc1/report/status/GV11/1/25)

But didn't after the last reboot. So the current instance of the running nodelink did not show this error but when I click arm away or arm stay on partition1, the activity box pops up saying it's talking to GV11 so I think it's related. 

sorka Advanced

sorka

Posted
  • Author
Posted

Logging window is confusing. I had debug selected but under the system config tab on nodelink, only info was selected, so I changed it to debug and tried again. Now when I try to arm the partition, I get:

 

2019-03-04 11:55:39 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="false"><status>405</status></RestResponse> (climate)
2019-03-04 11:55:39 - DSC TCP: Polling DSC [dsc1]
2019-03-04 11:55:39 - DSC: 50000025[C][L] [dsc1]
2019-03-04 11:55:39 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-03-04 11:55:40 - ISY Send: Variable dsc1-GV11 added to queue (Val: 1, QS: 1)
2019-03-04 11:55:40 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/2/nodes/n002_dsc1/report/status/GV11/1/25)
2019-03-04 11:56:09 - ISY Send: Variable dsc1-GV11 added to queue (Val: -1, QS: 1)
2019-03-04 11:56:10 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/2/nodes/n002_dsc1/report/status/GV11/-1/25)
2019-03-04 11:56:34 - Web Request: /config.htm
2019-03-04 11:56:34 - Web Request: /index.htm

io_guy Advanced

io_guy

Posted
Posted

You're not receiving the arm request from the ISY.  Verify the address and port you have entered in the ISY's node config.  

sorka Advanced

sorka

Posted
  • Author
Posted

Do you mean this? It ip address and port match the logs. Wouldn't I not be getting status from nodelink if this wasn't configured correctly?

isylinkconfig.JPG.4754eada67294db1c75c583b465bc74c.JPG

sorka Advanced

sorka

Posted
  • Author
Posted

It's receiving something from the ISY, this happens in nodelink's logs whenever I press the arm button on ISY:

 

2019-03-04 14:43:40 - ISY Send: Variable dsc1-GV11 added to queue (Val: 1, QS: 1)
2019-03-04 14:43:41 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/2/nodes/n002_dsc1/report/status/GV11/1/25)
2019-03-04 14:44:10 - ISY Send: Variable dsc1-GV11 added to queue (Val: -1, QS: 1)
2019-03-04 14:44:11 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/2/nodes/n002_dsc1/report/status/GV11/-1/25)
2019-03-04 14:44:40 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="false"><status>405</status></RestResponse> (climate)
2019-03-04 14:44:40 - DSC TCP: Polling DSC [dsc1]
2019-03-04 14:44:40 - DSC: 50000025[C][L] [dsc1]
2019-03-04 14:44:40 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-03-04 14:44:40 - ISY Send: Variable dsc1-GV11 added to queue (Val: 1, QS: 1)
2019-03-04 14:44:41 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/2/nodes/n002_dsc1/report/status/GV11/1/25)
2019-03-04 14:44:54 - Web Request: /config.htm
2019-03-04 14:44:55 - Web Request: /index.htm

sorka Advanced

sorka

Posted
  • Author
Posted

Not sure if this is a clue, but the first time I try the arm button after an ISY reboot, I get this strange z-wave error. I don't have any z-wave devices.

 

StrangeZWaveError.JPG.34b86c03346d0c8939ac61139c28a662.JPG

gzahar Advanced

gzahar

Posted
Posted
Do you mean this? It ip address and port match the logs. Wouldn't I not be getting status from nodelink if this wasn't configured correctly?

isylinkconfig.JPG.4754eada67294db1c75c583b465bc74c.JPG

I think he means on the NodeLink webpage. The System Config tab.

But maybe not?

 

Sent from my iPhone using Tapatalk

sorka Advanced

sorka

Posted
  • Author
Posted

There is just in case there's something on the nodelink side that can help debug it. Everything on the status side works fine. Zones, partitions, etc all show their state and status changes. Just not able to control dsc from ISY. 

I nuked the nodes and re-installed them. Re-installed the config pages from nodelink onto the ISY. Restarted both ISY and nodelink multiple times. 

Not sure what else to try. 

gzahar Advanced

gzahar

Posted
Posted

Are you running NodeLink in Docker?  I notice the 172.17 IP address.

I'm running in Docker, but using the 192.168 address of my NAS (in the ISY Node config along with the 8090 port) and it works fine.

(Even though the NodeLink startup log reports the 172.17 address.)

 

sorka Advanced

sorka

Posted
  • Author
Posted
44 minutes ago, gzahar said:

Are you running NodeLink in Docker?  I notice the 172.17 IP address.

I'm running in Docker, but using the 192.168 address of my NAS (in the ISY Node config along with the 8090 port) and it works fine.

(Even though the NodeLink startup log reports the 172.17 address.)

Yes. Running on my Synology. Keep in mind that this wasn't working this morning before I clicked "Enable repeater function". Right after I did that, it started working fine. Is this required to control the DSC from the ISY? 

After that, I was trying to figure out what node to use to send virtual key presses so I could do things like bypass zones. I clicked on "install isy nodes" from the dsc tab on the nodelink config page figuring that maybe enabling repeater would add more nodes. This of course is wrong and I later realized the only way I'm going to send keypresses is with a network resource formatted correctly with a checksum on the end. 

I then rebooted the ISY after re-installing the ISY nodes. After that, partition control has failed every time since. 

I'll try changing the IP server address of nodelink to 192.168.x.x and see if that makes a difference.

Willing to try anything at this point.

 

gzahar Advanced

gzahar

Posted
Posted

I have no idea what the repeater function is.  I don't have it enabled.

You might try turning it off once you change the IP address in the ISY.

It would make sense that communications from ISY to NodeLink/Synology doesn't work with a different subnet being used.

sorka Advanced

sorka

Posted
  • Author
Posted

OK, fixed. I changed the node config on the ISY to use the IP address of the synology rather than the bridged address of the docker container. It would be nice if the instructions were fixed in the "devices" tab of the nodelink config UI where it says "likely 172.17.0.2" when if you're running docker on a nas with the default NAT bridged translation, it will NEVER be that address. I realize that most people are installing on devices without using docker like on an RPI so "likely" will I guess be likely.

I probably would have tried this long before now had it not actually been working this morning for a good hour or so.

 

So gzahar, you win the price for figuring it out. Thanks :)

io_guy Advanced

io_guy

Posted
Posted

There's a docker post and a few repos for NodeLink.  Also use net=host.

It has nothing to do with the repeater. The repeater is used for other DSC apps to connect since the EVL only allows a single socket connection.  

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Recently Browsing

    • No registered users viewing this page.

  • Who's Online (See full list)

    • There are no registered users currently online

  • Forum Statistics

    • Total Topics
      37.1k
    • Total Posts
      371.6k
×
×
  • Create New...