Can you give me the link to where this is mentioned? I did a search and can’t find it.
It’s on the right side of the Kickstarter and Indiegogo page. Look for Tempest - Storm & Fire Ready Kit.
2 Likes
On Kickstarter and Indiegogo sites, the section listing Tempest Storm & Fire Ready Kit is grayed out.
1 Like
I think it may be disabled because both campaigns are closed. That’s just a guess.
2 Likes
It’s in this thread, post 7 above:
1 Like
Thanks DSJ. right now, those campaigns only let you get a full system. My hope would be that once you have them shipping, I can buy just the pro hub to use with my tempest station to get the HomeKit support. Hopefully that will be affordable. I don’t care about the cellular support.
Given that an email to WF for ordering just a single component is all it takes for current products (and some older ones), I would be shocked if you couldn’t just purchase the “pro hub” when it becomes available.
Yep - that’s my hope. 
1 Like
I contributed to the “Storm and Fire Ready” Kit campaign on Indiegogo and also run HomeKit, so I’m looking forward to this integration in the future!
Some handy automations - shutting sprinkler off if it rains and shutting off A/C if dew point drops below a certain level.
1 Like
Would be awesome if it included an ethernet port so we can avoid any wifi issues and if it was PoE that would be double awesome.
4 Likes
I’d be interested to know what any planned HomeKit support would expose to HomeKit and how it could be used. I was about to buy a Netatmo weather station (which supports HomeKit) until I discovered that the rain sensor and anemometer modules (potentially the most useful data for automation) don’t feed into HomeKit, so you’re limited to readings like temperature and humidity. Furthermore, it seems like HomeKit isn’t actually able to use any of these readings for event triggers. I’m not sure if this is a limit of Netatmo’s implementation or of HomeKit itself, so I’m trying to work out if it’s worth waiting for a HomeKit version of Tempest to be available in the UK or if that’s going to have the same restrictions.
1 Like
Hi Neil. You have hit on a point that has been clear to us for some time, but difficult to explain to users: HomeKit is not yet very useful for weather data. The short answer is that we intend to expose whatever parameters or “characteristic types” the Apple HomeKit ecosystem supports.
Now, as you have noticed, that list of types is not heavy on weather parameters. In fact, it’s not really aimed at outdoor parameters at all. The three possible candidates at the moment are temperature, humidity and light level (although, their “light level” is more about the setting value of an artificial light rather than the observed value of natural sunlight). Still, we expect to populate those three types with values from the Tempest system.
We also intend to expose all other weather parameters from the Tempest system to HomeKit via custom characteristic types. Apps must know about these custom types in order to make use of them, however, so they have limited functionality unless & until Apple adds them as standard types.
Meanwhile, regardless of the fate of HomeKit, we are strongly committed to supporting the Apple ecosystem in general. We have recently added Siri shortcuts to the Tempest iOS app, and we have iOS Widgets, Apple Watch and Apple TV on our road map (in addition to HomeKit).
We would actually love to help Apple define the set of weather characteristic types for HomeKit. And as members of the National Mesonet Program, we have a lot of experience defining data standards in the meteorological space. So, if you know anyone working in Apple HomeKit, tell them about us!
4 Likes
Thanks for the very comprehensive answer. I guess my concern would be Apple implementing support for other data (e.g. wind speed) in HomeKit in the future and being stuck with a device that only supported legacy HomeKit data (e.g. temperature), but I guess if a device is HomeKit certified, you can still expose new data to HomeKit now even if at this time, it’ll just ignore it? Or would you need to understand Apple’s device-specific HomeKit implementation before you could bake it into an existing product in anticipation?
Right, my understanding is that you can add custom characteristic types (like wind & rain) but the Home app will ignore them and other apps must build in support directly for them.
You would, but presumably we would be able to add support for future characteristics with a firmware update (not a hardware change).
If, for example, we added custom support for wind & rain and other parameters, and then Apple later released official support for those parameters, we would be able to support them as well with a firmware update. That’s the hope anyway - no guarantees when it comes to the HomeKit spec!
Out of curiosity, what is it you are trying to do? Maybe it can be done without HomeKit.
At this time I don’t have a specific use-case in mind (so I need to be careful I’m not wishing for something that I’m never going to have a practical use for), but I can see potential for this type of data, even if it’s very basic (e.g. turn the garden sprinkler off if it’s raining, send me an alert if the wind speed reaches a limit).
I’m trying to move more of my home automations into Home now it’s beginning to mature (slightly!) so I’m not having to deal with multiple manufacturers’ apps and services like IFTTT. Besides, I quite like the Applesque simplicity of HomeKit, despite its limitations (which are maybe good for reigning-in some of my automation-for-the-sake-of-it ideas). However, even if Apple do expand to support weather stations, I do wonder how useful they would be as event triggers given that HomeKit data has no historical context - if a single drop of rain falls on a sensor, I suspect HomeKit would consider that as “rain detected” even if it was the one and only drop all day. Even if HomeKit could process accumulated rainfall, hitting a 10mm total over a 24hr period gives no indication of how heavy it was actually raining when the device hit that threshold - 9.99mm could have fallen much earlier in the day. I guess it would really depend whether HomeKit was pulling raw or derived data fields from the devices.
Anyway, it’s somewhat academic right now until I can get my hands on a Tempest in the UK 
2 Likes
The free Eve app can apparently get 27 different weather observations and weather forecast values out of this HomeBridge plugin, which also offers some hackish mappings into fake (virtual) devices to access some of the unsupported values in Apple’s Home app:
If you do not have HomeBridge installed yet, I highly recommend using the HOOBS free Raspberry Pi Linux distro:
I’m running HOOBS in a Docker container on my Synology NAS, as a bridge between HomeKit and my Hubitat home automation system. With all of the plugins available for HomeBridge, the Hubitat could almost just be a Z-Wave bridge.
Speaking of plugins, feel free to write one for the WF PWS and forecast APIs, using the above as an example…
2 Likes
Add me as well, new Tempest owner here.
Those 3 specifically would be useful to me. I will control shades based on outside temperature and radiance for example.
For the custom attributes, am I able to use those to control automations in Homekit directly?
You actually can’t use those three parameters yet in the Home app to trigger actions. You can only view them. You need a third-party app to do anything useful with those three parameters.
No, you would need a third-party app that was aware of the custom attributes or a customizable solution like HomeBridge.
Both of these issues are what make HomeKit nearly useless for home weather stations at the present time. Services like IFTTT are much more useful.
1 Like