March 15Mar 15 Having an issue when I have my Tempest Wx Station setup and showing connected in Ployglot 3x, but no data is populating in the EISY (6.0.4) Device display.WeatherFlow(1)Current Status: ConnectedCurrent Version: 3.0.32 / Standard [Production]The EISY has a CAT-6 network connectionThe Tempest wx Station is connected via Wi-Fi.However, both are on the same subnet 172.16.101.0 /24Checking the WeatherFlow Log, I see the errors listed below...Not sure if these are preventing other data from being displayed on the EISYAny thoughts on how to investigate further or address?Pete2026-03-15 17:12:03.076 Thread-6 (udp_data) udi_interface INFO derived:updateTrend: TREND 1021.470000 to 1021.5300002026-03-15 17:12:03.076 Thread-6 (udp_data) udi_interface INFO derived:updateTrend: TREND 1021.470000 to 1021.5300002026-03-15 17:12:03.076 Thread-6 (udp_data) udi_interface INFO derived:updateTrend: TREND 1021.470000 to 1021.5300002026-03-15 17:12:03.076 Thread-6 (udp_data) udi_interface INFO derived:updateTrend: TREND 1021.470000 to 1021.5300002026-03-15 17:12:03.077 Thread-6 (udp_data) udi_interface ERROR tempest:update: Failure to calculate Air temps: unsupported operand type(s) for /: 'NoneType' and 'float'2026-03-15 17:12:03.077 Thread-6 (udp_data) udi_interface ERROR tempest:update: Failure to calculate Air temps: unsupported operand type(s) for /: 'NoneType' and 'float'2026-03-15 17:12:03.077 Thread-6 (udp_data) udi_interface ERROR tempest:update: Failure to calculate Air temps: unsupported operand type(s) for /: 'NoneType' and 'float'2026-03-15 17:12:03.077 Thread-6 (udp_data) udi_interface ERROR tempest:update: Failure to calculate Air temps: unsupported operand type(s) for /: 'NoneType' and 'float'2026-03-15 17:12:03.077 Thread-6 (udp_data) udi_interface ERROR weatherflow:udp_data: Failed to send data to ISY: unsupported operand type(s) for *: 'NoneType' and 'float'2026-03-15 17:12:03.077 Thread-6 (udp_data) udi_interface ERROR weatherflow:udp_data: Failed to send data to ISY: unsupported operand type(s) for *: 'NoneType' and 'float'2026-03-15 17:12:03.077 Thread-6 (udp_data) udi_interface ERROR weatherflow:udp_data: Failed to send data to ISY: unsupported operand type(s) for *: 'NoneType' and 'float'2026-03-15 17:12:03.077 Thread-6 (udp_data) udi_interface ERROR weatherflow:udp_data: Failed to send data to ISY: unsupported operand type(s) for *: 'NoneType' and 'float'2026-03-15 17:12:46.079 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV4 to 2 UOM 572026-03-15 17:12:46.079 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV4 to 2 UOM 572026-03-15 17:12:46.079 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV4 to 2 UOM 572026-03-15 17:12:46.079 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV4 to 2 UOM 57 Edited March 15Mar 15 by pete_balkus
March 16Mar 16 Does Weatherflow data populate in pg3x? Check the error log and the configuration settings in the plugin.
March 16Mar 16 Author Thank you for responding - appreciated...I tried the following to check for Wx Date by doing the following:Open Polygot V3Click on DashboardsClick on NodesClick on NodesStation parameters are listed, but values are all 0 as shown in the table below...I have tried both Local and Remote, and the same result...My station ID key (48909) was obtained from the following command:https://tempestwx.com/station/48909/Any thoughts on where to go from here?PeteNode DetailsNode Name 1AddressNodeDefPrimary NodeHintEnabledIs PrimaryDeleteST-00010151141178tempestcontroller0x00000000truefalseNameDriverUOMValueVariableStation PressureATMPRES1170${sys.node.n001_141178.ATMPRES} Sealevel PressureBARPRES1170${sys.node.n001_141178.BARPRES} BatteryBATLVL720${sys.node.n001_141178.BATLVL} HumidityCLIHUM220${sys.node.n001_141178.CLIHUM} TemperatureCLITEMP170 Edited March 16Mar 16 by pete_balkus
March 16Mar 16 Author Interesting - After letting things sit overnight (11:00 pm to 7:15 am) with no additional changes or restarts, I checked this morning and see that Wx Station data is now available, as shown in the table below.Unclear why things started working....The new problem is that, for some strange reason, the Temp Data is negative??Temp -48.98Dewpoint -49.0However, my iPhone App shows the same thing, so it appears to be a Station HW issue...Always something...PeteNameDriverUOMValueVariableStation PressureATMPRES2330.32${sys.node.n001_141178.ATMPRES} Sealevel PressureBARPRES2330.071${sys.node.n001_141178.BARPRES} BatteryBATLVL722.639${sys.node.n001_141178.BATLVL} HumidityCLIHUM2299.37${sys.node.n001_141178.CLIHUM} TemperatureCLITEMP17-48.98${sys.node.n001_141178.CLITEMP} DewpointDEWPT17-49.0${sys.node.n001_141178.DEWPT}
March 16Mar 16 A few things to check:Are you sure you are using the correct station ID? 13 hours ago, pete_balkus said:My station ID key (48909) was obtained from the following command:https://tempestwx.com/station/48909/Any thoughts on where to go from here?I am not sure what you mean by the statement and link above. If that is your actual station, after the page opens you should be able to click the top near the temperature and see data from your actual device. The landing page is Weatherflow's generic data for your area.Does the Weatherflow app on your phone show correct data? Open the app and click the Tempest symbol in upper right corner for your local data. Do you have correct data? If not, there is an issue with Tempest.13 hours ago, pete_balkus said:Node DetailsNode Name 1AddressNodeDefPrimary NodeHintEnabledIs PrimaryDeleteST-00010151141178tempestcontroller0x00000000truefalseIn my system, my node detail address matches what is listed in the variable, your variable for temperature is blank.13 hours ago, pete_balkus said:https://tempestwx.com/station/48909/In node detail above, you station is shown as 141178, yet your link is showing: 48909. Which is your actual station ID? Go to the app click settings bottom right corner, followed by Stations, station name, status, and then scroll down to Station ID under Hub. Do they match what you have in pg3x?If everything is correct and you are stil having issues, go to pg3x, Dashboard, Weatherflow, Log, and place log in Debug mode. While watching the log, restart the plugin. After it starts up and has some time to collect data, look for errors in log.
March 16Mar 16 Author Update & Next Steps...Regarding station ID - I have Public Data enabled in my Wx Station Setup, so I can send/share my Wx Data to Weather Underground, and the Wx Station data is visible to anyone on the Web. If you look at the two Tempest App screenshots I included with the post, you will see the setup and that the new Station ID created by doing this is 48909.Wx Station Sensor Failure - I also contacted Tempest Support regarding the temperature and Humidity sensor data issue, and it appears that I have had an internal sensor failure. As a result, I have arranged with them to obtain a replacement Wx Station unit to collect this data.I will report back on the overall operation once I install and test the replacement Wx Station.Pete
March 16Mar 16 The plug-in does not need the station to be shared publicly.When configured to get local data, it is getting the data the hub is broadcasting over your local network. There are only three things that can interfere with that. 1) the broadcast won't typically cross subnet boundaries (and based on your initial post, that is not a problem). 2) A firewall setting is blocking the UDP port internally (not something you'd typically set up). 3) Another program running on a machine on your network opens the address/port in exclusive mode (meaning nothing else can then open that address port). When configured for remote, you're requesting your data from the servers (and authenticating with the API key). So again, public sharing not needed. The "Station ID" and device address are two different things. With a Tempest, it's most likely a one-to-one relationship. However, with the early weather stations, a Station ID" would usually have two device addresses associated with it -- an Air device and a Sky device.The plug-in uses the Station ID to query the WeatherFlow server to get the device addresses, your preferred units, and historical rain data when it starts. If you configure a wrong/invalid station id, I don't think you'll get any nodes created, for sure you won't get any device nodes created as it won't be able to find any.When you get a replacement Tempest, it will have a different device address so you'll want to delete the node for the currently one from the eisy using the admin console. It's been too many years since I got a replacement Tempest to remember the exact steps. It may be easiest to simply copy the token, delete the plug-in, and then re-install it.
March 17Mar 17 Author Thank you for the response and information shared - appreciated.I understand that the IoX Plug-in does not require sharing the Wx Station data publicly; however, in my Wx Station use case, the Wx data has multiple uses, some of which require public data to be enabled.I also appreciate the suggestion and info you provided on configuring the EISY to access and use the replacement Wx Station.I will keep you posted...Pete
Saturday at 06:42 PM5 days Author Tempest Wx Station Replacement ProcessPer a conversation with Tempest Customer Support, here is the procedure I used to easily and seamlessly replace my defective Tempest Wx Station with a new replacement unit.The new/replacement Tempest Wx Station is now providing full, correct data to my EISY R2.PeteThe process of connecting the new Tempest Wx Station to my current Tempest Wi-Fi Hub was:1. Unmount and turn off the old/defective Tempest Wx Station.Turn on the new Tempest Wx Station.The LED should eventually slowly blink green, indicating it is in pairing mode.If the LED does not stay blinking green, press and hold the LED button until it flashes to reset the device.3. Open the Tempest App, go to Settings > Stations > (choose your station) > Manage Devices > (select the device you are replacing) > Advanced > Replace Device.4. The new device ID will appear on screen. Choose the new device to finish connecting it.5. The LED on the base of the Tempest Wx Station should flash green and then go out, indicating it has successfully paired to the Hub.6. Check the Tempest app and verify that the current observation data is displayed.7. Login to your EISY > Plugins > Launch Polyglot V3Select Dashboard > Nodes > Restart8. Verify that the Log data shows new data coming in from the Tempest Wx device9. Verify that the EISY Weatherflow device displays data from the Tempest Wx deviceNote: Using the above procedure, the new Tempest Wx Device will retain the old device's name (which will be defaulted to the old serial number). This makes replacement seamless with no Plugin changes required…
Create an account or sign in to comment