August 1, 20196 yr I just upgraded isy v4 to v5.0.15A. Previously used dsclink (in a docker container) without problem. Installed nodelink 0.9.34 (also in a docker container). Configured EnvisaLink OK, its nodes appear on isy but seem inactive. I think that is because I could not get "Install NodeDef Files" to work. Isy always repeats (3x) "ISY Error: REST Post Error: The server returned an invalid or unrecognized response." when button depressed. It does not appear to be an authentication issue and increasing logging to debug didn't shed any light. Any ideas?
August 2, 20196 yr I've read about similar issues elsewhere ... is this perhaps due to the version of mono that gets installed when one runs the Nodelink installation script (6.0.0.313)? Is the workaround to downgrade mono?
August 2, 20196 yr If you were to install the latest Raspbian or Debian (Buster), the install script takes the base repository mono version (5.XX) which would be fine. I haven't had time to install mono 6 to diagnose the problem.
August 2, 20196 yr Author Thanks everyone for your replies. The problem was using mono:latest as my base image (mono 6+). I switched to mono:5.20.1.34 and things seem to be working fine now (I just have to gain a little more experience with isy5/nodelink).
August 3, 20196 yr FWIW, I'm running NodeLink on the latest Mono release without issue. 2019-08-03 05:16:33 - ISY NodeLink Server v0.9.34 started 2019-08-03 05:16:33 - OS: Linux raspberrypi 4.19.57-v7+ #1244 SMP Thu Jul 4 18:45:25 BST 2019 armv7l GNU/Linux 2019-08-03 05:16:33 - Mono version: 6.0.0.313 (tarball Sun Jul 14 10:28:06 UTC 2019) 2019-08-03 05:16:33 - Web config server started (http://192.168.1.5:8090)
August 3, 20196 yr I am running NodeLink on v5.2xx no problems. The only problem I really had was trying to install mono 5.0.0 on a RPi1 about a year or two ago.. Some of the needed files did not exist on the RPi Raspbian install. NOOBS was notorious for missing all kinds of utilities. I switched up to a RPi 3 at that time and the same mono installed fine. That is not NodeLink's fault on that one though. 2019-07-28 16:53:10 - ISY NodeLink Server v0.9.33 started 2019-07-28 16:53:11 - OS: Linux rpi3 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux 2019-07-28 16:53:11 - Mono version: 5.20.1.19 (tarball Thu Apr 11 09:28:30 UTC 2019) 2019-07-28 16:53:12 - Web config server started (http://192.168.0.175:8090) 2019-07-28 16:53:13 - ISY resolved to 192.168.0.161 (5.0.15) 2019-07-28 16:53:13 - ISY Node Server config detected (profile 1)
Archived
This topic is now archived and is closed to further replies.