WeatherFlow PiConsole - Archive

Thank you Eric :slight_smile:
So I opened it and all the data incl. I have entered it correctly :frowning:

guess I’ll have to ask @peter to jump in. He’s the coder and has a brilliant mind imaging what can go wrong :rofl:

I can only think about a space that creeped in after the last character of the api key …

I’ve been looking for ā€œspaceā€, unfortunately they are not there, I don’t know what could cause …

But if the WeatherFlow API KEY was incorrectly embedded, it wouldn’t show any more information, would it?

Hi Petr, glad to hear you like the console, but sorry your having problems. Can you let me know your station ID and I will have a look into it!

Ps. Thanks for the troubleshooting help @eric

Hi Peter, thank you so much :slight_smile:
Station ID : 2867

Petr

Hi again - the weather forecast has already started :+1:. I didn’t do anything at all - I just turned off piconsole for the night and turned off again in the morning … Isn’t that weird? I didn’t fix anything.
And Can anyone please explain that Sager choice?

How can I set the time to turn off the Raspberry screen (screensaver?)?

And one more question:
I would like to turn ā€œpiConsoleā€ on and off with a home automation system. Is it possible to switch off / on ā€œpiConsoleā€ (resp. Raspberry) via LAN? I have a PoE power supply (PoE HAT) ready for Raspberry, so the console will still be connected to the PoE power supply.
Some ideas?

Thank you very much, gentlemen

Great! Glad it is working again. I found the bug that stopped it working yesterday (it crashes when the chance of rain is 0%) and I will get a fix pushed out today/tomorrow.

The Sager forecast is derived every 6 hours based on past and current wind speeds, wind direction, pressure and cloud cover. You can see how the forecast changes with different conditions on websites such as this one: Weather-Above Sager Algorithm

Have a look at this post here: Announcements & Updates - #64. It gives instructions on how to use energy saving features to turn the screen off after a set period of time

Using the command wfpiconsole autostart-enable you can set the PiConsole to start automatically when your Raspberry Pi is powered up. So you could use your PoE HAT to turn your Raspberry Pi on remotely, and then have autostart enabled to start the console automatically.

1 Like

Hi Peter,
thank you so much :blush:

PoE and remote turn on/off
Sure, I was ready to turn on the console by controlling the PoE power supply.
ā€œwfpiconsole autostart-enableā€ is already set.

But I read somewhere that the Rapsberry Pi should never be turned off by turning off the power, but always by software (shutdown).
That turning off the power over time can damage the SD card or the software on the card …

Can you please advise me how to make a printscreen (screenshot) piConsole and from piConsole then expert such an image easily out?
Because when controlling remotely via VNC Viewer or AnyDesk, the Rapsberry desktop is always displayed, not the piConsole screen. I tried to find a solution here in the forum, but I didn’t find anything cool …

Thank you Peter

Yes, that is a good point. I’m not sure how you could get around this as to safely shutdown the Pi you need to use a command like: sudo shutdown -P now. If you can’t send this from your home automation system then I don’t know how to get around it. Of course you could always just accept that eventually the SD card might get corrupted and you’ll just have to rebuild the console when this happens.

Yes unfortunately this is expected behavior on a Pi3. I think you can use the scrot command, however, to take screenshots: Scrot: A Command Line Tool to Take Desktop/Server Screenshots Automatically in Linux (I haven’t tested this over VNC though)

Hi Peter,

Thanks Peter, regarding the problem of getting a print screen from the WF piConsole screen, I’ll study it. Thank you :slight_smile:

My previous problem with the forecast - the problem reappeared today, and I think it was after 7pm (our time), like yesterday, that’s weird. Shutdow and reconnect did not help, and the error is back.

But SAGER weather forecast is provided :slight_smile:

Thank you for help
Petr

some firewall rule ??

@eric : I don’t have any firewall rules in my LAN system that have any time control …

But Peter mentioned today that ā€œā€¦I found the bug that stopped it working yesterday (it crashes when the chance of rain is 0%) and I will get a fix pushed out today / tomorrowā€¦ā€

let’s wait for the update … might solve your case tough I never saw it happen and we recently had several days with 0 rain … weird but … wait and see :grinning:

Probably yes, because SAGER weather forecast is provided.

@padamec and @eric, I’m just testing the new release over night to check for any gremlins and then I should be able to release it tomorrow. The problem seems to be that when the chance of rainfall is exactly zero (I think), the precip_probability field is not present in the forecast API response. That is why the forecast fails. This might be a bug in the API, but as is it still in a beta stage I just have to work around it.

@bmcgrady384 and @brian.vargo, can you check if you CheckWX API keys now work? I have had an email from support saying that all the issues with newly registered keys should have been fixed. You may need to restart the console to trigger an update to the Sager forecast if it is not working already.

yes it’s working. got my new key this morning from them.
Thanks!

1 Like

I had several emails from CheckWx support this morning. One of them contained a key which appears to be working.

Yeah haven’t noticed same behavior after reboot but seems my lightning strikes for the year is the same as my monthly and today. Rebooted same result, i can chk again tomorrow and restart

I tried to play a bit more with my M5StickC based temperature sensor. I moved the sensor a bit away from the micro controller and especially it’s battery and charging unit;-) Now I’ll have to adapt the conversation method a bit;-) Sorry about the color choice for the block below. That was the filament, my printer was using right now;-)20200701_225640_HDR
20200701_225652_HDR 20200701_225812

1 Like