search

openweave / openweave-core

openWeave is a home area network application protocol stack designed to enable asynchronous, symmetric, device-to-device, device-to-mobile and device-to-cloud communications for control path and data path messaging.
Apache License 2.0
233 stars 106 forks source link

Nest weave sucks - range issues #407

Closed sebastienbo closed 4 years ago

sebastienbo commented 4 years ago

Hi,

I feel very frustrated with nest weave. When I used zwave I had the benefit of never having network issues, becausse when a device was out of range, the zwave protocol relayed the message untill it got to the recipient device that wass out of range.

But with my nest thermostat I notice that 12 meters is not enough to contact my thermostat wirelessly (which is a requirement for the opentherm...doesn't work wired...) However my whole house is full of nest protect smokedetectors, why do they not relay between my thermostat and heat link ... and why does opentherm does not work with the wired setup? and why can't the heat link connect via wifi.

Is there some nest weave extender available for such a situations or is it just crap and do i need to look for another solution/brand?

jaylogue commented 4 years ago

Hi Sebastien,

I'm sorry to hear you're frustrated with the performance of your Nest Thermostat.  Unfortunately, I don't think the developers of OpenWeave can help you.  OpenWeave is a communication framework that is used by Nest products to carry out application-layer communication between devices.  It sits above network layers like WiFi and Thread.  As such, it is subject to the range limitations inherent in those technologies, as well as any local effects arising from the environment (e.g. physical obstructions).

Rather than filing an issue here, I would suggest reaching out to the Google Nest support team at https://nest.com/support/contact-us/. They should be able to help assess the issues you're seeing and find a solution.

Thank you.

sebastienbo commented 4 years ago

Well my point was, that the waring protocol would require enhancements by using neighbours to send messages to a destination, jut like zwave can.

Contact nest didn't help because they told that the caring protocol openweave doesn't allow such feature and they use open weave. basically they are saying its openweavess limitation, not nest.

jaylogue commented 4 years ago

Well my point was, that the waring protocol would require enhancements by using neighbours to send messages to a destination, jut like zwave can.

Thread has this feature as well. Again, this is a feature of the underlying network technology, not of the application layer. (If you're interested, you can read more about Thread at openthread.io/guides).

Contact nest didn't help because they told that the caring protocol openweave doesn't allow such feature and they use open weave. basically they are saying its openweavess limitation, not nest.

It is unfortunate that they are confused in this way. If you have a contact for who you spoke with, I can investigate further.

I think the fundamental problem you're facing is that Nest does not offer a Thread mesh router product that can act as a range extender for your thermostat. The Nest Connect product does exactly this. Unfortunately its not available for sale in the EU.