Software Update without usb stick

[nellog 0]

Hi, I've an HC2 with broken usb stick key but still it running (i don't wanna send to support for usb replace because I've just send few month ago and i've already spent more then 100 euros). As you to know I can still perform the upgrade to latest software release?

 

Thanks.

[1152 33]

Nellog, sorry I can not help you.

 

Fibaro, pleas come up with a fix for the USB issue - you soon have customers all over the world trapped - out of service - time - and money

[j.nowacki 5]

State of recovery memory is not relevant in update process, but of course automatic backups will be omitted.

[1152 33]

j.nowacki

 

I have now contacted support after trying multiple times to upgrade my system (the one at my home). I can not get past a need more space message that generates an Error 10 at the 10% level. (The system reports updating from 3.600 to 4.054, then changes to 4,049, then downloading patch, extracting, creating backup 3.600->4.049 at the 8% level, then stopping all services at 9% level, checking firmware at 10% and then need more space and the Error 10 message).

 

I had the impression this was related to the usb memory, but according to your statement I understand I got it wrong. Could you please expand on this issue, eg upgrade and memory - (not the back up issue that remains for those with a broken usb stick).

[Ucciogenerale 2]

Hi, I've an HC2 with broken usb stick key but still it running (i don't wanna send to support for usb replace because I've just send few month ago and i've already spent more then 100 euros). As you to know I can still perform the upgrade to latest software release?

 

Thanks.

Hi Nellog, we are in the same boat, USB suddenly broken but update worked well, no problem at all.

 

Backup all your scenes and data with Krikroff's tool, Krikroff made the tool that allow you to save at least all the LUA code. 

 

Why Fibaro did not yet implement the cloud backup to allow the people to not struggle with it? Honestly I don't know. As of today this is the best home center but something really simple like that is still missing.

 

A domotic system must be reliable, usb stick isn't! The rest of hardware is really ok, but why I should stop my system for one month in order to change only the usb stick?

[nellog 0]

Hi Nellog, we are in the same boat, USB suddenly broken but update worked well, no problem at all.

 

Backup all your scenes and data with Krikroff's tool, Krikroff made the tool that allow you to save at least all the LUA code. 

 

Why Fibaro did not yet implement the cloud backup to allow the people to not struggle with it? Honestly I don't know. As of today this is the best home center but something really simple like that is still missing.

 

A domotic system must be reliable, usb stick isn't! The rest of hardware is really ok, but why I should stop my system for one month in order to change only the usb stick?

Hi, thanks for information! where I can find the Krikroff's tool? do you have a link for latest version? Thank you!

[SpikeB 0]

Hi, thanks for information! where I can find the Krikroff's tool? do you have a link for latest version? Thank you!

 

Please login or register to see this link.

[sj3fk3 27]

On 9/15/2015 at 2:04 PM, j.nowacki said:

State of recovery memory is not relevant in update process, but of course automatic backups will be omitted.

 

I wish that was true.. I'm trying to upgrade and don't even care about back-ups anymore.. But cannot upgrade because of faulty recovery-USB stick

Please login or register to see this attachment.

[petergebruers 1,268]

@sj3fk3 not sure why you quote a post from 2015 but your question/observation seems quite valid anyway!

 

Indeed, AFTER the migration to 4.510 you can (should!) remove the recovery key. But right before the upgrade, I guess it's still used to make one complete backup.

 

What did [email protected] tell you to do?

 

EDIT: what I want to say is (1) I'm sorry you cannot upgrade (2) in the past Fibaro could sometimes check/repair/clean the stick via remote access.

 

Edited August 22, 2018 by petergebruers

[sj3fk3 27]

1 hour ago, petergebruers said:

@sj3fk3 not sure why you quote a post from 2015 but your question/observation seems quite valid anyway!

 

Because it's still valid?

 

Quote

Indeed, AFTER the migration to 4.510 you can (should!) remove the recovery key. But right before the upgrade, I guess it's still used to make one complete backup.

 

See statement above.

 

Quote

 

