Concern about updating via SSH

[Greg P.]

Hi All,

I had not seen the notes about NOT doing a forced upgrade with SSH until AFTER I had done it. Now I'm concerned about what I may have messed up (I recently migrated from ISY994ir/Zw to eisy). Also, and I don't know if this was an issue BEFORE I did the forced upgrade, but when I try to go into PG3, I get the login screen and enter a login and click Submit and then literally nothing happens - screen does not even redraw. Wondering if the PG3 issue is related to my forced update via SSH.

In the interest of a "clean" system, can someone advise how I might go about "starting over" with the eisy hardware/OS so I'm sure I have not introduced problems? Clearly the first step is to backup Z-Wave and then backup the eisy, but then what... Will the Factory Reset TRULY reset it to the way it was when I unboxed it or is it going to just reset all config files, etc. but leave the current (forced-upgraded) version of the underlying OS there?

Note: I'm also hoping this solves the issue with getting notices about upgrades being needed every time I log in. I did see notes above to clear the Java cache and applications and downloading a new start.jnlp AFTER doing a full power-off (pull the power cord) so I will try that once I get the rest of this done if the issue still persists.

SOOOOO, if someone can advise on whether or not Factory Reset is the best way for me to get back to the true original files/OS that was on it out of the box, I would be most grateful. And if the process is just "do backups, factory reset eisy, restore backups" that's fine but if there's something else I need to do along the way, please advise.

[DennisC]

23 minutes ago, Greg P. said:

Hi All,

I had not seen the notes about NOT doing a forced upgrade with SSH until AFTER I had done it. Now I'm concerned about what I may have messed up (I recently migrated from ISY994ir/Zw to eisy). Also, and I don't know if this was an issue BEFORE I did the forced upgrade, but when I try to go into PG3, I get the login screen and enter a login and click Submit and then literally nothing happens - screen does not even redraw. Wondering if the PG3 issue is related to my forced update via SSH.

In the interest of a "clean" system, can someone advise how I might go about "starting over" with the eisy hardware/OS so I'm sure I have not introduced problems? Clearly the first step is to backup Z-Wave and then backup the eisy, but then what... Will the Factory Reset TRULY reset it to the way it was when I unboxed it or is it going to just reset all config files, etc. but leave the current (forced-upgraded) version of the underlying OS there?

Note: I'm also hoping this solves the issue with getting notices about upgrades being needed every time I log in. I did see notes above to clear the Java cache and applications and downloading a new start.jnlp AFTER doing a full power-off (pull the power cord) so I will try that once I get the rest of this done if the issue still persists.

SOOOOO, if someone can advise on whether or not Factory Reset is the best way for me to get back to the true original files/OS that was on it out of the box, I would be most grateful. And if the process is just "do backups, factory reset eisy, restore backups" that's fine but if there's something else I need to do along the way, please advise.

I would suggest that there might not be a need to do a factory reset. However, if you wish, the multi function button is your friend. Per the eisy user manual here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Multi_Function_Button, 10 presses of the multi function button does a factory reset.

The reason for using the upgrade packages button is to insure the updates are applied in the correct order.

I would suggest signing in to admin console and go to Configuration tab and select upgrade packages. Note that the admin console should close after a short delay and you should wait about 15 - 30 minutes before logging in again. You might also need to do a reboot after upgrading.

I would suggest trying this and if all is good afterwards, a factory reset isn't required, but future upgrades should follow the directions.

As for the PG3 login issue, you should be using the same login credentials for PG3 on eisy that you use for your eisy. If you still can not login, I have found shutting down eisy and removing power for a few minutes corrects that issue. It is something that is being investigated. If you still have an issue, post full details and a screenshot of errors.

As for the notice about upgrades being available, that is a known bug that will be corrected with the next release. 

 

[TRI0N]

13 hours ago, DennisC said:

I would suggest that there might not be a need to do a factory reset. However, if you wish, the multi function button is your friend. Per the eisy user manual here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Multi_Function_Button, 10 presses of the multi function button does a factory reset.

The reason for using the upgrade packages button is to insure the updates are applied in the correct order.

