Steve Horn wrote: ↑Sat Dec 28, 2024 5:01 pm
OK, I can look inside HBData.(I havent been here in a LONG time.) DevID is a TIVO STB. Prop 73 is Send IR command. Delete the device??
I wouldn't delete the device unless it's invalid somehow or shouldn't exist.
Better to just delete the reference in the TaskList table (if you can find it).
It’s valid but something that could be rebuilt. If I can get HBData to load and HB to launch that would be a big step. Didnt get far into the DB last night but will look at the TaskList table.
i deleted 100+ records in TaskList for the devid 516 prop 73. then got a similar message for 324/73. (Strangely, I was unable to make changes to HBData on the Win11 box, was told it was read-only, even after I changed all its security properties to full control. but I made the changes on the old win10 box then copied it over.)
Thinking that might be IR related, I migrated, with some difficulty, the USBUIRT device and its drivers to the new Win11 box. Same result. But now I'm thinking that there is a more fundamental problem with HBData. I shouldn't have to be deleting 100s of records from it.
Ive resolved myself to having to essentially start from scratch… I can add all the devices fairly easily, and relearn IR codes, rebuild tasks etc. BUT how to rebuild/import, without starting over, the themes?? (That said, there are probably only a few that would need doing. Sadly, this has probably triggered a serious HB housecleaning effort. Lots of stuff has been built and collected since Day One that is no longer used or necessary.)
Well... that's a bummer. Unfortunately even though the theme are just XML files, when you recreate devices and tasks, they will get new IDs that won't match the ones stored in the theme XML.
Suspected as much, looking at the OLD diagram of the MS Access HBData database. HOWEVER...
I found an ancient Aug '24 backup of CONFIG. used it on a new install of HB on yet another (WIN10) PC and was able to see everything. Not functional of course; the PC is nowhere near the server/equip closet - no hardware connections etc.. BUT it did load. So... I took the same ancient Config and put it on the new Win11 box and new HB install and it works! (Interesting to note that that same CONFIG STILL doesn't work on the original HB Server. Which is a non issue at this point; may investigate that further another day.) Meantime; new HBServer#4 (I've been through that many hardware upgrades over time) Is mostly functional; just not fully baked in yet. Suspect minor issues only.
(And if it hadn't snowed 3" in AL I would never been house trapped long enough to spend the time on this.)
I have run in to a minor issue. When i try to delete an unused hardware interface or task i get an error message. See attached lousy screen grab. (Same file reference each time but different line #, IIRC. I haven't attempted any other clean-up but would like to weed out some of the old stuff at some point.
(I suspect you got snow there as well. Stay safe.)
Attachments
20250111_080221_Original.jpeg (5.94 MiB) Viewed 22918 times
Looks like your database might still be a little corrupt. You will probably need to delete the data in the DB directly (or send it to me and I can look into it). If you have any questions about the tables and relationships, let me know.
We got some snow too. Probably not as much as you.
Thanks; suspected that much. That brings up a question i had last weekend. I have an old diagram the MS Access version of HBData. But could not find a way to create a similar diagram for the SQL version. I can draw one manually using the DB browser ive been using to look at the tables. But there must be a better way. Can you provide me with a diagram or a way to create one?
I can live with it as-is but it seems like it might be a ticking bomb. I could try to clean up the back end myself but would be thrilled if you are willing to take a look at it. I can snail-mail a thumb drive of CONFIG for you to look into. Or use Dropbox or similar transfer method of your choice. Let me know.
The schema is the same for the new SQLite database. Unfortuntaly there aren't foreign keys to help with the relationships (which is part of the problem you are experiencing), but hopefully most of the table relationships aren't too difficult to figure out.
If you want to Email/Google Drive/Dropbox/etc. the DB to me that's fine. Just let me know what, exactly, you are trying to delete.
The Deleting Things problem... went away. I had just shut down HB and rebooted, for another non HB reason. After rebooting and restarting HB, I created a test device to see if I could delete it. And I could. So I tried again to delete a task that I previously gotten that error message on. Deleted successfully. Same for an unused hardware interface, deleted just fine. Go figure.
Bottom Line? Never mind. Thanks for listening.
This is unrelated to the Delete issue, I think. But I've noticed on several instances where the serial port assignments (Hardware Interfaces) and their enabled status is lost for all assigned ports/devices. I cannot pinpoint the conditions when it has happened, but it has occurred several times since HB has been resurrected. This morning, I tested to see if a HB Quit/launch cycle would trigger it. All OK. Also did a Win warm start without quitting HB first. Also OK. So I have no idea when or why. But when things stop working (lighting tasks, theater controls, blinds and other Arduino controlled things) that's where I check first. And I'll find that all port settings have been lost.
Food for thought.
Weird. I don't see anywhere where the generic serial interface will disable itself once enabled and running. It will disable itself on startup if there is a problem connecting to the com port. Is HouseBot getting restarted when this happens?
Maybe since it's a new machine the windows serial driver is creating virtual ports that are changing port numbers somehow??
When it has happened i dont think windows is “creating” new ports. When i go into HB to add them again the drop down lists the same ports I “discovered” when I first added the serial port (USB->RS232) dongle. A HB restart MAY have been involved; that trail is cold. And I havent been able to duplicate the problem with a HB restart, at least this morning. May try again. Knowing how that operates will help.
(Ive always had problems with RS232 serial ports. Been through several RS232 single and multi port cards. And since have migrated to seemingly more reliable USB dongles. And of course, motherboard RS232 has pretty myuch gone away.)