What did [email protected] tell you to do?

 

Given up hope long ago.

 

Quote

 

EDIT: what I want to say is (1) I'm sorry you cannot upgrade (2) in the past Fibaro could sometimes check/repair/clean the stick via remote access.

 

 

Tried repair myself but did not help.

 

I've got a clean HC2 with factory default that doesn't want to upgrade to 4.510 either..  Completely switching over to Home Assistant (a open source Python solution).

 

Edited August 22, 2018 by sj3fk3

[petergebruers 1,268]

I am sorry to hear you're stuck with this... twice!

 

You say you're going to migrate away from Fibaro to Home Assistant. I run Home Assistant as my test system, so I can understand why you'd want to do that.

 

I hope you get it fixed anyway.

[tinman 1,070]

5 hours ago, sj3fk3 said:

On ‎9‎/‎15‎/‎2015 at 2:04 PM, j.nowacki said:

State of recovery memory is not relevant in update process, but of course automatic backups will be omitted.

I wish that was true.. I'm trying to upgrade and don't even care about back-ups anymore.. But cannot upgrade because of faulty recovery-USB stick

there is difference between "not relevant in update process" and "relevant to run update process".

 

 "not relevant in update process" -> means, it will run without or with broken (if the script managed to get timeout) recover drive

 "relevant to run update process" -> means, it will not even start when no space left.

 

Why is like that ? Very simple, the update from 4.180 to higher firmware is in first place part of 4.180 firmware, which does check the recovery drive size and stops when no space left. When you remove it, boot your HC2 without, you will be able to run update. It will only not be able to create autobackup, that's all. As soon the migration firmware (the first part of 4.5xx) takes control over the system, the recovery drive is not necessary any longer anyway and will even get disabled (no boot from external recovery drive).

 

 

3 hours ago, sj3fk3 said:

I've got a clean HC2 with factory default that doesn't want to upgrade to 4.510 either.

 

clean but already used HC2, right? Factory default does not clean up the recovery drive, nor makes any checks on it. If so, you might have here problem with S/N manipulations, MAC manipulations, empty S/N, bad recovery drive blocking 4.1xx update procedure, bad internal drive (preventing from fs resize).

I have "recovered" / updated to 4.5xx some previously "broken" HC2s, where customers rejected to get recovery drive repaired with the hope for 4.5xx changes, and got already all kind of possible errors, but the all related to something which is already broken or manipulated (e.g. empty S/N), once these things fixed no issues with 4.5xx migration (as long we did it, sure, there are customer who clicked right after first boot of 4.510 on recovery, and produced additional work for us).

 

[sj3fk3 27]

20 minutes ago, tinman said:

Why is like that ? Very simple, the update from 4.180 to higher firmware is in first place part of 4.180 firmware, which does check the recovery drive size and stops when no space left. When you remove it, boot your HC2 without, you will be able to run update. It will only not be able to create autobackup, that's all. As soon the migration firmware (the first part of 4.5xx) takes control over the system, the recovery drive is not necessary any longer anyway and will even get disabled (no boot from external recovery drive).

 

There's no recovery-drive in the "broken" HC2 and it's not able to update. It is able to boot Software Version: 4.170  (without the recovery disk).

 

20 minutes ago, tinman said:

 

 

 

clean but already used HC2, right? Factory default does not clean up the recovery drive, nor makes any checks on it. If so, you might have here problem with S/N manipulations, MAC manipulations, empty S/N, bad recovery drive blocking 4.1xx update procedure, bad internal drive (preventing from fs resize).

I have "recovered" / updated to 4.5xx some previously "broken" HC2s, where customers rejected to get recovery drive repaired with the hope for 4.5xx changes, and got already all kind of possible errors, but the all related to something which is already broken or manipulated (e.g. empty S/N), once these things fixed no issues with 4.5xx migration (as long we did it, sure, there are customer who clicked right after first boot of 4.510 on recovery, and produced additional work for us).

 

 

The other HC2 I bought as backup, was clean. Does the update but then becomes unresponsive..