io_guy Posted June 6, 2019 Posted June 6, 2019 Yes. Or just enter the first 6 characters in NodeLink. DSCLink used to just take the first 6 characters and send (that's all the EVL3 cared about). NodeLink supports the EVL4 as well so it will try to send the full 9 (and fail).
hum099 Posted June 6, 2019 Author Posted June 6, 2019 io_guy Thank you very much for your time and expertise, much appreciated. Everything seems to be working now.
hum099 Posted July 12, 2019 Author Posted July 12, 2019 I needed to go into the logs on the isy for something else and noticed these entries in the log. There are literally thousands of them. Is this normal. sample below DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:15:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:15:33 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:15:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:16:04 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:16:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:16:34 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:16:56 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:17:04 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:17:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:17:35 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:17:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:18:05 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:18:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:18:35 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:18:56 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:19:06 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:19:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:19:36 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:19:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:20:06 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:20:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:20:37 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:20:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:21:07 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:21:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:21:38 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:21:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:22:08 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:22:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:22:38 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:22:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:23:09 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:23:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:23:39 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:23:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:24:09 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:24:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:24:40 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:24:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:25:10 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:25:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:25:40 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:25:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:26:11 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:26:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:26:41 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:26:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:27:11 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:27:25 PM System Log RainMachine Custom Control 1 -1 Thu 2019/07/11 05:27:42 PM System Log DSC Alarm Custom Control 11 1 Thu 2019/07/11 05:27:55 PM System Log RainMachine Custom Control 1 1 Thu 2019/07/11 05:28:12 PM System Log DSC Alarm Custom Control 11 -1 Thu 2019/07/11 05:28:25 PM System Log
tmorse305 Posted October 31, 2019 Posted October 31, 2019 I am having the same Envisalink 3 password issue that others have reported. I tried entering just the first 6 characters in the password field but that didn't help. I then reduced the password to just 6 characters but still no luck. Here is the error as reported. The disarm password is the 4 digit code right? Just making sure. If that is wrong would it generate this error? There are also some ISY errors reported, are those related? Thanks io_guy 2019-10-31 16:47:19 - ISY NodeLink Server v0.10.1 started 2019-10-31 16:47:19 - OS: Linux raspberrypi 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux 2019-10-31 16:47:19 - Web config server started (http://192.168.1.xxx:8090) 2019-10-31 16:47:19 - ISY resolved to 192.168.1.xxx (5.0.15A) 2019-10-31 16:47:19 - ISY Error: Received an invalid status line: 'POST reuse HTTP/1.1'. (profiles/ns/0/connection) 2019-10-31 16:47:19 - ISY Error: Error getting Node Server list - Root element is missing. 2019-10-31 16:47:19 - ISY Node Server profile set to 1 2019-10-31 16:47:21 - ISY Error: Received an invalid status line: 'POST reuse HTTP/1.1'. (profiles/family/10/profile/1/download/EDITOR/I_EDIT.XML) 2019-10-31 16:47:22 - Warning: Node definitions need updating in ISY, see NodeLink's Devices page 2019-10-31 16:47:22 - DSC: EVL User Login - Password Incorrect [dsc1] 2019-10-31 16:47:23 - Relay Server: Started on port 2405
io_guy Posted October 31, 2019 Posted October 31, 2019 Yep there's a new bug that the password can't be set. I'm releasing an update to fix it tonight.
tmorse305 Posted October 31, 2019 Posted October 31, 2019 How do I force the upgrade? Normally I just let Nodelink check in the middle of the night. Rerun the install script or is there another script for that. Thanks.
io_guy Posted November 1, 2019 Posted November 1, 2019 If you restart NodeLink it'll check on startup (assuming you have auto-update enabled). I also added a check button to 0.10.3 (not released yet).
tmorse305 Posted November 1, 2019 Posted November 1, 2019 I do have a uto update set, but a restart doesn't not change the rev from 0.10.1 to 0.10.2
io_guy Posted November 1, 2019 Posted November 1, 2019 Then just manually download it, or delete the file and re-run the install script. Should be an error in your log if it's not connecting to the update server properly.
tmorse305 Posted November 1, 2019 Posted November 1, 2019 I deleted the file and re-ran the script. 0.10.2 is now running and the password is accepted. DSC nodes appear in the ISY and are tracking the actual zone activity. Thank you for fixing the password issue so quickly! One last problem. I cannot communicate with the DSC from ISY using network resources. I use Command Outputs 1 & 2 in my automation. I have the relay server enabled in Nodelink The port defaulted to 2405, I tried that without success, then I switched it to 2402 which was the setting in DSClink. Still no luck. The main web display shows that the relay port is starting successfully I couldn't find a error log file to check in the Node folder on my pi. What else can I check? Thanks.
io_guy Posted November 1, 2019 Posted November 1, 2019 Enable debug or information on the NodeLink "System Config" page and the log window. You should see a request coming from the ISY when you send the ISY resource.
tmorse305 Posted November 2, 2019 Posted November 2, 2019 I enabled debug, see screen shot of the log. The last 9 entries are the result of sending 3 different commands from ISY. The first was a status request, the 2nd was to Command Output 1 on, and the 3rd was Command Output 2 on. All 3 entries seem to be identical and if I'm reading it right it looks like DSC is acknowledging a command of 000, (500 000 25) in all cases. Using DSCLink I sent Command Output 2 from ISY. I can see DSC acknowledges the output command 020 in the 4th entry.
io_guy Posted November 2, 2019 Posted November 2, 2019 You didn't enable the debug on the System Config page, can't see what you're sending through the relay server.
tmorse305 Posted November 2, 2019 Posted November 2, 2019 Here it is with System Config on debug. I sent the Command Output 2 at 7:38 AM. Full log attached. Thank you io_guy. logfile_2019-11-02.txt
io_guy Posted November 2, 2019 Posted November 2, 2019 You're using the Relay Server, you should be using the repeater function on the DSC tab.
tmorse305 Posted November 2, 2019 Posted November 2, 2019 Thanks io_guy, I switched to the repeater and it is now working. I used the relay server in DSClink and just thought it would be the same for Nodelink. Thanks again for all of the troubleshooting help.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.