Device names, Apps and rules gone or different after upgrade to 2.3.3.xxx

🛎️ Get Help
1

I upgraded my hub to 2.3.3.xxx when it came out and I had a lot of problems. Stable rules didn't work using motion triggers, the hub mode wasn't working, a handful of items. No big deal, I restored back to my previous version to 2.3.1.142. Everything was good again. I wasn't overlly worried as I didn't need to take advantage of new features and if I just wait a while these bug will get ironed out.

I tried a later version of 2.3.3.xxx and same thing. Now 2.3.3.138 seems like it works like it should and that's where I'm at. My question is while I was at the previous version I renamed some devices and installed an app or two and had a few rules I had made. Upgrading to the newer version for some reason lost them and I'm curious if there is a way to get it back. If I revert back to the previous version it will be there, but rolling forward it is lost. It's almost like the upgrade isn't done on the active version I'm sitting on and a different one is used (pre my rules, updates and apps).

Thanks ahead of time, I'm hopeful this makes sense and I don't need to go through the effort of screenshots and the whole bit. It's probably a horse a piece of redoing the work vs creating the documentation for the case above. If someone's run into this it may be something I need to do in a specific way I'm not aware of. Its a few hours work I'm trying to avoid.

2

Just to confirm, you mean you’ve already tried reverting to a backup prior to the firmware upgrade, you can see the data that was “lost,” and then updating the hub firmware causes things to disappear again?

1 Like
3

Possibly. There was a change in database format introduced in 2.3.3.x - so it is possible that when you reverted to 2.3.1.x (the first time), device and app changes were made.

When you upgraded again to 2.3.3.x, it used the 2.3.3 formatted database, rather than re-convert the old (albeit updated) database.

Tagging @gopher.ny

If it were my hub, I would try this:

  1. Go to 2.3.1.x - make a backup and download it.
  2. Update to 2.3.3.x - and do a soft reset
  3. When you restore, use the saved backup from 2.3.1.x

I think that will put everything back in sync again.

4 Likes
4

Right, grab the latest pre-2.3.3 backup and restore it to 2.3.3. That should bring it up to date. Automatic database conversion is a one-time deal (on purpose).

3 Likes
5

Correct.

6

Oh thanks for the advice. I will give this a try tonight and what happen. Fingers crossed.

10-29-22 - That worked, thank you very much for the help!

2 Likes
7

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.