Upgrade to 2.5.x failed, soft reset and restore failing

What version were you on before? What are your options in the restore previous version from diagnostics? Did you try any of those?

What he (we) said.

Vitaliy’s explanation clarified what you meant. You used jargon, and then used more jargon to explain the initial jargon :slightly_smiling_face:.

To update where we are, I have completed a shutdown, power down, restore power, and I'm back at just spinning while restoring the database. I did not do an additional soft reset, and I have Open Weathermap in my device list; that's all (restore still spinning).

Log viewer returns Error 500. fml :slight_smile:

Did you do a reboot w/database rebuild (even though you had done a soft-reset)? If not, humor me (I obviously have a very low humor threshold :wink: ) and do that.

@bobbyD - any advice here?

This is potentially relevant information to know.

1 Like

I was originally on 2.4.3.173. Restore previous version gives me the option of 2.4.2.160 and 2.5.0.126.

Same behavior, more or less:

  • rebuild fails
  • soft reset
  • restore from latest compatible backup (2026-04-10, 2.4.3.173) restores Open Weathermap, nothing else, Error 500 on logs, restore does not visibly complete
  • after waiting a while, soft reset/soft reboot
  • Open Weathermap still listed!
  • restore from 2026-03-14 (2.4.3.173)
  • still no devices other than OpenWeathermap (haven't rebooted, logs still 500)
1 Like

Please send a message to @support_team along with your Hub ID. Based on the details you’ve shared so far, it appears you may be dealing with a hardware-related issue. If you have Hub Protect, you may qualify for a free replacement hub. However, we’d first like to confirm whether the issue is truly hardware-related and not caused by software or just database problems.

1 Like

I might have confused your username for someone else's, but could you remind me which PoE adapter you're using?

@dennypage did a nice study revealing the ones that worked v/s the ones to be avoided.

1 Like

I was thinking it sounds like when the hub runs of storage space from logging going crazy or something. But I have no idea how to get those logs cleared without a full reset.

It’s a plausible theory, as I did get that alert about log space. However there is no UI to my knowledge that lets me disconfirm or confirm it.

FWIW, I did also select log truncation on at least one of the resets, and on the one occasion when the 500 error was not showing, there were not a bunch of new entries. I did not confirm old entries.

Its not typically been the system log that you see, that is setup as a rolling file with a file size cap. In the past it was some internal engineering log that was not capped or not rolling over correctly and it blew up and filled the entire hub storage until it could not boot.

1 Like

Thanks for that observation. Being unable to see any log entries or usage of system partitions, I'm not able to validate the theory. I'm still waiting on support at this point.