DeviceID error messages

[Steve Horn]

Along with the error messages I'm getting on "Error Reading COM port. Error=Insufficient Data in read buffer", I'm getting several messages "Unable to find Device ID [nnn] in Device list", where nnn is 152, 166, and 235. I've looked at all the tables in HBDATA but cannot find the device IDs listed in the error messages. The tables I found that specifically reference Device ID are Alphalist, DevicePropertymap, Devices, PropertyValueCommandMap, PropertyValueIRMap, PropertyValueWinMsgMap, TaskList, and TestConditions. Where else could they be found?

[ScottBot]

The table you are looking for is the Devices table. It is most likely coming from a Theme that has a control that is referencing a Device that has been deleted. The next release will help to identify these controls so you can either remove them or resolve the invalid Device reference.

[Steve Horn]

Been to all the tables. Will poke around in the Theme file to see what I can find there. Thanks.

[Richard Naninck]

Strange, I wrote a reply to your first post telling the error could be in the theme xml file. Something similar Scott wrote.
Did that reply not make it, or has it been deleted? Just curious!

[Steve Horn]

Richard, the reply did not make either here or to the forum. But after Scott replied I remembered that I had asked the same question... and gotten the same answer a year or so ago. My work with HB comes in fits and starts and I apparently don't or can't remember from one session to the next what transpired and what I learned in the last go round. Sad.

[ScottBot]

Strange, I wrote a reply to your first post telling the error could be in the theme xml file. Something similar Scott wrote.
Did that reply not make it, or has it been deleted? Just curious!

I definitely didn't delete it... I greatly appreciate any help on the forums. It's possible that maybe it was getting posted when I upgraded the forum software several days ago, although the database shouldn't have been effected. I've also been having more problems than usual with my hosting provider, so maybe something got lost there.