I would suggest signing in to admin console and go to Configuration tab and select upgrade packages. Note that the admin console should close after a short delay and you should wait about 15 - 30 minutes before logging in again. You might also need to do a reboot after upgrading.

I would suggest trying this and if all is good afterwards, a factory reset isn't required, but future upgrades should follow the directions.

As for the PG3 login issue, you should be using the same login credentials for PG3 on eisy that you use for your eisy. If you still can not login, I have found shutting down eisy and removing power for a few minutes corrects that issue. It is something that is being investigated. If you still have an issue, post full details and a screenshot of errors.

As for the notice about upgrades being available, that is a known bug that will be corrected with the next release. 

 

In addition to the Upgrade Button, it also makes sure that some libraries are not updated if they are not compatible with the current build of eisy. Just an example, lets say pyton released a new point release. UD might not have made any changes needed to ensure compatibility with a new point release of a library file. So they make sure that isn't updated till needed. 


TRI0N

Edited March 27, 2023 by TRI0N

[Greg P.]

@DennisC and @TRI0N - thank you both for the assistance. Dennis, per your guidance, I will hold off on the factory reset and see if I can get the updates message to stop showing. TRI0N, the detail on what the Upgrade button does is SUPER helpful!

All of that said, if I cannot get into PG3 at all, I may have no choice but to factory reset.

ONLY the very first time that I tried to login did PG3 "do something" (and it complained that my username or password was wrong). I refreshed the page and tried the same login I am using for IoX Launcher/Admin Console and when I click Submit, literally nothing happens - nothing spins, etc. in the browser to indicate it's trying to load a page and I do not get any error messages about the username, and it does not advance to any other page. 

I am going to try powering it off now per your other guidance and I'll loop back and let you both know how this turns out.

Thank you both again - very much appreciate the help!

[DennisC]

5 minutes ago, Greg P. said:

@DennisC and @TRI0N - thank you both for the assistance. Dennis, per your guidance, I will hold off on the factory reset and see if I can get the updates message to stop showing. 

For the messages to stop completely, a new firmware upgrade will be issued by UD. It's not been released yet 

[Greg P.]

