Jump to content

NodeLink forgets ISY Password


biiiink

Recommended Posts

I seem to be having an issue with NodeLink and the ISY password field. 

I enter the password and click "Set" . Nodelink connects to the ISY and I can see the devices page, but after a minute or so, the Devices page shows "Not authorized - Please setup valid ISY password

When I go to the System Config page, i notice that the password is 1 character shorter than my password.  I re-enter the password and it will connect again but still disconnects after a min.

 

The only thing I see in the Web Display log is:

2018-04-24 14:17:08 - ISY Error: Login failure (verify ISY user/password on the system config page)
2018-04-24 14:17:38 - ISY Error: Login failure (verify ISY user/password on the system config page)
2018-04-24 14:18:09 - ISY Error: Login failure (verify ISY user/password on the system config page)
2018-04-24 14:18:12 - ISY Error: Login failure (verify ISY user/password on the system config page)
2018-04-24 14:18:39 - ISY Error: Login failure (verify ISY user/password on the system config page)
2018-04-24 14:19:09 - ISY Error: Login failure (verify ISY user/password on the system config page)

 

Any help would be appreciated

Link to comment
Share on other sites

  • 1 month later...
On 4/25/2018 at 6:14 AM, io_guy said:

Password "display" is always just 8 astericks. 

You havent mentioned your OS, mono version, whether this install is new...

It is installed on a Raspberry Pi, and Mono version is 5.12.0.226

Link to comment
Share on other sites

FWIW, I had a similar issue when upgrading to v0.9.15 of Nodelink.  After checking the auto-update box, the new version was downloaded and the Nodelink server restarted, coming back up in the new version.  I got the same error about invalid ISY password and my Nodelink devices were also missing (ISY data, Ecobee, Datalogger).  After trying to reset the password unsuccessfully, I removed the config.xml file and replaced it with the configbak.xml file.  This brought things back to normal.

My setup is a bit unconventional in that I'm running Nodelink in a Docker container on my NAS.  I thought it may have been due to that setup so I just wrote it off as a hiccup.  I'm a noob at using Docker so things remain a bit mysterious in that realm for me.

Link to comment
Share on other sites

This has happened to me in the past also. Somewhere in the Nodelink modifications it's algorithms detect it is a new installation, somehow and it starts over with a blank slate.

Try Toddimus' method above to get your original config.xml file back. My password and structure could be built from scratch no problem, but io_guy installed a backup file routine to save some work if and when this ever happened again.

Link to comment
Share on other sites

Didn't get a lot cause NodeLink writes a default to it on startup.  

Any chance you have the NodeLink log for the startup with the messed xml?   I'm guessing there should have been an xml error.  

Link to comment
Share on other sites

The xml file is a newly created one here each time. It only contains virgin setup info as it appears to overwrite the original config.xml

IIRC it happens at  the time of an ISY reboot after NodeLink version upgrade. I am thinking I manually rebooted ISY from NodeLink each time it happened..

Link to comment
Share on other sites

27 minutes ago, io_guy said:

OK, In the next version I've added auto-restore of a backup config (if it exists) when the start-up loading fails.

It seems to me that there is a scenario where NodeLink requests some info from ISY after a new version is installed for the ISY setup link.  If ISY doesn't answer (due to being rebooted) then NodeLink appears to make an assumption that this is a virgin installation and overwrites the good file. Looking for a good file may alleviate this but may complicate  new or messed up  installs.
There may be a cleaner way to work around this but you know the workings  better than anybody. :)

Link to comment
Share on other sites

  • 3 weeks later...

Just installed 5.0.12 last night and experienced this exact issue when trying to get Nodelink running on my Windows 7 server.  I was initially able to see the devices page and add DSC but when I would try to go to the DSC config page it would tell me my ISY wasn't authorized. I've been using DSClink successfully for quite awhile but I did turn it off before running Nodelink.  

Updating to add additional details:

Here's what I'm doing. First kill DSCLink so that it is not interfering. Run Nodelink.exe as admin. Enter credentials for ISY. Hit Set. Additional options then refresh and show up on System Config page. Go to Devices page (sometimes it won't even let me do this because it says I'm not authorized). Add DSC. Go to DSC page and get "Not Authorized - Please setup valid ISY password". If I try rebooting Nodelink, I have to start all over by entering password again on the system config page. I've tried deleting the config.xml and starting over but that didn't help. My DSCLink still works fine when I turn it back on it connects to both ISY and my DSC without issues. 

Link to comment
Share on other sites

2 hours ago, biiiink said:

Im still having this issue.  I just sent you my log file

Not sure what to say about that one.  You can successfully get the node list from the ISY, but it returns 401 errors every time you try to write a value.  Can you give me a full log - I'd like to see the successes and failure (and startup).

Link to comment
Share on other sites

Find the log file under the "node" directory on your RPi.

 I use Filezilla, an awesome and free file porting program running on my Win machines,  to port the file over to a Windows machine so I can paste it into the forum or PM it.

Link to comment
Share on other sites

1 hour ago, larryllix said:

Find the log file under the "node" directory on your RPi.

 I use Filezilla, an awesome and free file porting program running on my Win machines,  to port the file over to a Windows machine so I can paste it into the forum or PM it.

In an upcoming version I'm going to include a file server so the logs can be pulled from the web interface.  

 

Link to comment
Share on other sites

1 hour ago, io_guy said:

In an upcoming version I'm going to include a file server so the logs can be pulled from the web interface.  

 

Nice!

Where will they go? Sounds like a lot of work if you  have to install a folder/file browser for Win and iOS stuff ? 

EDIT: Ahhh.  this would be  pulled" from the client computer from the web interface server. In the "debug" setting, those files take 20-30 minutes to render on my Netbook Win Wordpad or text editor. Editing out a chunk takes about an hour to scroll top to bottom to select useless text out. :( The files cross-load fast enough but that is HDD targeted. I think the editing is bogged down by the memory limitations.

 

Link to comment
Share on other sites

Archived

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


×
×
  • Create New...