Multiple versions using external shard database

[hamanjam]

I have 2 separate printers with separate Raspberry Pis. When I created the external database and attached both instances to share filament history, I noticed when I start printing with one instance, the other will show that spool selected as well. When I change the active spool on one instance, the other instance shows the same spool as the active and usage gets mixed up.

[ericus256]

Also see #106. I wonder if this used to work before and only broke more recently? I have been struggling with this exact problem since setting up the database method a couple of days ago.