Hub, range, documentation

[dan.gealt]

Agree with @vreihen!

[dan.gealt]

Agree! The WiFi to Internet router should be shown on the diagram.

[bernd.wechner]

@vreihen

The problem is that as soon as the specs quantify a range estimate, many people will hold you to it.

Alas as I mentioned, as a profession project manager my experience is also that most professionals will find any excuse in the book not to deliver estimates. Sorry. Just not convinced that people holding you to it is a reason not to deliver estimates. Estimation is all about informing with expectation management, and that is why the three point estimation delivery is so powerful. But even it can be improved in particularly critical or hostile stakeholder environs, but adding a clear explanatory footnote of pretty much everything you have said in more terse and elegant form perhaps. For example: “these are estimates that derive from our field tests, and radio frequency communications are notoriously variable based upon intervening obstacles and surrounding interference. We can’t guarantee any particular range in a given environment without testing it, nor can you, but in typical domestic environments we full expect these … kind of ranges”.

[WFmarketing]

Hi @bernd.wechner Good inputs. Would love for you to experiment with your HUB -> AIR or SKY and let us know what range you find. Be sure to note environmental elements.

Here’s an informative report from @dave.larson1 : Photos of Sky and Installation

[WFmarketing]

All, that was just an old diagram I found on my hard drive. Thought it would be helpful to some. Was never really meant for public critique. Sure we can make it better, but right now we have more important things to do — like ship weather stations to eager backers.

@dan.gealt

The WiFi to Internet router should be shown on the diagram.

@vinceskahan

Also, you might want to show a residential WiFi gateway or something between the Hub and the WF servers, as we’re certainly not talking WiFi from our houses to wherever your servers are…

@vreihen

For the sake of completeness, can you please add the UDP broadcasts to this most excellent diagram???

[WFmarketing]

@vinceskahan

Do the 3rd party integrations happen from the WF servers, or from the Hub ?

Hi @vinceskahan Right now all third party integrations leverage the WeatherFlow APIs to securely pull authenticated data from the WF servers.

That said, we did specifically design the system so that a user could simply swap out the HUB for a proprietary direct local integration to various communication platforms. For example, we can make versions of the HUB with Zwave, Zigbee, HomeKit, Thread, etc. that would talk direct to systems and devices locally. Future stuff.

[bernd.wechner]

@WFmarketing Will do. Have to wait for batteries to arrive first ;-). Ha, ha, I didn’t even get an email warning me the kit was shipped and to order batteries now. It just turned up in the mail one day. A surprise, out of the blue, given how long it’s been since I backed it. Thats aid, unlike some cruddy crowdfunded projects it has delivered and not disappeared on us! That alone is worth kudos slowly, failed projects becoming so seemingly common. But yes, I look forward to plugging in batteries when they get here , setting it all up and then checking site options. I expect my focus will be on testing my desired sites, but I may feel a desire to take a unit for a walk down the road to see how far I get before I lose contact with the hub, if there’s a good cue either end when that happens.