Last Strike 19903 days ago

Developers WeatherFlow PiConsole
21

Got a problem:
I stopped the console and deleted the wfconsole.ini then restarted -
BUT
I cannot get past the TEMPEST device ID step:

Station and device IDs
  ---------------------------------
  Please enter your Station ID*: 147356
  Do you own a TEMPEST?* [y/n] y
  Please enter your TEMPEST device ID*: 2207
    TEMPEST not found. Please re-enter your TEMPEST device ID*: ST-00152207
    TEMPEST device ID not valid. Please re-enter your TEMPEST device ID*: 2207
    TEMPEST not found. Please re-enter your TEMPEST device ID*: 2207
    TEMPEST not found. Please re-enter your TEMPEST device ID*:
22

Best guess is ‘maybe’ your TempestID is incorrect. The ID of 2207 is a very low number and I don’t recall the ID matching up with the last few digits of the SN but it’s been a long time since I had a Tempest so I don’t recall exactly. I’d check those first.

Your later post a few minutes ago also says your ID of 2207 is incorrect.

23

Your device ID is 357406

IMG_1879
IMG_18791170×2532 263 KB

24

TempestID
TempestID1920×2560 155 KB

What is this then?

25

That’s for last 4 digits of the device serial number. The Device ID and serial number have always differed in the Tempest ecosystem

2 Likes
26

Looks like I am good now.
Seems like the confusion was all about the TempestID.

Thank You Peter and Vince.

image

27

I guess I spoke too soon.
Lightning just struck nearby and I am still seeing the Last Stike be 19944 days ago…
At least we fixed everything else…

image

28

At least we are getting somewhere! I was never able to recreate this, so I think we need to examine exactly what data your console is receiving.

Are you happy editing Python code? If so, open ~/wfpiconsole/lib/observation_parser.py and on line 420 add: print(message) (make sure the indentation matches the preceding and following lines).

When you next receive a lightning strike, look on the terminal (make sure you start the console manually from the terminal - don’t rely on the autostart functionality) and you’ll see the lightning strike JSON packet printed to the screen. Share that with me and I can try and see if I understand what is going on

29

Did I put it in the correct location line420?
It keeps bombing out with error:

TabError: inconsistent use of tabs and spaces in indentation

image
image787×559 66.1 KB

30

You want all spaces (no tabs) and line’em all up visually. It’ll tell you if you get the indenting wrong.

But you want the print statement above the return there.

31

Hmmmm… sounds like a SitCom… Tabs vs Spaces…

2 Likes
32

Yes, that’s the right line but you need to use spaces to get the correct indentation rather than tabs. Python is very picky….

I made a mistake in my previous post. At the moment the print statement is 4 spaces over-indented. It needs to be on the same indentation level as the if-else statements (4 spaces to the left).

1 Like
33

Looks like I got it.
HOWEVER
If I reboot it, it autostarts and works.

If I stop it and then start it in the terminal, I never see the GUI on the screen:

image
image1428×544 91.1 KB

34

Depends on how you are in a terminal. If you’re using a local keyboard/mouse it will work fine. If you came in remotely, not so depending on how you remoted in. See GitHub - peted-davis/WeatherFlow_PiConsole: Raspberry Pi Python console for WeatherFlow Tempest and Smart Home Weather Stations

35

Here is everything again.
I disabled autostart.
I rebooted.
Using VNC I remoted in.
I started wfpiconsole.
The strike count is incrementing on it - but nothing is being printed in the console…
image

36

OK, it is very strange that the lightning strike count is increasing, but no lightning strike events are appearing on the console.

Between lines 144 and 145 of ~/wfpiconsole/service/udp.py please can you add the following line:

print(self.message)

Make sure the indentation matches line 145. This will print all UDP messages received by the console. Do you see any messages with type = evt_strike while the lightning strike is increasing?

37

You could run my wfudptools (available via pip) listener and capture your evt_strike events to a file as another way of capturing data…

1 Like
38

If it helps, this is what I am seeing on the UDP Debug of the Weather Display PC Application:
“strike_last_epoch”:1725496830,"
It will be storming by 2pm today, so I should be able to do the udp.py trace that Peter requested above, then.

{"status":{"status_code":0,"status_message":"SUCCESS"},"device_id":357406,"type":"obs_st","source":"cache","summary":{"pressure_trend":"steady","strike_count_1h":0,"strike_count_3h":0,"precip_total_1h":0.0,"strike_last_dist":40,"strike_last_epoch":1725496830,"precip_accum_local_yesterday":0.07449,"precip_accum_local_yesterday_final":0.280677,"precip_analysis_type_yesterday":1,"feels_like":36.6,"heat_index":36.6,"wind_chill":28.9,"raining_minutes":[0,0,0,0,0,0,0,0,0,0,0,0],"dew_point":26.9,"wet_bulb_temperature":27.4,"wet_bulb_globe_temperature":29.7,"air_density":1.16855,"delta_t":1.5,"precip_minutes_local_day":0,"precip_minutes_local_yesterday":9},"obs":[[1725628313,0,0.29,0.71,19,3,1013.2,28.9,89,35459,3.58,295,0,0,0,0,2.72,1,0,0,0,0]]}
{"device_id":357406,"type":"obs_st","obs":[[1725628373,0.0,0.1,0.51,199.0,3.0,1013.2,28.9,88.0,35315.0,3.57,294.0,0.0,0.0,0.0,0.0,2.73,1.0,0.0,0.0,0.0,0.0]],"summary":{"pressure_trend":"steady","strike_count_1h":0,"strike_count_3h":0,"precip_total_1h":0.0,"strike_last_dist":40,"strike_last_epoch":1725496830,"precip_accum_local_yesterday":0.07449,"precip_accum_local_yesterday_final":0.280677,"precip_analysis_type_yesterday":1,"feels_like":36.4,"heat_index":36.4,"wind_chill":28.9,"dew_point":26.7,"wet_bulb_temperature":27.3,"wet_bulb_globe_temperature":29.6,"air_density":1.16855,"delta_t":1.6,"precip_minutes_local_day":0,"precip_minutes_local_yesterday":9},"source":"mqtt","serial_number":"ST-00152207","hub_sn":"HB-00158637","firmware_revision":179}
{"device_id":357406,"type":"obs_st","obs":[[1725628433,0.0,0.35,1.04,26.0,3.0,1013.2,29.0,88.0,35230.0,3.56,293.0,0.0,0.0,0.0,0.0,2.73,1.0,0.0,0.0,0.0,0.0]],"summary":{"pressure_trend":"steady","strike_count_1h":0,"strike_count_3h":0,"precip_total_1h":0.0,"strike_last_dist":40,"strike_last_epoch":1725496830,"precip_accum_local_yesterday":0.07449,"precip_accum_local_yesterday_final":0.280677,"precip_analysis_type_yesterday":1,"feels_like":36.7,"heat_index":36.7,"wind_chill":29.0,"dew_point":26.8,"wet_bulb_temperature":27.4,"wet_bulb_globe_temperature":29.7,"air_density":1.16816,"delta_t":1.6,"precip_minutes_local_day":0,"precip_minutes_local_yesterday":9},"source":"mqtt","serial_number":"ST-00152207","hub_sn":"HB-00158637","firmware_revision":179}
39

That sounds good. It’ll be really useful to see what is being ingested by the console.

Just to check - are you sure that the time on your Raspberry Pi is correct? If the time is wrong, it will affect the calculation of the time since the last strike

40

Yes, the time is correct and is set to a local/stable NTP source:
image