Originally posted by codemonkey
View Post
What does the log show when the plug-in is started? It should look something like this:
Code:
Jun-11 9:59:10 AM WeatherFlow Skiping calculations, missing sky data. Jun-11 9:59:10 AM WeatherFlow Starting communication with websocket server. Jun-11 9:59:09 AM WeatherFlow Adding station 123 to station list (3) Jun-11 9:59:09 AM WeatherFlow Querying meta data for station Home Jun-11 9:59:09 AM WeatherFlow Adding station Home to station list (4) Jun-11 9:59:09 AM WeatherFlow Querying meta data for station Outside Jun-11 9:59:09 AM WeatherFlow Adding station Outside to station list (7) Jun-11 9:59:09 AM WeatherFlow Querying meta data for station 1831 Jun-11 9:59:09 AM WeatherFlow Adding station 1831 to station list (4) Jun-11 9:59:09 AM WeatherFlow Querying meta data for station 123 Jun-11 9:59:09 AM WeatherFlow Adding station 123 to station list (3) Jun-11 9:59:09 AM Starting Plug-In Plugin WeatherFlow started successfully in 6 milliseconds Jun-11 9:59:09 AM Starting Plug-In Initializing plugin WeatherFlow ... Jun-11 9:59:08 AM Info Plugin WeatherFlow has connected. IP:127.0.0.1:58429 Jun-11 9:59:08 AM WeatherFlow I have connected to HomeSeer. Jun-11 9:59:08 AM Plug-In Finished initializing plug-in WeatherFlow
Just a question, but what was the trial version going to do when the trial time ran out?
I can confirm that my hub is working correctly as I can access it via the weatherflow app.
The plug-in is listening for the UDP network broadcasts (unless you check the remote checkbox in the station config, then it's getting the data from the WeatherFlow servers).
One of the characteristics of the UDP broadcasts is that it's very simple from the client side (and from the server side, too). The client doesn't know anything about who is sending information. It's like going into a room and listening to others talk. You don't really need to know who is in the room talking, you just walk in and start listening. If they stop talking, you don't hear anything, but you can't really do anything to make them talk to you.
So at this point, the most likely cause is the hub no longer sending out the data via UDP. There are other programs, see https://community.weatherflow.com/c/...tions/l/latest, that can make use of the UDP data from the hub. That or some type of network monitoring tool will be needed to determine if it's the hub or the plug-in.
Some routers can be configured to not forward on UDP packets, that's not likely the case here since it was working (unless it stopped after replacing or re-configuring your router).
You could try rebooting the hub, if it is the hub, then a power cycle/reboot may get it to start sending data out again.
I also added a debug config option to the plug-in to get some more detailed log messages when enabled. I don't think it will provide any additional information in this case but that's what's in 3.0.0.7 when it shows up in the updater.
Comment