Can't update Nodedefs file

[johnnyt]

I had to downgrade ISY from 5.1 to 5.0.16C as there are too many zwave problems in 5.1.

Nodelink now consistently returns the message " - Warning: Node definitions need updating in ISY, see NodeLink's Devices page "

But every time I press "Install Nodedefs file" on the Devices page I get:

2020-08-25 16:44:03 - ISY Error: REST Post Error: Timeout
2020-08-25 16:44:03 - ISY Error: REST Post Error: The response ended prematurely.
2020-08-25 16:44:03 - ISY Error: REST Post Error: The response ended prematurely.

2020-08-25 16:44:14 - ISY Error: REST Post Error: Timeout
2020-08-25 16:44:15 - ISY Error: REST Post Error: The response ended prematurely.
2020-08-25 16:44:15 - ISY Error: REST Post Error: The response ended prematurely.

2020-08-25 16:44:47 - ISY Error: REST Post Error: The response ended prematurely.
2020-08-25 16:44:47 - ISY Error: REST Post Error: The response ended prematurely.
2020-08-25 16:44:47 - ISY Error: REST Post Error: The response ended prematurely.

Tried multiple times yesterday. Didn't get the Timeout message but got the other three each time I tried. I've restarted Nodelink several times and rebooted ISY a couple times hoping it might fix the problem. While I have seen this before, it usually worked after a couple tries and/or restart.

Anyone else run into this?

[io_guy]

Seems to be a an issue on Windows.  I had the same issue when trying out a new test version.  Once I moved it over to the Pi it worked fine.  Not sure if it's a Net Core issue, I haven't had time to play around.  

[johnnyt]

In 10.5 it would only do it once in a while but then work on retry. There's been some windows updates too. This morning I'm only getting one message (one try) when I try to update, whereas I used to get 3. Strange.

I saw that .net core had an update Aug 11 (3.1.7) so went ahead and installed that latest version but I still get the error, with only one attempt being made, Could this be related to other problem I reported that while I can stop nodelink from web page or ISY, it won't restart?

I see there's a .net 5.0 preview version. I might try running it with that version on another box to see if makes any difference.

 

[macjeff]

You have to manually send the node definitions using the ISY. 

but as far as downgrading the ISY.  I am surprised it worked.  I was able to go back but everything was totally messed up.  I talked to UDI and they said you cant go back so I went back to 5.1.

And as far as the z-wave issues, a lot of them are things you may have to work around since they are going for z-wave plus certification and a lot of stuff has to change.

I had to go to each device and redo the links.  Right click on the device.  there is no longer any heal zwave network option!!!

 

[johnnyt]

11 minutes ago, macjeff said:

You have to manually send the node definitions using the ISY. 

but as far as downgrading the ISY.  I am surprised it worked.  I was able to go back but everything was totally messed up.  I talked to UDI and they said you cant go back so I went back to 5.1.

And as far as the z-wave issues, a lot of them are things you may have to work around since they are going for z-wave plus certification and a lot of stuff has to change.

I had to go to each device and redo the links.  Right click on the device.  there is no longer any heal zwave network option!!!

 

if by "manually" you mean push the "Install NodeDefs file" on the devices page that's what I'm trying to do but if you mean something else, please let me know the steps.

as far as downgrade, it was a mess but it worked. I was told the following by support: "upgrade is the same procedure as downgrade, and yes if 5.0.16 works you should use it until we can fix the Z-Wave bugs. No reset is required for that firmware change, but make a backup just in case if you do not have one already."

The problem was that I had changed a bunch of stuff in 5.1 and added zwave devices so lost all of that. But I had to do it as eight of my zwave devices were unusable in programs and I could no longer change my thermostat in the admin console, among other things. 5.0.16 backup was 12 days old so I had to fix a lot of things. To fix the zwave differences I did a Synchronize Nodes, which seemed to work. Hopefully there aren't unfound gremlins now lurky... I've never has to roll back before. This was definitely unusual and I"m a little worried about what this zwave certifcation is going to mean.

[johnnyt]

I uninstalled .net core 3.1.7 and installed older 3.0.3 and, after three tries, the nodedefs file finally updated. I must have tried over 50 times without luck before doing the roll back...

 

 

[gzahar]

On 8/26/2020 at 12:00 PM, johnnyt said:

if by "manually" you mean push the "Install NodeDefs file" on the devices page that's what I'm trying to do but if you mean something else, please let me know the steps.

In version 0.10.6 of NodeLink, there is the following line on the devices page:

"If NodeLink is unable to send its configuration to the ISY, the nodedefs can be manually downloadedHERE"

If you click the "HERE" link, it will download your Nodedefs to a zip file.

Then go to ISY admin console, Node Servers menu and select 'Configure' and the slot your NodeLink is in (isylink).

At the bottom of the pop up window will be a button to upload profile.  Select this and the previous zip file you downloaded.

[gzahar]

On 8/25/2020 at 4:29 PM, io_guy said:

Seems to be a an issue on Windows.  I had the same issue when trying out a new test version.  Once I moved it over to the Pi it worked fine.  Not sure if it's a Net Core issue, I haven't had time to play around.  

I was getting the same "The response ended prematurely." error on a NAS running docker.  Not sure how that would be related to Windows, but not too educated on that subject.