Ah ok thanks for that on the firmware upgrade! I saw something about that in one of the posts I read but I got the impression the upgrade was already out (I am on 5.5.9 if that's the version that fixes this).

I did the full power cycle and waited 5 minutes before plugging it back in and that DID fix my login issue with PG3 - thank you once again!

I'll just ignore the upgrade notices for now and if, after the next firmware upgrade, it's all still happening, I'll open a ticket with UDI so they can advise if I really just need to factory reset or if there is some other way to fix the situation.

[Greg P.]

NOTE: The power cycle also seems to have corrected a "hung" upgrade process. I was watching the logs earlier today when I ran the upgrade using the button in Admin Console and the log messages stopped at "checking for the availability of updates for libarchive..."

It's gotten much further this time and is showing where it's checking repositories, etc (that was not in the prior log entries). At the moment it's been on "checking whether or not we need to reboot after upgrade" for about 2 minutes so far. The message DIRECTLY above that states that "upgrading eisy complete..." so that's good I suppose.

Not sure how long it should stay on the check for reboot - if you have any idea, let me know. I will otherwise give it an hour and then do a reboot, let it come back online, then shut it down and pull the power again.

QUESTION: Is there a "right" way to shut it down or is it ok to just pull the power out from under it?

Edited March 26, 2023 by Greg P.

[TRI0N]

8 minutes ago, Greg P. said:

NOTE: The power cycle also seems to have corrected a "hung" upgrade process. I was watching the logs earlier today when I ran the upgrade using the button in Admin Console and the log messages stopped at "checking for the availability of updates for libarchive..."

It's gotten much further this time and is showing where it's checking repositories, etc (that was not in the prior log entries). At the moment it's been on "checking whether or not we need to reboot after upgrade" for about 2 minutes so far. The message DIRECTLY above that states that "upgrading eisy complete..." so that's good I suppose.

Not sure how long it should stay on the check for reboot - if you have any idea, let me know. I will otherwise give it an hour and then do a reboot, let it come back online, then shut it down and pull the power again.

QUESTION: Is there a "right" way to shut it down or is it ok to just pull the power out from under it?

Press the button 6 times and wait for the light to turn red and then remove power is the correct way.


https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Multi_Function_Button

TRI0N

Edited March 26, 2023 by TRI0N

[Greg P.]

YAY! Between the power cycle and hitting the Upgrade button again, and then waiting a full 30 minutes, then a reboot, I am NO LONGER getting the repeat Upgrade notifications!

At this point, it feels like it's "all good" now.

Can't thank you guys enough!

[Greg P.]

@TRI0N - thank you for that info! 

QUESTION: since it's Linux powered, is there any reason I cannot do:
 

sudo shutdown -h now

(if there is/are better/safer options of 'shutdown' than '-h now' please let me know.

?

[TRI0N]

20 minutes ago, Greg P. said:

@TRI0N - thank you for that info! 

QUESTION: since it's Linux powered, is there any reason I cannot do:
 

sudo shutdown -h now

(if there is/are better/safer options of 'shutdown' than '-h now' please let me know.

?

Running that command is fine.. But I don't think it changes the front power button color. I never really looked.

TRI0N

[Greg P.]

Ok thanks! Way easier for me than running down to the basement

[Geddy]

@Greg P. There's also a "Reboot" button/option in Admin Console -> Configuration tab

While it's almost fool proof it doesn't always actually work, but should get you there in a pinch. 

However, seems like you connect via SSH more often than admin console so the shutdown command may be acceptable.

I've seen UDI suggest using: 

sudo shutdown -r now

Rather than your "-h" command. Not sure the difference.

 

[TRI0N]

57 minutes ago, Geddy said:

@Greg P. There's also a "Reboot" button/option in Admin Console -> Configuration tab

While it's almost fool proof it doesn't always actually work, but should get you there in a pinch. 

However, seems like you connect via SSH more often than admin console so the shutdown command may be acceptable.

I've seen UDI suggest using: 

sudo shutdown -r now

Rather than your "-h" command. Not sure the difference.

 

-r is Reboot. -h is just shutdown...

TRI0N

[Geddy]

13 minutes ago, TRI0N said:

-r is Reboot. -h is just shutdown

Thanks. Not a *nix user/fan. I'd think you would always want to reboot the device. Otherwise how do you get it to come back from a "shutdown"? Maybe -h also allows it to come back on?

@Greg P. some have gone outside the ISY world and use a wifi enabled outlet to be able to perform a "remote" power cycle for the device. It's an option...maybe not the cleanest reset option, but also saves you a trip to the basement. 

 

[DennisC]

5 minutes ago, Geddy said:

Thanks. Not a *nix user/fan. I'd think you would always want to reboot the device. Otherwise how do you get it to come back from a "shutdown"? Maybe -h also allows it to come back on? 

 

@Geddy,

The "-h", is to do a graceful shutdown, so he could pull the plug. It's the only way I know of to recover access to sign into PG3 when it doesn't accept your login.

Rebooting hasn't worked for me under those circumstances.

[Greg P.]

I do have an Amazon Echo plug hooked up to my eisy and I ended up remembering that AFTER I asked the question (duh). Thanks!!!

And I did know about the -r option. -h is for "halt"

My approach will be to use the shutdown command and THEN turn off the Amazon plug.

Edited March 26, 2023 by Greg P.

[Geddy]

1 minute ago, Greg P. said:

-h is for "halt"

"Halt & Catch Fire"! Great show on AMC for a while. 

5 minutes ago, DennisC said:

The "-h", is to do a graceful shutdown, so he could pull the plug

That's the thing though... @Greg P. said he just used the (-h) shutdown command rather than going down to the basement to pull the power. So if -h doesn't reboot it then he (or somebody) would have to go turn the device back on....right? Best yet...."Alexa, Reboot eisy" routine upcoming!

Glad @Greg P. has it sorted out though. I was just uncertain about the command difference. I've seen the -r mentioned here so many times that the -h was "new to me". Thanks for the lesson!