rahnee Posted February 21, 2017 Posted February 21, 2017 Hoping you can help me out on this one. Setup Nodelink on the same RPI that I have DSCLink running on. Turned OFF the Relay Server on DSCLINK and turned it ON for NODELINK. Configured Nodelink to use 2402 (like DSCLink had so I don't have to reconfig all the network resources). Turned repeater mode on so I can connect my DSCLink to NodeServer as to support the production ISY and allow me to play with the v5 Test ISY. When sending Relay commands via Nodelink I get "NOK" response. Simply switching back to DSCLink relay server (reconfig and reboot both DSCLink and Nodelink) the commands work without an issue. Is there an issue with Relay Server or is there a different configuration that I should be using. Repeater Function Issue: I just need to utilize the same Envisalink connection thus using Repeater Mode. Repeater mode ONLY works if it is on Nodelink and have DSCLink connect to it, if I turn it on for DSCLink, Nodelink cannot get the DSC Panel data. Help would be appreciated.
io_guy Posted February 21, 2017 Posted February 21, 2017 The relay server is no longer connected to the DSC features in NodeLink. It is only used for the specific items called out in the relay config tab. Any commands you want to relay to the DSC should be sent to the repeater port, not relay.
rahnee Posted February 21, 2017 Author Posted February 21, 2017 What about repeater? Why can nodelink not connect to the repeater from dsclink? Sent from my iPhone using Tapatalk
bgrubb1 Posted February 21, 2017 Posted February 21, 2017 I believe to make this same setup work I had to change the dsclink setup to use address 172.0.0.1 To capture the relay packets the dsc ip controller only allows one active connection
rahnee Posted February 21, 2017 Author Posted February 21, 2017 I believe to make this same setup work I had to change the dsclink setup to use address 172.0.0.1 To capture the relay packets the dsc ip controller only allows one active connection Correct, I was able to get DSCLink working by configuring it to 127.0.0.1 and NodeLink was the repeater. The relay server is no longer connected to the DSC features in NodeLink. It is only used for the specific items called out in the relay config tab. Any commands you want to relay to the DSC should be sent to the repeater port, not relay. What I would like to do is use the repeater function on DSCLink (aka legacy) and have Nodelink connect to it. This does not seem to work, only the other way around with Nodelink as repeater. Am I configuring something wrong?
rahnee Posted February 21, 2017 Author Posted February 21, 2017 The relay server is no longer connected to the DSC features in NodeLink. It is only used for the specific items called out in the relay config tab. Any commands you want to relay to the DSC should be sent to the repeater port, not relay. IO_GUY, I modified my network resources to point to the repeater port on Nodelink port 4025 and when I do that, I get "50196" as the response. Is it still TCP or is it a different setup now?
io_guy Posted February 21, 2017 Posted February 21, 2017 There are no relay commands for NodeLink, that's the point of V5. The old relay commands are integrated into the ISY itself: Sending to the repeater passes whatever you send directly to the alarm. Any response comes directly from the alarm.
rahnee Posted February 21, 2017 Author Posted February 21, 2017 There are no relay commands for NodeLink, that's the point of V5. The old relay commands are integrated into the ISY itself: stayarm.JPG Sending to the repeater passes whatever you send directly to the alarm. Any response comes directly from the alarm. Duh, makes sense. I am trying to have a hybrid setup of v4 and v5 at the same time. Was trying to utilize Nodeserver as a repeater for v4....which will never work. I will keep DSCLink relay server on so I can access the Panel and use v5 "directly". This is exactly why I am running a second unit to get used to v5. Thanks again!
rahnee Posted February 22, 2017 Author Posted February 22, 2017 IO_GUY, One more strange item. If using the Master code (UserID 40) to disarm the DSC Panel the Disarming User is updated to 32. This is incorrect, it should be 40. (and is reported that way on connect2go / envisalink directly). UserID 32 is a valid userID which is different from Master. Valid userIDs are 01-39 and 41-95. Thanks again
danbutter Posted February 24, 2017 Posted February 24, 2017 I was never able to get the repeater for dsc working on nodelink when using dsckeypad for android. Not really sure why as the configuration isn't different than what I ended up using. I ended up using dscserver.jar on a server I have running all the time. Works okay, but the time on the panel sometimes gets messed up and I have to take nodelink down before I can correct it. Otherwise all works as expected.
io_guy Posted February 24, 2017 Posted February 24, 2017 IO_GUY, One more strange item. If using the Master code (UserID 40) to disarm the DSC Panel the Disarming User is updated to 32. This is incorrect, it should be 40. (and is reported that way on connect2go / envisalink directly). UserID 32 is a valid userID which is different from Master. Valid userIDs are 01-39 and 41-95. Thanks again Send me a verbose log of the data received from the alarm.
rahnee Posted February 24, 2017 Author Posted February 24, 2017 Send me a verbose log of the data received from the alarm. Here are the logs and some screenshots. You will see that DSCLink webpage shows 40 and Nodelink webpage shows that it is user 0040. However both show 0040 in the raw data from the panel. edit: Added additional screenshots from webpages.
io_guy Posted February 25, 2017 Posted February 25, 2017 Fixed in the next version. For some reason V5 likes to consider 0040 as the number 32. I need to ditch the leading zeros. Gotta love V5.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.