johnnyt Posted July 2, 2022 Posted July 2, 2022 Installed this NS for my new Tempest Wether Station yesterday and am getting the following error: 2022-07-02 08:39:22,072 Thread-730 udi_interface ERROR weatherflow:forecast_query: local variable 'value' referenced before assignment I'm a bit confused about the idea of putting my station ID in twice but if I don't put it in as local I get a message that at least one must be entered. Below are my settings (I deleted token for screenshot but there is one and am not getting any error messages about that). What am I not understanding needs to be done?
bpwwer Posted July 2, 2022 Posted July 2, 2022 2 hours ago, johnnyt said: Installed this NS for my new Tempest Wether Station yesterday and am getting the following error: 2022-07-02 08:39:22,072 Thread-730 udi_interface ERROR weatherflow:forecast_query: local variable 'value' referenced before assignment I'm a bit confused about the idea of putting my station ID in twice but if I don't put it in as local I get a message that at least one must be entered. Below are my settings (I deleted token for screenshot but there is one and am not getting any error messages about that). What am I not understanding needs to be done? The configuration looks right. Looks like a bug in the node server is causing that error. Many people have more than one WeatherFlow station so the node server needs to know which station to pull data from and which station to get forecast data for. They don't have to be the same station.
johnnyt Posted July 2, 2022 Author Posted July 2, 2022 3 hours ago, bpwwer said: The configuration looks right. Looks like a bug in the node server is causing that error. Many people have more than one WeatherFlow station so the node server needs to know which station to pull data from and which station to get forecast data for. They don't have to be the same station. I'm new to the tempest so i may be missing some key info but I can say I'm getting both the data from my station and forecast info on my app and when pointing to the web page for my station and this is with having bought only one station. I'll email tempest support to see if maybe I have two separate stations ID to provide - one for spot data and one for forecast info
bpwwer Posted July 5, 2022 Posted July 5, 2022 On 7/2/2022 at 12:12 PM, johnnyt said: I'm new to the tempest so i may be missing some key info but I can say I'm getting both the data from my station and forecast info on my app and when pointing to the web page for my station and this is with having bought only one station. Other people, have more than one station, not you. The separate forecast and local entries are for them. In your case, since you only have one station, it is the same station number that gets entered for both.
johnnyt Posted July 5, 2022 Author Posted July 5, 2022 50 minutes ago, bpwwer said: Other people, have more than one station, not you. The separate forecast and local entries are for them. In your case, since you only have one station, it is the same station number that gets entered for both. I did enter the same id for both and got the error. i also heard back from tempest tech support and there isn't a separate station ID for forecast. only the one associated with the weather station. In an urban setting one generally only needs one station. certainly I don't need 2 stations. will you be fixing things for those of us with only one station or is this NS only for people with more than one station?
bpwwer Posted July 5, 2022 Posted July 5, 2022 Version 3.0.21 fixes the bug you were seeing. If you refresh the store you should see that version. Then restarting the node server will automatically install it. 1
johnnyt Posted July 9, 2022 Author Posted July 9, 2022 So not getting the error anymore (after upgrade) but am also not getting station data, and top node will go from "Hub Seconds Since Seem" of 0 right to 1657295307 and move up from there (since screenshot I took the number has gone up to 1657295727). See screenshots below
bpwwer Posted July 11, 2022 Posted July 11, 2022 In general, there are no known issues that prevent node servers from running or reporting data except for miss-configuration. Your configuration looked correct. The ETo might cause forecast data to not display or it may be because it doesn't have any data to calculate ETo yet. The second listing is normal for a new station as it tries to get precipitation data for the year, but you don't have any historical data yet. Neither would (or should) cause it to not have or not display data. Please attach or PM me the full log, ideally after you've changed the log level to debug and restarted the node server.
johnnyt Posted July 13, 2022 Author Posted July 13, 2022 On 7/11/2022 at 4:44 PM, bpwwer said: Please attach or PM me the full log, ideally after you've changed the log level to debug and restarted the node server. I set log level to debug, restarted NS, and waited at least long poll (600) seconds (I assume). Attached is log. WeatherFlow_7-13-2022_54818_PM.zip
bpwwer Posted July 13, 2022 Posted July 13, 2022 From what I see in the log, the node server is working correctly. It's not reporting any data to the ISY because it's not receiving any data from your hub. Either the hub isn't working or something on your local network is preventing the hub's data broadcasts from reaching the node server.
johnnyt Posted July 14, 2022 Author Posted July 14, 2022 Oh, I see. I think it's a VLAN issue. I have all my wireless IoT devices (a.k.a Internet of insecure things) on a separate VLAN (100) from ISY - and ISY is on separate (more trusted) VLAN (200) than my regular computers (VLAN 0). I do have firewall rules that allow all VLANs to connect to VLAN 100, but block VLAN 100 from connecting to other VLANs. How does the Node Server connect to the Tempest Hub? I'm wondering about the mechanism the NS uses because I noticed I didn't have to put in an IP address for the hub. I wonder if being able to put in the hub's IP address would solve the problem, and, if so, if you would consider adding that option? As you know, there are many horror stories of IoT devices not getting patched when critical vulnerabilities are discovered so I would think it's important to allow for segregation of those onto their own separate subnet or vlan.
bpwwer Posted July 14, 2022 Posted July 14, 2022 17 hours ago, johnnyt said: How does the Node Server connect to the Tempest Hub? It doesn't. The WeatherFlow hub uses UDP broadcasts to push it'd data to the local network. The node server just listens for those broadcasts. I don't know anything about VLAN's and their configuration so I don't know how or if UDP broadcast packets would route through them. The WeatherFlow hub doesn't have a way to connect to it directly via a TCP/IP address.
johnnyt Posted July 14, 2022 Author Posted July 14, 2022 I did some packet sniffing on port 50222 (default "listen" port) and the "Destination IP" for the traffic from the hub is 255.255.255.255, which can't really be pushed to another VLAN or translated to the Polisy's IP address. Or at least I don't think it can because what I've tried that's worked in other situations (e.g. NAT'ing 192.168.100.1:50222 to 192.168.200.1:50222, or subnet to subnet) didn't work for this. Unless someone reading this knows more about networking than I do, I think I may have to stick ISY & Polisy on the VLAN with all the insecure IoT devices. I guess they are kind of IoT devices anyway.
Bumbershoot Posted July 14, 2022 Posted July 14, 2022 1 minute ago, johnnyt said: Unless someone reading this knows more about networking than I do, I think I may have to stick ISY & Polisy on the VLAN with all the insecure IoT devices. I guess they are kind of IoT devices anyway. Keep in mind that your Polisy is running FreeBSD. With TPM enabled and strong passwords, your Polisy/ISY will likely be the least of your worries on your IoT VLAN.
Recommended Posts