Error

[jstaab]

For varying reasons, I've had to delete and recreate numerous devices in HS that I have defined in mcsTemperature to track and graph. I've found that each time this occurs, I typically receive numerous errors in mcsTemperature upon doing so. I've been able to tweak the INI file on occasion, however, most of the time I end up shutting down mcsTemperature, deleting the INI file and database file and starting over from scratch. I'd like to try to figure out what the problem is without starting over each time. At the moment, I'm receiving the following error when trying to view a graph or table:
11/5/2005 12:36:54 PM - mcsTemperature - FormatTemperatureScreen on line 2120 Syntax error (missing operator) in query expression 'ID='.
I can edit the default group just fine, I receive no errors when viewing the general setup in the GUI (which wasn't the case earlier until I tweaked the ini file).

Any thoughts?

[jstaab]

Never mind, just updated to the latest version to HS 2.0 and the problem is gone now, go figure. I'll repost more info next time it happens.

[Michael McSharry]

I can see where the potential for an error when the database being referenced is empty. What is the process that you use when informing mcsTemperature about your configuration changes?

The logic is quite complex to try to understand what a user is trying when multiple things are being changed. mcsTemperature needs to keep track of the relationship between a sensor, a virtual device code, a virtual device name, and a database field name. It will delete/rename/add HS devices. It will add database fields, but not delete any. It will try to fix breakages by creating database fields when requested ones do not exist.

[jstaab]

I've had several scenarios. The most common one though is where the device is completely deleted, then re-added. The device codes and name, may or may not be the same (they come from another plug). Next time I walk through this scenario, I'll attempt to take snapshots of the ini file and other information along the way as well to get a trace of the events that took place. Renaming the devices via HS seems a bit tricky as well at times. I've somewhat figuered out the relationship of the items in the INI file and have figured out how to fix a couple of the errors when they occur. I'll attempt to gather more info next time around and keep track of the steps I took in hopes that they will be re-produceable. I THINK though that a portion of my problem was that a plug in created multiple devices with the same house code and unit code.

[Michael McSharry]

A relatively recent HS build fixed the problem of multipe device creation. This can really mess things up when it happens

[jstaab]

Maybe that was part of the problem. I hung out on build 1996 for a while, upgraded to the latest today.