I'd appreciate a more detailed description of your setup (setups ?)
Do you run one MB instance or three (one could read this from your description) ?
To me, what you write, looks like 3 MB instances, one with 7 stations, one with ? stations and purple air sensors and one with ? stations including a GW1000.
Or do you run one MB instance with 7 stations, where the GW1000 is station #2 and you also have a purple air station ?
Could you be clearer on this ?
What platform(s) do you run MB on ?
Nano SD, MB Pro, MB RPi ?
I would personally guess a RPi setup, as a multi-station setup is difficult for a Pro (depends of course on the number of sensors all-together and the archiving intervals chosen). My MB Pro fight with a more than one station setup (30 sensors + minute data archiving though). My RPi4 handles two GW1000 with 30 sensors each and minute based database recording (archiving) without any complaints. Even the meanwhile 1.5 GB large database is backed up in two minutes (where probably the USB2 protocol is the limiting factor)
So I am wondering if this is a logger issue or a load issue (=hardware capacity issue). My MB Pros started behaving in a very weird manner with all types of symptoms including spontaneous reboots, logger crashing etc. when running with more than one station (GW1000) and hourly database backups. With only one station they run +/- issue free.
EDIT (addition):
"THE METEOBRIDGE DOES NOT HAVE ANY ISSUES IF I REMOVE THE GW1000 FROM STATIONS."
This only means that the MB doesn't have issues after you remove the GW1000. That does not necessarily mean that the GW1000 presence is the primary cause. In order to exclude that (partially), you would need to remove your Davis and leave the GW1000 on
(and add a 2nd GW1000 or another (non-Davis) station).
On the other hand, there are many joint Davis/GW1000 implementations which run flawlessly.