Hi there folks,
finally installed my Tempest and i’m loving it.
Unfortunately i am only able to use it locally over bluetooth as i’m unable to connect the hub to my Wifi network.
I have triple checked the following:
the SSID is the correct one
it is broadcasting on 2.4 ghz
The password is correct
Unfortunately the app is returning an Error Code 1006.
I have a strong hunch that this failed auth message is due to the fact that my wifi network is setup to ONLY allow WPA3 auth.
Unfortunately for security reasons i cannot downgrade this or establish a separate guest network with WPA2.
IF(and this is speculation on my part as i haven’t pulled the auth logs form the wifi AP yet) the Tempest Hub is confirmed to NOT support WPA3 then i implore the team to consider adding support to it as its adoption is only gonna increase in the future.
I mean, to be perfectly honest i could with some fiddling create a completely isolated ad-hoc network with WPA2 auth just for the Tempest but i would very much prefer to NOT have to do that.
I had a look and i can’t find a single reference to WPA3 being unsupported in the knowledge base eg:
They do mention Enterprise auth being incompatible which is perfectly fine tbh as not really widely used in a consumer/residential env.
On the other hand WPA3 being unsupported(again,if confirmed) is a pretty big deal imho especially since wifi is the ONLY connection option and i certainly can’t be the only one with a network configured to exclusively use it ; i’m sure it’s gonna be a much more widespread issue in the near future as more APs adopt it by default.
Would love to hear from the folks at Weatherflow to shed some light on this as i was unable to pull detailed auth logs from my APs(seems like failed auth events are not logged) to confirm that this is indeed the root cause of the Error Code 1006 message(altho it seems very plausible judging by the error codes table available here https://help.weatherflow.com/hc/article_attachments/9159541794331/Tempest_App_Error_Codes.pdf ).
And you’re def right that all of this would be completely moot if the hub had an RJ45 port.
All of this being said i am perfectly happy to keep using it locally over Bluetooth but would appreciate getting to the bottom of this.
I suspect that the internal chipset (and/or its drivers) does not support WPA3.
One thing that I would suggest trying is to put up a 2.4 Ghz only SSID if your current one has both frequencies broadcasting with the same name. There are known issues with the wifi chip in the hub when the same SSID is broadcast on both frequencies, possibly due to band steering on some access points…
Thanks for the suggestions!
Created a new isolated vlan and assigned a new wifi network to it(2.4 ghz broadcast only so no band steering, WPA2-Personal).
Hub was able to connect instantly.
Not really happy with the(at this point i’d say confirmed) inherent WPA3 limitation but i’ll make do.
I concur with @vinceskahan ! Remember back in the “Field Test” days. . .they kept us informed very (quite) often. After about the middle of 2022. . .things pretty much fell silent.
e.g. Q#1: what’s the latest Tempest app firmware (for Android)?? A#1 have to go and “hunt it down” at Tempest for Android weatherflow.github.ioTempest for Android
Ah NO! It’s FWR (FirmWareRevision v176) ! ! (v143 was from the early 1st Production run of Tempest devices in 2020 — the ones with the Blue “North Marker” and the Blue WeatherFlow logo on the backside!
Thanks for the information, y’all. I just noticed at the top of this post you can VOTE for this - maybe it’s to get it in front of the dev team? Couldn’t hurt to up-vote it.
I recently purchased the new Tempestº Purple, which I was told by support was WPA3 capable. I began the setup process only to find that I’m unable to connect to my Netgear Orbi mesh network, even after trying all the suggestions in the FAQs and Forum articles (restart router and hub, disable 5 GHz, turn off satellites, remove non alpha-numeric characters from password, stand on my head and spit quarters, etc). I think it’s great that they’ve enabled WPA3, but haven’t fixed the issue with connecting to some wifi systems. I’m getting the 326-08 error - 326 = “Set WiFi timed out” and 08=“android”. This is unhelpful. Any other suggestions before I send it back?
Yes, wait for the update from the Android app. Yesterday it was discovered Android once again change things under the hood and broke the app. Coders are working on a solution. If you have eventually an iOS device you can set up the station via that device and it’ll work (WPA3 included).
Sorry, solution is coming. Just give the coders some time to write the solution and test it.
@eric - why doesn’t your company publish a page similar to this one that shows status of your services and notifies your data providers (those that purchase your hardware) of these issues? Is there a place like this in the Weatherflow or Tempestº ecosystem? Can we sign up for such alerts? Is there a pinned forum thread for such things?
