Cannot completely revert from 2.3.3.121 to fix an exuberant user error

ISSUE:
When reverting from 2.3.3.121, restoring database, then reapplying 2.3.3.121, it seems remnants of new database are not cleared.

EXPECTED BEHAViOR:
I would be reprompted to import scenes and motion lighting into new room lighting app and see old legacy apps still intact

ACTUAL:
Legacy apps are removed and previous mistakes in imports already appear as if new database was not deleted on reversion of firmware and restoration of old backup.

DETAILS:

I recently installed the new update 2.3.3.121 but found that i coukd not get old scenes to operate correctly. Unfortunately i committed a major I.D.-10T by being a bit over exhuberant in removing the old legacy groups and scenes and associated child apps prior to throughly testing everything out. That left me unable to self troubleshoot the transition between old scenes and the new ones in room lighting. Doh!

I attempted to restore the previous firmware through the diagnostics app and then restore the backup from prior to application of the latest firmware. That was successful in restoring everything to working order in a state prior to applying the latest firmware update. Unfortunately something is either wrong or i am still in idiot mode.

I then attempted to reapply the new firmware update thinking that it would then prompt me to reimport scenes and motion lighting into the new room lighting app (as it did the first time i opened the new room lighting app), but it does not. It automatically has removed my legacy apps and recreated my previously imported room lighting child apps as when i screwed it all up the first time i applied the update (but yet i did not recreate any of those prior actions). For some reason it seems part of the new database from 2.3.3.121 is not being wiped in the reversion to previous firmware and restoration of the previous backup. Unfortunately there is no way to reinstall the legacy apps so i can recreate scenes in them and then experiment with walking them over to see whats going on. New "scenes" i am creating are still giving me problems (namely not activating completely, at all, or with major popcorning). I am not really focused on this latter issue until i can recreate the firmware update and migration first so i can figure out what i need to tweak and adjust from the migration.

What am i doing wrong in my method for reverting... or can i just get the source code for the legacy apps so i can install those for troubleshooting purposes? Thanks!

Database migration creates a one time marker. Why not just restore 2.3.2 backups to 2.3.3 firmware? Those will work on either version. 2.3.3 backups will not import into 2.3.2 or earlier versions, though.

Honestly did not try that option. I assumed wrongly backups needed to be applied with their associated firmware, at least in terms of applying backup with older firmware. I will give it a shot.

Thanks! I should have tried that first. I had made what i already made complicated even more complicated. Cheers!

1 Like