@storm_tracker I don’t believe that I’m seeing the data errors, but I may be looking in the wrong place. Where are you seeing that?
It showed up yesterday and the day before. (per my post several threads up)…it looked like this:
That’s why I called it a “False Negative” because the 4 LEDs were still illuminated Green on the Hubs. Had the “Error” been true. . .then the 4 LEDs would-a turned red.
However. . .today. . .there is no red “Error” under the Status heading. . .and the red-circled " ! " was not visible today either.
But. . .in the Barometer section of mine (upper right-hand window). . .when I switch to one of my other stations. . .the trend will show something like: 0.018 inHg/hr Falling but only for about 10 seconds. . .then it will change right before my very eyes to: —inHg/hr . . . and the verbage below that normally states: “Conditions unchanged” will also be dashed ( — )
When I press the menu button in the lower right corner. . .then press “Exit”. . .it takes me back to the main prompt screen. . . in which the log shows the “WARNING” in yellow letters as seen two images above.
I think I saw elsewhere earlier in the topic that there was a possible API issue with WF | t° not returning some sort of data. For my ‘wfpiconsole’. . .this all started late this past Monday night (the 19th). I do not mess with the “wfpiconsole.ini” file unless it is an “emergency” . . . otherwise I leave all of the directory folders and files alone.
Jut let do for now. Problem is most probably identified but Peter and WF/T° need some time to solve this.
Thanks for your patience and sorry for the mess.
3 Likes
It looks like this has been resolved, everything looks fine on my display now and I didn’t do anything.
Thank you, whoever fixed this!
1 Like
Yes…I noticed this also around Noon CDT. I echo your final sentence above!
@storm_tracker and @DavidK, great - glad to hear it’s working again! There was a little glitch in the API that the T° team fixed up
2 Likes
as of 2 days ago (09/26/2022). . .the red-circled exclamation point ( ! ) and the Station status: “Offline” in red is showing up again. . . as well as the word “Error” for device status… . . exactly the same as my post several threads up. All 4 Hubs are Green . . . and now. . . I’m seeing this for the card view for all 4 of my stations.
I guess. . . I’ll just have to play along with it — just “grin & bear” it!
might be again a WF/T° problem but with a hurricane situation not going to ask, priority is the hurricane situation.
[WARNING] [Websocket ] 2022-09-24 13:53:20 - Ping failed
[INFO ] [Websocket ] 2022-09-24 13:53:20 - Closing connection
[INFO ] [Websocket ] 2022-09-24 13:53:20 - Connection closed
[INFO ] [Websocket ] 2022-09-24 13:53:30 - Opening connection
[INFO ] [Websocket ] 2022-09-24 13:53:34 - Connection open
[WARNING] [Websocket ] 2022-09-24 14:07:59 - Ping failed
[INFO ] [Websocket ] 2022-09-24 14:07:59 - Closing connection
[INFO ] [Websocket ] 2022-09-24 14:07:59 - Connection closed
[INFO ] [Websocket ] 2022-09-24 14:08:09 - Opening connection
[ERROR ] [Websocket ] 2022-09-24 14:08:19 - General error:
[INFO ] [Websocket ] 2022-09-24 14:08:29 - Opening connection
[INFO ] [Websocket ] 2022-09-24 14:08:34 - Connection open
[WARNING] [Websocket ] 2022-09-24 14:15:36 - Ping failed
[INFO ] [Websocket ] 2022-09-24 14:15:36 - Closing connection
[INFO ] [Websocket ] 2022-09-24 14:15:36 - Connection closed
[INFO ] [Websocket ] 2022-09-24 14:15:46 - Opening connection
[ERROR ] [Websocket ] 2022-09-24 14:15:56 - General error:
[INFO ] [Websocket ] 2022-09-24 14:16:06 - Opening connection
[ERROR ] [Websocket ] 2022-09-24 14:16:16 - General error:
[INFO ] [Websocket ] 2022-09-24 14:16:26 - Opening connection
[ERROR ] [Websocket ] 2022-09-24 14:16:36 - General error:
[INFO ] [Websocket ] 2022-09-24 14:16:46 - Opening connection
[ERROR ] [Websocket ] 2022-09-24 14:16:56 - General error:
[INFO ] [Websocket ] 2022-09-24 14:17:06 - Opening connection
[INFO ] [Websocket ] 2022-09-24 14:17:06 - Connection open
[WARNING] [Websocket ] 2022-09-24 14:18:27 - Ping failed
[INFO ] [Websocket ] 2022-09-24 14:18:27 - Closing connection
[INFO ] [Websocket ] 2022-09-24 14:18:27 - Connection closed
[INFO ] [Websocket ] 2022-09-24 14:18:37 - Opening connection
[INFO ] [Websocket ] 2022-09-24 14:18:43 - Connection open
[WARNING] [Websocket ] 2022-09-24 19:44:56 - Ping failed
[INFO ] [Websocket ] 2022-09-24 19:44:56 - Closing connection
[INFO ] [Websocket ] 2022-09-24 19:44:56 - Connection closed
[INFO ] [Websocket ] 2022-09-24 19:45:06 - Opening connection
[INFO ] [Websocket ] 2022-09-24 19:45:08 - Connection open
I kinda had that thought too. Florida’s focus is “Safety First”. . .everything else is tertiary. Totally Understandable. Power outages and networks interruptions are quite likely. . .if not already happening due to the situation at hand.
Like others, the “Red Exclamation mark” appeared a couple of weeks ago in wfpiconsole. Kill the program and restart would seem to fix it for 10-15 minutes, and then it would appear again. Then, three or four days ago, the problem went away but as of yesterday, back again. At first I thought it might have been something wonky with running two instances of wfpiconsole (I run one on a VNC server for a tablet to connect to, and another on the Gnome desktop in Ubuntu). But, both instances eventually result in the red exclamation mark. The tempest app seems to be pulling data in okay - so is this an issue with generated API keys?
Correct me if I am wrong. . .but I am assuming that this is still an issue because of post-Hurricane cleanup / recovery and Computer-Communications problems in the Daytona Beach area. . .as well as most all of the Florida peninsula.
Servers are not in house. They are in real data centers all over the country. They have not been affected by the hurricane and even if a center has an issue, they are redundant (AWS)
I just looked at mine and I have no errors anymore. Have you tried a reboot recently ??
1 Like
Let me know if a reboot fixes the problems - otherwise I will try and take a look at what is going on (although I’m, not sure how helpful that will be as it sounds like others are connecting fine)
I have switched stations / devices. . .and that cures it. . .but only for < 3 minutes. . .then it goes red again. . .but only for my WFAIR devices. I have done several reboots of ‘wfpiconsole’ (which didn’t eliminate the “red”). . .and I even do a Shutdown at the end of my weather-duty day. Then I start up ‘wfpiconsole’ in the next morning. All goes well for about 3 minutes. . .then it’s back again. I have not “monkey’d” with the “wfpiconsole.ini” for any other files what-so-ever.
Followup: at approximately 1610 UTC. . .I did another reboot of my ‘wfpiconsole’. . .as of now. . .1726 UTC. . .‘wfpiconsole’ is normal. . . as in no red (Shhhhh I don’t want the console to hear me or see me typing this or it might misbehave again!)
I didn’t do anything out of the ordinary except pressing the Reboot button at the bottom Menu. . .then doing a normal “wfpiconsole start”.
I will continue my Situational Awareness and hopefully normality will prevail.
I’m starting to see the red! on my console just today but I have also seen my Web site say 32mins ago etc.
I do nothing and it comes right. Though it’s happening a few times today so I persume a wider issue could be happening or the terrible weather coming my way (snow in spring time) .
I’m presuming that as I had not had any internet issue at the same time, that I notice.
I think a I may have cured the red " ! " and the red " Error " problem that my ‘wfpiconsole’ has been experiencing lately. I unplugged the Netgear N450 Router and left it off for 2 minutes. . .long enough for the four WFHUBs to turn from green LED to red LED. Then I plugged the N450 back into the AC and allowed the 4xWFHUBs to turn back to green LED again. Then I did one Reboot of ‘wfpiconole’ afterwards. The console is now on normal display (as it Should Be) and there is no visible " ! " or the word " Error " for the Station status or Device status. It took me many tries to learn what the probable cause was. . .but thru Operant Conditioning. . .I have now learned how to solve that little issue! Basically. . .a reset of the Router. . .and a Reboot of ‘wfpiconsole’ seems to be the fix action for this.
1 Like
My current Router / Access Point is a DOCSIS 3.0. I was told by my internet provider that the N450 is rapidly becoming “ancient technology” and that I should highly consider upgrading to the latest version. . . something like DOCSIS 4.0. Having that “older” technology is probly >75% of the problem!
Docsis refers to the technology in the cable modem. Having a combination cable modem / router is common, but not the best approach. Better to have a separate modem and router.
2 Likes