JohnM wrote:Sorry I copied the wrong parts, understand that these are the outputs. The problem is when running /root/platform/upgrade.sh not update is generated like the last time, line just defaults to prompt.

I suspect something happened to your wink device outside of the norm... example, you should never have to run chmod +x on the update scripts as they should never be lost...

JohnM wrote:Sorry I copied the wrong parts, understand that these are the outputs. The problem is when running /root/platform/upgrade.sh not update is generated like the last time, line just defaults to prompt.

I suspect something happened to your wink device outside of the norm... example, you should never have to run chmod +x on the update scripts as they should never be lost...

Hiya,I tried the instructions and it got my system going again, was able to return to step 6# to run /root/platform/upgrade.sh which this time spewed out content similar to yours but had issues with the datecheck at the end.

JohnM wrote:I'll check the DNS settings as suggested, if I need to make changes from which step should I run again?

From what I can tell, all it failed to do was set the time... your hub probably thinks it's January 1st 1970.

Here is an example of me manually setting the date "date -s" to 1/1/1970... displaying the date... updating the date directly from 208.88.126.226 (one of the addresses 0.rhel.pool.ntp.org points to)... and displaying the date again showing a current and correct date and time.

JohnM wrote:I'll check the DNS settings as suggested, if I need to make changes from which step should I run again?

From what I can tell, all it failed to do was set the time... your hub probably thinks it's January 1st 1970.

Here is an example of me manually setting the date "date -s" to 1/1/1970... displaying the date... updating the date directly from 208.88.126.226 (one of the addresses 0.rhel.pool.ntp.org points to)... and displaying the date again showing a current and correct date and time.

Since I'm using an IP address instead of a DNS name, DNS isn't required

JohnM wrote:I'll check the DNS settings as suggested, if I need to make changes from which step should I run again?

From what I can tell, all it failed to do was set the time... your hub probably thinks it's January 1st 1970.

Here is an example of me manually setting the date "date -s" to 1/1/1970... displaying the date... updating the date directly from 208.88.126.226 (one of the addresses 0.rhel.pool.ntp.org points to)... and displaying the date again showing a current and correct date and time.

Since I'm using an IP address instead of a DNS name, DNS isn't required

Thank you, I will try that. I have blue light back on my wink hub, since the update, without the date being corrected will do that next. Just wanted to update you to say that the hub is now fully working again and blue solid light.