Yes. If you are already using Hubitat Variable Connectors (the devices that mirror your Hubitat Variables), those devices also expose commands to update the variables like setVariable(value)
I am, but don’t see where it exposes commands to update the variable. (this “seems” like the simplest approach of the options you listed…
It sems like that connector variable (Day High Temp) “should” be listed in my SharpTools “Things” after a reauthorization, (like a device), but it is not.
Yeah, a Connector is basically just a ‘Thing’ that mirrors the specific Hubitat Variable’s state bidirectionally.
So you have to explicitly ensure the variable has a matching Connector ‘Thing’, then you have to explicitly authorize that Connector ‘Thing’ to the associated app (SharpTools in this case). Usually that involves going through the authorization flow again and making sure that new Connector device has the box checked next to it so it will be authorized.
For use-cases where you want to expose the Hubitat Variable to another app, especially for read access, I would agree.
If you only ever want to write to the Hubitat variables, then the Rule Machine setHubVariable approach is probably more efficient as you don’t have the extra work of setting up the Connectors (assuming you don’t need them elsewhere) and can just update any Hubitat variable you want without additional Connectors, authorizations, etc.