Is it possible for the hub to transfer outdoor temperature from a physical sensor to a thermostat?


The thermostat is currently under development, and we are willing to have an external outdoor temperature to be pushed to our device. The source could be a weather app or a sensor.

We are currently investigating the possibility to use physical outdoor sensors.

If you’re building your own, zigbee is the usual choice for outdoor sensors over zwave. For one thing, it operates better through rain.

I know that, but we are currently developing a Z-Wave platform.

Do you know if it’s possible to query a Z-Wave hub for an external temperature?

Or is it possible to configure a Z-Wave hub to send the outdoor temperature to its devices?

Same answer as above.

What about SmartThings hub?

The Keep Me Cozy II Smart App is to have another sensor to replace the embedded sensor in a thermostat.

This is not want I want to achieve.

The thermostat I’m developing has its own internal sensor to display the indoor temperature.

But on the LCD, there is a place to display the outdoor temperature. The thermostat will not come with an extra sensor. It will rely on the network to provide the outdoor temperature.

My questions are the following:

  1. Can SmartThings hub send the Outdoor Temperature received from a Multi-Sensor device to a Z-Wave Thermostat Device on its network?
  2. Can SmartThings hub send the Outdoor Temperature fetched from a weather service to a Z-Wave Thermostat Device on its network?

I just answered this in post 5. Weather as a service in SmartThings typically uses Weather Underground.

See, for example:

Or this code example:

I installed the Smart Weather Station to my SmartThings hub.

It does display the temperature on the SmartThings app, no issue.

But what I want to achieve (and this is where I need support) is how to make the SmartThings hub to SEND that temperature to a thermostat device?

That sounds more like a SmartApp coding question than a device integration question. Perhaps if you ask in that category you’ll get more answers.

It may also help to understand that the version 1 ST hub is just a radio station. It receives strings of data and it sends them out.

The logical processing of that data occurs in the ST cloud.

So you’re asking a coding question, not an antenna question. Cloud, not hub.

Well, yes, I may ask for the SmartApp coding if there is no other solution.

But it’s more of an integration question: is it possible to do what I describe?

Is is possible, in a SmartThings environment, one way or another, to have a temperature being sent from one device to another through the SmartThings hub?

Can the SmartThings hub receive a temperature from a device and transfer it to another device?

These are the answers I’m looking for.

I’ve already proven that it works using the direct association, but I’m limited to 5 NodeIDs and it does not involve the hub.

The radio will send whatever bytes you tell it to send. It doesn’t know or care about their content. it just has to fit a known message format.

What’s the zwave device class your thermostat will be certified as?

The thermostat will be a generic thermostat v2.

I don’t know how SmartThings is designed under the hood.

So far, I’ve seen many devices displayed altogether on the SmartThings mobile app, but I haven’t seen any interactions between the devices THROUGH the hub.

I’m looking for a way to tell SmartThings to take temperature from device A and send a temperature report to device B.

SmartThings is certified as a zwave controller for the Basic command set. That’s what’s “under the hood” for your situation. You’ve read the ST developer docs, right?

If your device is a zwave certified thermostat, you can send it a supported zwave command.

How you get the content of that command is up to you. Typically through a SmartApp, which is why this is a coding question.

The hub just passes on the messages, it doesn’t create them. So you more likely have a SmartApp that gets the temperature from Device A, then formats a message for the hub to pass to Device B. The hub just passes along the messages the SmartApps tell it to pass along.

1 Like

Thank you @JDRoberts. I will pass along my questions into the Smart App forum.

1 Like

Gosh… Quite a long thread when the answer is YES.

Any Devices (“Things”) connected to your SmartThings Account (the hub is just a transmission layer and doesn’t do any processing) can interact with each other, but ONLY through one or more SmartApps. (Devices cannot (or should not) directly interact with each other.)

This includes reading the temperature value of a temperature sensing device and sending it to a value displaying device.

The other thread gives a two line example: subscribe to the sensing device, and execute a Comman, or perhaps a direct Attribute update Event, to the display Device.

1 Like


Devices certainly can interact directly. Association in zwave, Binding in zigbee.

It’s just that’s not typically how you pass values like temperature.

(See what happens when you mix coding and device integration discussions! :stuck_out_tongue_winking_eye: )

Yes, but I guess I mean within the specific context of within SmartThings.

I just don’t know what terminology to use to be accurate, but I was attempting to simplify the model.

SmartThings Device Handlers cannot (or should not, per Device Type certification guidelines) interconnect Devices directly with a few very limited exceptions.

Associations & Bindings are not SmartThings features or tools, as far as my definition is concerned.


See the last section on this page. It’s definitely part of the ST codebase, as it should be. (The Minimote, among other devices, wouldn’t work in SmartThings without it.).

Perhaps a better or just another way I can say it:

Nearly all of my Device (“Thing”) related discussions are protocol agnostic.

Thus, since a ZigBee Device cannot be directly associated with a Z-Wave device, the concept of Association does not apply in my context. Ever.

Yes… as per your documentation reference, there are associations for special cases within a protocol. But I focus on the abstraction of Things independent of protocol, such that the end-user and SmartApp developer properly can ignore the communication protocols and other physical attributes of things, and only deal with the abstraction provided by the Device Type (ideally abstracted to the standard SmartThings Capabilities.

It’s not about being right or wrong – it’s about context.

Which makes perfect sense in a coding context for a SmartApp developer.

But not in a device integration context or for a device handler developer.

This topic is in the Device Integration category. We have to consider specific protocols.

But the answer to the OP’s question will be in the SmartApp coding category, which is why the second topic has been created over there. All good. :blush: