Not sure I am fighting a problem with updating NodeLink or if the problem lies with Honeywell api. Updated NodeLink to v0.9.34 this morning and noticed this in Nodelinks window:

2019-07-21 13:21:34 - ISY NodeLink Server v0.9.34 started
2019-07-21 13:21:34 - OS: Linux AutoMationPi 4.19.57-v7+ #1244 SMP Thu Jul 4 18:45:25 BST 2019 armv7l GNU/Linux
2019-07-21 13:21:34 - Mono version: 6.0.0.313 (tarball Sun Jul 14 10:28:06 UTC 2019)
2019-07-21 13:21:35 - Web config server started (http://192.168.0.164:8090)
2019-07-21 13:21:36 - ISY resolved to 192.168.0.165 (5.0.15A)
2019-07-21 13:21:37 - ISY Node Server config detected (profile 1)
2019-07-21 13:21:40 - Warning: Node definitions need updating in ISY, see NodeLink's Devices page
2019-07-21 13:21:40 - Relay Server: Started on port 2402
2019-07-21 13:21:43 - TCC Get StatusError: Redirect [hwstat1]
2019-07-21 13:26:44 - TCC Get StatusError: Redirect [hwstat1]
2019-07-21 13:30:03 - ISY Error: REST Post Error: The server returned an invalid or unrecognized response.
2019-07-21 13:30:03 - ISY Error: REST Post Error: The server returned an invalid or unrecognized response.
2019-07-21 13:30:03 - ISY Error: REST Post Error: The server returned an invalid or unrecognized response.

This is with debug set.

Question, if I "restored" ISY to an earlier time do the node definitions revert back to that earlier time also are does the ISY restore not change the defs?

 

Thanks,

Tim

Yea, the node defs are restored.  

I'm wondering if it's a mono 6 issue. Heard another poster say he had issues that we're fixed when he went back to mono 5.  

Yep, your right. I rolled back to before I did updates this morning, it likely is mono. I am back on v5.xx of mono and your latest Nodelink is working correctly.

Before, when I was on a pogoplug running arch it was easy to roll back a package or to specify not in upgrade a package. I have not found any info on doing the same on stretch pi3. Is there a way to specify not to upgrade or to roll back a package?

Hey all,

I thought I would try updating mono again to see if it had been fixed, July was the last time I had updated and it broke Honeywell in Nodelink. Just updated to the latest version of mono and am getting same errors as above so mono apparently has not been fixed.

Tim

I haven't looked into mono 6 much.  

.NET Core 3 gets released in a week so I plan on moving NodeLink over to it shortly after.  

For what it's worth, I'm running Mono 6 successfully.

2019-09-22 03:43:12 - ISY NodeLink Server v0.9.36 started
2019-09-22 03:43:12 - OS: Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
2019-09-22 03:43:12 - Mono version: 6.0.0.327 (tarball Thu Aug 29 21:49:40 UTC 2019)
2019-09-22 03:43:13 - Web config server started (http://192.168.1.5:8090)

Updated Mono to the latest/greatest.  Still runs.

2019-09-25 03:43:12 - ISY NodeLink Server v0.9.36 started
2019-09-25 03:43:12 - OS: Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
2019-09-25 03:43:12 - Mono version: 6.4.0.198 (tarball Tue Sep 24 01:57:00 UTC 2019)
2019-09-25 03:43:12 - Web config server started (http://192.168.1.5:8090)

 

Edited September 25, 20196 yr by Bumbershoot