WeatherFlow not producing data after

[scrutch]

WeatherFlow is connecting but not showing any data.  Was working on 5.7.0 not working on 5.8.0

There is no error indication that I can find

[bpwwer]

Switch to debug level logging and then wait a few minutes or restart the plug-in.  Then download the log package and PM it to me.

[schleigh]

bpwwer, I've got the same problem with no data after update. I hope that this is the log that your looking for.

Thanks

debug 23.log

[bpwwer]

I really need to see the debug log after restarting the plug-in.  

However, from the log, it looks like it's getting a response but all the values are "None" instead of actual numeric values.  I can't really tell if it's getting the response from the local hub or the WeatherFlow servers or both.  

Given that it seems to be invalid data being received from WeatherFlow, it doesn't seem like it has anything to do with the IoX update.

[schleigh]

I hope that this log is what you're looking for. I restarted the plugin and then copied error log. If it's not the update, do you any other ideas as to what happened?

 

WeatherFlow_4-2-2024_14345_PM(1).zip

[bpwwer]

That's a lot more helpful.  It seems to be your Tempest is not sending data to WeatherFlow.

Running the query the plug-in is making, all the data coming back looks like this:

[1712062080,null,null,null,null,20,null,null,null,null,null,null,0,0,0,0,2.39,1,0,0,0,0]

All those 'null' fields should have actual data.  The structure of the returned data is:

timestamp = 1712062080
Wind lull = null
Wind Speed = null
Wind Gusts = null
wind Direction = null
Wind sampele interval = 20
Pressure = null
Temperature = null
Humidity = null
Illumination = null
UV Index = null
Solar Radiation = null
Rain = 0
precipitation type = 0
Lightning striks = 0
Lightning distance = 0
Battery = 2.39 volts
Reporting interval = 1

This is why the plug-in is showing all those errors (It does't like null values) and why you're not seeing any data.  There's no data to show.

[schleigh]

bpwwer, just to let you know, my problem was the Tempest.

[Morris Hansen]

I have a similar issue.  connected but all data is null.  weatherunderground seems to be getting the data.

WeatherFlow_4-8-2024_114523_AM.zip

[bpwwer]

@Morris Hansen It's hard to draw any conclusions from that log. 

The Tempest hub sends out data packets every 60 seconds.

The log shows that the plug-in starts listening from those at 1:45:11pm and the last entry is at 1:45:15, 4 seconds later.  Without knowing how long you waited before downloading the log it could be that you downloaded the log before the Tempest hub sent an update or if it was sitting for while without any log updates, it could be that something is blocking the plug-in from seeing the Tempest hub data.

The Tempest hub sends out UDP packets using port 50222.  UDP packets won't typically cross subnet boundaries so if the hub is on a different subnet form the eisy/Polisy, then it won't work.  If you have some firewall rule that blocks UDP packets then it won't work. 

[Morris Hansen]

I guess I should have waited longer. It is on the same subnet. The EISY is on wireless.

I was able to get it to work by changing from local to remote. I can pull another log today and share it.

Thanks

[bpwwer]

No need, it doesn't work locally with eisy wireless.  The wireless network is a different subnet internally on the eisy.

[Morris Hansen]

Ah.  I connected ethernet to the EISY and both Sonos and Weatherflow (local mode) work.  I figured it was something to do with the wireless.

[dbwarner5]

On 4/9/2024 at 11:56 AM, bpwwer said:

No need, it doesn't work locally with eisy wireless.  The wireless network is a different subnet internally on the eisy.

@bpwwer I just switched my EISY to wireless due to some other issues that I am working thru with Michel.

As a result the Station node has only zero values in it for local. Tempest is working fine, data is reported to hub, Alexa, tempest app.

Is there a fix or suggested work around for this? 

Thanks!

Just saw this post you made a while back. Will try this in the meantime. 

If it's not possible to have them on the same subnet, you can configure the node server to use remote data vs. local data.  It will then query the WeatherFlow servers for the data instead.  The trade off being that you're now dependent on the your external Internet connection for the weather data.

Edited September 11 by dbwarner5

[dbwarner5]

Switched it to remote and it's working as expected.