Database Error

[jbfoster]

I restarted HS4 and this was in the log.

[SteveMSJ]

I restarted HS4 and this was in the log.

The error means the pi can't find the database of battery history file which is '[HomeSeer directory]/Data/SDJ-Health/BatteryLog.db3'.

If you can give a bit more information and I'll try and pin down the issue.

• What OS?
• What versions of HS4 and SDJ-Health?
• Is this an upgrade from HS3, if so which method did you follow?
• Has it been running ok or is this the first start up in HS4?
• Is the database file noted above present on your system and if so what size is it?
• Have you got LogToDatabase checked on the Battery Devices config page?
• Do you get any displayed battery history or error messages when you click on the 'History' button of any of the monitoring devices?

Thanks,
Steve

[jbfoster]

The error means the pi can't find the database of battery history file which is '[HomeSeer directory]/Data/SDJ-Health/BatteryLog.db3'.

If you can give a bit more information and I'll try and pin down the issue.

• What OS? Windows 10 Version 2004
• What versions of HS4 and SDJ-Health? Ver 3.0.8.6
• Is this an upgrade from HS3, if so which method did you follow? I upgraded from HS3 to HS4 using the alternate method.
• Has it been running ok or is this the first start up in HS4? It's been. Plugin seems fine since since about July 3rd.
• Is the database file noted above present on your system and if so what size is it? No Database or folder with that name.
• Have you got LogToDatabase checked on the Battery Devices config page? No.
• Do you get any displayed battery history or error messages when you click on the 'History' button of any of the monitoring devices? Where is the History Button?

Thanks,
Steve

See my remarks above in Red. I'll post some screen shots. Let me know if I forgot something.

Thanks
Jim

[SteveMSJ]

See my remarks above in Red. I'll post some screen shots. Let me know if I forgot something.

Thanks
Jim

Hi Jim,

Thanks for the detailed information.

I can see now that this is actually an inappropriate error message that shouldn't occur in your particular circumstances. It doesn't affect the operation in any way but I will correct it in the next update.

The reason is that, as you don't have LogToDatabase selected the pi does not maintain a history log of battery values for the devices. In version 3.0.7.4 I added extra features to the discharge rate information which included average discharge rates from the time of the last battery change. If there is battery history information then the pi can find the start battery level after the last battery change but if not it assumes the batteries started at 100%. The error message you see is where the pi looks for the database to check if it can find a start level. As there is no database in your case it logs the error message and then uses 100%. It shouldn't log an error message if LogToDatabase is not selected because it should not expect to find one, which is my slip up.

Having said that you may wish to consider using the LogToDatabase feature as it builds up lots of useful, or at least interesting, information over time. Have a look at pages 8, 9 and 13 of the guide.

Steve

[jbfoster]

Sounds good thanks. I turned on LogToDatabase.

Jim