fucked up update!

[akatar 208]

Well updating the master and slave was again a disaster, master works, most of the slave devices are gone and scenes are not running with slave devices.

restored bot with the last backup (just made it before updating) that resolved in a working master and a slave starting up and rebooting constantly

 

Any idea how to solve this easy? i am not going to add every device again

how is it possible that this is the third *abuse* time in a row that a simple update fails!

[akatar 208]

well, i will try to factory reset slave, update it, add as new slave to the master and restore last backup............

did that and again devices where gone (powernode 6) i had to remove and add that again and it seems if there are scenes with device in it that are missing the scene will not run at all, even the devices that are there won't do anything.

 

thing is that the powernode 6 (i have a couple of them) where only gone on the slave not on the master

[m.roszak 763]

This one (with scenes) - working on it.

As for the issue with the update, we tested this on a lot of different master-slave configurations and worked ok.

 

If you already have your system back and running maybe we can arrange updating to the next package with our supervision?

 

This will help a lot with pinpointing what is the issue here which we can't reproduce.

[akatar 208]

@m.roszak so the scene problem is a known problem?

just add a greenwave powernode 6 to a slave, do the update and you will see that that device is gone, did it twice and both times it was gone.

 

After restoring the last backup the slave ended in a bootloop (restarting over and over) until is booted on the other system.

the moment this will happen you won't see that remotely because it wil not get a connection?

next update wel will do together

 

[m.roszak 763]

If on action side of the scene is a code related to not existing device anymore scene execution will be cancelled when this part od code is executed.

 

I think that we already working on it, I will update with devs on the ETA with fix let you know.

[Comfortica 17]

10 minutes ago, m.roszak said:

If on action side of the scene is a code related to not existing device anymore scene execution will be cancelled when this part od code is executed.

 

I think that we already working on it, I will update with devs on the ETA with fix let you know.

But scenes without "missing" devices work correctly in this update ? 

[akatar 208]

@Comfortica

Yess, scenes without missing devices work

@m.roszak it would be nice if fibaro add "known problems" at the feature list of that fw release.

[m.roszak 763]

This is an old issue I think - just found recently.

As for known issues, if there is something critial we often put this on the changelog