Settings Reset on upgrade to 0.8.5?\

[Scyto]

My pi had been down for a week or so (i had pulled the power and hadn't noticed).

 

I started it up the pi this morning, it upgraded itself but all the settings seems to have reset to default?

I will see if i have a backup file somwhere i can copy over... so FYI i guess?

 

2017-12-18 20:17:41 - ISY NodeLink Server v0.8.5 started

2017-12-18 20:17:42 - Mono version: 5.4.1.6 (tarball Wed Nov  8 22:23:23 UTC 2017)

2017-12-18 20:17:46 - No password specified for the ISY

2017-12-18 20:17:55 - ISY resolved to 

2017-12-18 20:17:55 - Web config server started (http://192.168.1.118:8090)

2017-12-18 20:17:55 - ISY Error: Error resolving hostname - ISY

2017-12-18 20:17:55 - ISY Error: Invalid URI: The hostname could not be parsed. (profiles/ns/0/connection)

2017-12-18 20:17:56 - ISY Error: Error getting Node Server list - Root element is missing.

2017-12-18 20:17:56 - ISY Node Server profile set to 

[Scyto]

i found a file from ealier in dec, on my pc, that restored settings.

does nodelink create a .bak file - i had one in the dir but it was from the summer, if not i guess i created it....

[io_guy]

Something crapped out, no idea why.

 

NodeLink doesn't create a backup file. I'll add that feature to the next version.

[Scyto]

Thanks,

 

My nodelink just updated to 0.8.8 - the pasword for the ISY seemed to have barfed?

--edit-=- the ISY cosole exited due to a reboot so i  guess this was casued by nodelink rebooting it for the upgrade?  Nothing in the log indicated thats what happend... t

 

2017-12-27 11:46:20 - ISY NodeLink Server v0.8.8 started

2017-12-27 11:46:20 - Mono version: 5.4.1.6 (tarball Wed Nov  8 22:23:23 UTC 2017)

2017-12-27 11:46:21 - ISY resolved to 192.168.1.97

2017-12-27 11:46:23 - Web config server started (http://192.168.1.118:8090)

2017-12-27 11:46:29 - ISY Error: Error getting web response from the ISY (The request timed out)

2017-12-27 11:46:29 - ISY Error: Error getting Node Server list - Root element is missing.

2017-12-27 11:46:29 - ISY Node Server profile set to 

2017-12-27 11:46:30 - Auto-Update: Checking for program update...

2017-12-27 11:46:30 - Auto-Update: No web update available

2017-12-27 11:46:31 - DSC: Connected to 192.168.1.118 [alarm]

2017-12-27 11:46:32 - GEM: Repeater started on port 8000 [gem]

2017-12-27 11:46:32 - DSC: EVL User Login - Password Sent [alarm]

2017-12-27 11:46:32 - DSC: Status Request Sent [alarm]

2017-12-27 11:46:32 - DSC: Data Sent - 00191 [alarm]

2017-12-27 11:46:34 - DSC: System Status - Disarmed (Set By Status Request - Partition 1) [alarm]

2017-12-27 11:46:36 - ISY Error: Error getting web response from the ISY (Error: ConnectFailure (Connection refused))

2017-12-27 11:46:44 - GEM: <data cut here by alex>

2017-12-27 11:47:32 - DSC: System Status - Disarmed (Set By Status Request - Partition 1) [alarm]

2017-12-27 11:47:32 - Web Request Invalid: /isylink/nodes/n001_owfs1/query

2017-12-27 11:47:32 - ISY Error: Status 404 (API_NOT_RECOGNIZED): ns/1/report/request/48/fail

 

[larryllix]

In a previous version (about NodeLink 8.4?) when I turned on the verbose and logging to a file it deleted my setup file completely and started over with all links cleaned out.

 

A backup file would be  good idea. This time I manually made a copy of the setup file. Setup parameters don't change very often once all devices are running.

 

As an aside... v8.8 has generated very few errors so far, compared to previous versions. It always seems once one device starts throwing errors the other devices start ,  along with the original device,  and it would escalate. Some problem in the Ethernet driver sharing I suspect.

 

I did have my ecobee3 and ecobee4 stats both go down simultaneously, and then come back simultaneously (stat server?), a few days ago, for about 6-8 hours but recovered by themselves without escalation on the system. v8.8 with ISY v5.0.11b seems to be working much more reliably so far! I understand there was interfacing cleanup and it seems to show so far.

[io_guy]

Verbose logging has zero to do with the config file.

 

I'm yet to see anything even close to the "ethernet driver" crapping out.

 

Ecobee's crappy server goes down all the time.

 

A logfile would be a lot better than coincidence. V0.8.8, or any in the last 20ish releases have done nothing to device interaction or handling.

[larryllix]

Verbose logging has zero to do with the config file.

 

I'm yet to see anything even close to the "ethernet driver" crapping out.

 

Ecobee's crappy server goes down all the time.

 

A logfile would be a lot better than coincidence. V0.8.8, or any in the last 20ish releases have done nothing to device interaction or handling.

It was about NodeLink v8.4?.

I clicked on ISY verbose logging and then Log to file and NodeLink disappeared off the screen immediately. When I re-opened NodeLink via same URL,  no devices were present. I checked the setup file and it was clean with only basic info. IIRC it remebered my ISY IP address only.  Only trying it again once it didn't happen again and I have produced log files.  I turned it off while I was away for a few weeks.

 

 

While my two ecobees were down errors started on my Venstar stat also. Only a few random  times. With v8.8 I see very few errors now. Maybe one per every few days. Before all the updates I would see 10-20 per weeks or more once they started until NodeLink reboot.

[Scyto]

On the 12th of Jan the settings got wiped out again, any ieas?

This also blocked upgrades (i assume by design).

 

2018-01-12 16:30:31 - ISY NodeLink Server v0.8.8 started

2018-01-12 16:30:33 - Mono version: 5.4.1.6 (tarball Wed Nov  8 22:23:23 UTC 2017)

2018-01-12 16:30:34 - No password specified for the ISY

2018-01-12 16:32:39 - ISY resolved to 

2018-01-12 16:32:39 - Web config server started (http://192.168.1.118:8090)

2018-01-12 16:32:39 - ISY Error: Error resolving hostname - ISY

2018-01-12 16:32:39 - ISY Error: Invalid URI: The hostname could not be parsed. (profiles/ns/0/connection)

2018-01-12 16:32:40 - ISY Error: Error getting Node Server list - Root element is missing.

2018-01-12 16:32:40 - ISY Node Server profile set to 

[larryllix]

 

On the 12th of Jan the settings got wiped out again, any ieas?

This also blocked upgrades (i assume by design).

 

2018-01-12 16:30:31 - ISY NodeLink Server v0.8.8 started

2018-01-12 16:30:33 - Mono version: 5.4.1.6 (tarball Wed Nov  8 22:23:23 UTC 2017)

2018-01-12 16:30:34 - No password specified for the ISY

2018-01-12 16:32:39 - ISY resolved to 

2018-01-12 16:32:39 - Web config server started (http://192.168.1.118:8090)

2018-01-12 16:32:39 - ISY Error: Error resolving hostname - ISY

2018-01-12 16:32:39 - ISY Error: Invalid URI: The hostname could not be parsed. (profiles/ns/0/connection)

2018-01-12 16:32:40 - ISY Error: Error getting Node Server list - Root element is missing.

2018-01-12 16:32:40 - ISY Node Server profile set to 

 

I had the same thing about v8.8 but I had a config.xml backup file created (after my last time) and it made it much easier to get back running. io_guy has added this to his versions now.

 

It seems NodeLink decides it is a virgin installation for some reason, and overwrites the config file with fresh startup information.

[Scyto]

I had the same thing about v8.8 but I had a config.xml backup file created (after my last time) and it made it much easier to get back running. io_guy has added this to his versions now.

 

It seems NodeLink decides it is a virgin installation for some reason, and overwrites the config file with fresh startup information.

good to know it is not just me, i think i saved a config.xml backup last time, will revert to that again.

[Scyto]

It didn’t just overwrite the file, it nuked the backup I had in there too. Went back to the file from July, upgraded, modified settings and this time saved the bak file off pi.