@bravenel and others, I get the below error every time I restart my hub from the "Hubitat Dashboard" app...
org.h2.jdbc.JdbcSQLException: Column "device_id" not found [42122-197] on line 903 (dashboardDevices2).
Wondering if phantom devices might be causing issues in my hub...
Also, I've done a few soft resets in the last couple of weeks and that acts like a restart for me... Makes the hub run faster for a day and slowdowns return the next day...
Interested in this thread as well as I am seeing similar limited uptime before substantial slowdown (my original post describing my issue was split off into Problems with hub performance after update )
No performance issues surface until a couple of days elapse.
For what it's worth, I'm now also getting a bunch of dashboard error messages:
app:32020-01-23 10:38:30.101 pm errororg.h2.jdbc.JdbcSQLException: Column "device_id" not found [42122-197] on line 903 (dashboardDevices2)
app:32020-01-23 10:37:50.069 pm errororg.h2.jdbc.JdbcSQLException: Column "name" not found [42122-197] on line 903 (dashboardDevices2)
app:32020-01-23 10:37:16.714 pm errororg.h2.jdbc.JdbcSQLException: Column "name" not found [42122-197] on line 903 (dashboardDevices2)
app:32020-01-23 10:36:39.109 pm errororg.h2.jdbc.JdbcSQLException: Column "name" not found [42122-197] on line 903 (dashboardDevices2)
app:32020-01-23 10:34:26.250 pm errororg.h2.jdbc.JdbcSQLException: Column "device_id" not found [42122-197] on line 909 (dashboardDevices2)
app:32020-01-23 10:32:21.612 pm errororg.h2.jdbc.JdbcSQLException: Column "device_id" not found [42122-197] on line 909 (dashboardDevices2)
app:32020-01-23 10:31:47.610 pm errororg.h2.jdbc.JdbcSQLException: Column "device_id" not found [42122-197] on line 909 (dashboardDevices2)
app:32020-01-23 10:26:57.087 pm errororg.h2.jdbc.JdbcSQLException: General error: "java.lang.NullPointerException" [50000-197] on line 909 (dashboardDevices2)
app:32020-01-23 10:25:37.110 pm errororg.h2.jdbc.JdbcSQLException: Column "device_id" not found [42122-197] on line 909 (dashboardDevices2)
app:32020-01-23 10:24:22.503 pm errororg.h2.jdbc.JdbcSQLException: Column "device_id" not found [42122-197] on line 903 (dashboardDevices2)
app:32020-01-23 10:24:10.986 pm errororg.h2.jdbc.JdbcSQLException: Column "device_id" not found [42122-197] on line 909 (dashboardDevices2)
app:32020-01-23 10:22:08.702 pm errororg.h2.jdbc.JdbcSQLException: Column "device_id" not found [42122-197] on line 903 (dashboardDevices2)
app:32020-01-23 10:21:29.639 pm errororg.h2.jdbc.JdbcSQLException: Column "name" not found [42122-197] on line 903 (dashboardDevices2)
These are signs of a corrupted database. It is conceivable, although we haven't seen it before, that you do have a bad flash memory in your hub. Contact me by PM about this...
I am running hub watchdog.
EVERY morning at around 2am the watchdog figures go from between 0.09 to 0.3 to 10 to 20 seconds.
This is during the maintenance window.
My auto backups run at 03:00 so I know it's not this that is causing it.
I have asked in a previous thread what actually happens in a maintenance window but never had a response to it.
As I'm getting my much needed beauty sleep at this time I didn't pursue it but it would have been nice to get a response.
I'm glad you're getting your sleep, my beauty! 
To Hubitat Management: @bravenel etal:
Perhaps you've already thought about this, perhaps not.
Perhaps we should not have to do this, but perhaps it will help many users.
We can make this optional, by allowing the user to opt-out, by putting something in "settings"
Why not make, as part of the daily backup procedure at 3am, a period of "maintenance". As part of that "maintenance" you reboot the hub, or even perhaps do some "soft reset procedure".
P.S. A number of other competitors do this daily (e.g. Vera, etc.).
Please consider this a "feature change".
By making it optional, you can ensure that everyone who doesn't want to occur, will not have it occur.
There may be a small number of users who will not be able to do a reboot - but they have will issues anyway.
I know that you shouldn't have to do this, but isn't it expedient to do it this way?
Skipping it entirely might cause more support issues than they can handle. Perhaps just the ability to change the schedules start time of maintenance, and if necessary move the backup time forward with the change in maintenance time.
That is, if it’s at all possible. There’s typically a good response to requests from many people here, but this one hasn’t seen any love. So maybe it’s just not an option that’s under their control. 
Looks like I had a faulty hub. HE sent me a replacement hub and the performance is a LOT better with all my apps and devices migrated. Much better experience finally
Did you migrate everything over manually or were you able to use a backup?
I am having the same issue and have ordered another hub. My plan is to leave my devices paired to my current hub and move all of my apps and cloud devices to the new hub and use Hub Connect. The new hub will do the thinking and the old hub will talk to the devices. Would love to hear other ideas. I have 217 devices 19 of which are cloud based.
Edit: Polling any Z-Wave devices makes the hub slow down at an increased rate in both time and severity. I still wonder if there is some kind of memory leak.
Manually. I only have 35 or so devices so wasn't too bad for me. Can't imagine even beginning to move everything around if I had 217 devices. Would leave others more experienced to chime in on your best options. I do use Hubconnect to connect HE to SmartThings and it works great
I have all of my lights on my original hub, and just end devices and repeaters I trust on the new hub. I recreated most of the rules on the new hub and put my Hue bridge integration (CoCoHue actually) there as well. I kept Alexa on the "lights" hub thinking it would cut down on traffic that way. I'm using HubConnect with the 2 HE hubs, a ST hub (for Echo Speaks), and 2 HomeBridge instances for my Home dashboard. I haven't seen slowdowns so far and it all has been very reliable.
Interested to know your reason to “poll” devices as it’s known to strain the little ZWave radios throughput.
Polling
I have some non Z-Wave plus switches that do not report status if actvated manually. They are used in rules and the rules do not run because the hub does not know they were turned on. Example, I have a rule to turn off bathroom exhaust fans 15 minutes after they are turned on. Since I moved to Hubitat, that rule will not run. It was never a problem with SmartThings or Iris.
You probably are aware of this: SmartThings has a ZWave Poller running too, just it's permanent and polls everything, antique tech or not and is hidden. Remember, their hub doesn't have very much to do. Samsung swears they are going to get more local processing, but then the hub is going to be competing with the hidden ZWave Poller task.
I'm getting this same error on my new hub and my hub gets very slow when I get it. No idea what's going on. This time, I've only been getting it for about 2 weeks. Maybe my database has gotten corrupted again? I did a soft reset but still get the same error.
Thanks
org.h2.jdbc.JdbcSQLException: Column "device_id" not found [42122-197] on line 915 (dashboardDevices2)
I'm also seeing similar error messages in the logs with extreme slow downs.
Hubitat Team - What is causing this issue? HELP!
org.h2.jdbc.JdbcSQLException: Column "device_id" not found
That error seems to be caused by the hub (or an app) looking for a device that has been removed, but not completely removed from all rules. Watch the log while you trigger rules/devices and you should be able to narrow it down.
Download the Hubitat app
