Google Sheets Publish Different Tabs For Each LoRa Device

Is your feature request related to a problem? Please describe.
The SitkaNet project is using Loom to collect data on several LoRa nodes, send this data to a LoRa hub, and then publish this data to Google Sheets. One aspect of this feature set is that the Google Sheet contains a tab for every device the hub is receiving from, limiting the confusion of data points in each sheet.

The current Google Sheets publishing implementation determines which tab to use by looking at the device ID stored in the LoomManager instance:

Loom/src/PublishPlats/GoogleSheets.cpp

Lines 77 to 81 in a797aab

    
           if (tab_matches_dev_id && device_manager) { 
        
           	char buf[20]; 
        
           	device_manager->get_device_name(buf); 
        
           	snprintf(buf, 20, "%s%d", buf, device_manager->get_instance_num()); 
        
           	network->print(buf);

This device ID is not updated when the JSON is changed, and as a result does reflect a the device ID of a LoRa packet being received from a different device. This was intentional behavior, as it doesn't make sense to change the device name of the hub every time we receive a packet from the child—one consequence of this, however, is that a single device can never publish to a different tab, regardless of values in the JSON.

Some possible solutions to this problem include:

Redefining how ComPlats put messages into Loom (perhaps into another array in the contents array?), and then creating tabs based on that structure.
Allowing the device name to be changed in the JSON at any time, and realizing the consequences for this in other modules (Spool?).
Changing specifically Google Sheets publish to pull the device name from the JSON, and pushing a general solution until later (not recommended).

I've implemented the third bullet for @maxchu765 in the SitkaNetV2 branch as a temporary fix (8302340), but I believe we should consider implementing one of the first two bullets for the rest of the lab.

Another proposed solution is to keep a nodeID on Loom Manager with a specified value that corresponds to the Hub. This would be the simplest solution, but as with bullet 1 would require addressing this new value in all other publishing platforms.

Can we have a description of how this is now handled in Loom3?

	if (tab_matches_dev_id && device_manager) {
	char buf[20];
	device_manager->get_device_name(buf);
	snprintf(buf, 20, "%s%d", buf, device_manager->get_instance_num());
	network->print(buf);