A solution to display the values of two xDrip on one watch

[atomphil]

Me and my little son both have the same hobby: diabetes type 1 :-/ To keep an eye on his glucose level, I run a second xDrip on my phone (via xDrip variants) in parallel to my xDrip, which is connected to the xDrip on my son's mobile phone via Nightscout and xDrip Sync Follower.
I use Watchdrip to display my values on my watch. It would be great if I could see not only my values on the watch, but also those of my son.

A solution would be to have an xDrip version with a different name, like xDrip variant, so that it can be installed in parallel. This version would generate an image like the old xdrip-miband (from its own background image and json file). However, the generated image should not be packed into a watchface and sent to the watch, but serves as my_image.png as a background for Watchdrip, which then builds the finished watchface from it and synchronises it with the watch.

I am sure that such a solution would be appreciated by all those who need to monitor more than one glucose value.

[bigdigital]

Hi, unfortunately, this would be too complicated to implement. Not sure i could do this. Sorry

[atomphil]

https://github.com/bigdigital/xDrip-miband/tree/miband-integration

Is this the latest source code of the xdrip-miband app? Maybe I can try to build such a version myself.

[bigdigital]

https://github.com/bigdigital/watchdrip this is the latest watchdrip app source. The xdrip app is from official repository

[atomphil]

https://github.com/bigdigital/watchdrip this is the latest watchdrip app source. The xdrip app is from official repository

I would like to look at the source code of your old xdrip-miband app that you built before Watchdrip.
I am interested in using it to follow my son's xDrip and generate an image with his values, which is then used as my_image.png with WatchDrip listening to my xDrip. That way I would have both values on the watch.
But maybe it is too complicated thought.

Would it be possible to extend Watchdrip so that it receives the values from multiple xDrip instances and then displays them together (via an appropriate custom WF and json-file, of course) - that would of course be much more elegant and probably more universally usable for others.