Win10, Eclipse Oxygen, 3.0.0b3 SDK, va3 with 2.40 FW
In the past, a widget on the va3 could access the Tempe by way of Sensor in a widget. It was a bit tricky, as it can take the Tempe a minute or more to connect, and the widget timeout on the va3 is pretty short (20 second?), but the timeout could be reset by just tapping the screen every 15 seconds until the tempe connects. watch-apps (device-apps) still function normally with regard to getting data from the Tempe.
To reproduce, this I've attached a slightly modified version of the Sensor sample in the SDK. I commented out the graphing part, and changed heart-rate to temperature. The attached version is set as a watch-app.
Sideload to a va3, and observe it works with the Tempe (Tempe must be a paired sensor). There will be the delay to connect, and the data, as expected, will update every minute.
Change the project manifest.xml to make this a widget instead of a watch-app, and sideload again. Swipe to the widget, and tap the screen every 15 seconds to prevent the widget from timing out, and after a few minutes, you'll see the Tempe never connects with data.
I'm wondering if they disabled the Tempe for widgets on the va3 due to the time it takes to connect along with the short widget timeout, but that makes things inconsistent with other devices, and if that's the case, it needs to be documented. Or it could be a bug in the FW.
Attached is the project