Weird - I must have been doing something silly this morning as I couldn’t find 6392 at all!
I’m not sure there is anything wrong with the JSON data. The available fields look identical to my station: https://swd.weatherflow.com/swd/rest/stations/4968?api_key=20c70eae-e62f-4d3b-b3a4-8586e90f3ac8. I think what we as a community refer to as “Station ID” is actually the “location_id” in the JSON data.
When I first created a station - 6382 - it had a station_id. Then, after some time the API wouldn’t find it when looking via station ID, so I looked at the JSON for retrieving all stations and station_id was gone, but it showed up. I deleted the station, created a new one - 6392 - and while station_id was not present I could still retrieve it via ID. Seems like there may have been some oddity in weatherflow’s API for some period of time.
Odd. Perhaps that’s why I couldn’t find your station this morning?! It would be interesting to hear what WeatherFlow have to say about it.
Heya @peter - just started playing around in the source (preparing to make some changes so that I can pull internal temperature from my ecobee thermostat). I’ve cloned your repo and am running in IntelliJ. When I run the console, though, things look like there’s some kind of scaling problem - see the attached image.
Have you tried doing this at all? If so, any tips on making the display render better on my Mac?
that’s on a mac most probably and now the wild guessing, is there some config part where you can pre define the screen size in which you run the script ??? Seems like something overflows and pushes all around.
Yup, it’s on a mac. The screen is defined to be 800x480, which is the same screen size as on the Pi console itself. The blank templates are rendered correctly, but the dynamic parts are not.
It looks like it’s some kind of a scaling problem. I’m not familiar with kivy, so I thought I’d check with @peter to see what his development model is - i.e., whether he runs it only on the Pi with its screen, or if he develops on a Mac/Linux/Windows PC and has some “trick” to set the screen scaling correctly.
Peter does develop on PC according this post way above
I’m afraid I don’t have much advice to offer here. I was going to suggest it was a screen resolution issue, but it sounds like you have it set to 800x480. As @eric mentioned, I develop using a windows PC and then test everything on the Pi with an attached touchscreen. I don’t have a Mac to develop/test on. I know @tcichowicz had the PiConsole running on Linux quite happily, and was experimenting with Mac. Perhaps @tcichowicz has some suggestions?
Did you get the pressure to match?
No, But its close enough for me.
PiConsole = 30.284
Arcivesw = 29.170
I wonder if it could be a font problem. You used maybe a font that doesn’t pre exist on mac and by default it’ll go for system font I think, and that might not be at all the same size and spacing, hence flow over
Turns out that it’s a problem with the way you specified the pixels in wfpiconsole.kv - you’re using actual pixels and not dp for the sizes. I’m still working on it (got to fix the buttons on the bottom), but I’ve changed them from, for example size: (90,30) to size: dp(90), dp(30). I still have to check to see if it’s still correct on the Pi, but at least I can see it on the mac 
Progress - note the buttons on the bottom still need some work:
Once I’m done I’ll fork the repo and submit a PR.
I’ve been successful with linux, and PC not the MAC. I tried several installs of python, and got to a point where nothing I tried got me passed what I believe is an environmental issue. Refer back to this post for more details of my problems. Sorry I wasn’t able to be of more help. I did spend a couple of days trying to get it working. Including 3 Time Machine restores to get me back to a known clean starting point.
I do run wfpiconsole on monitors / resolutions outside the recommended Official 7" Rpi display. To fix the issue you have - I’ve made some changes in the wficonsole.kv file, to force the image size…from size: self.size to size: (800,480) . This is under the ## CURRENT CONDITIONS SCREEN section.
It appears you got further than I did. I could NOT get passed the ‘pygame’ issue that is shown in my older post that I provided a link to. Good Luck.
They should be exsctly the ssme. I think you are missing a configuration value on the Panel.
just an FYI I also show a difference between ArchiveSW & wfpiconsole. The screenshots below are in realtime - one a wfpiconsole running on my PC desktop (Windows10 x64) and the ArchiveSW is running (on my Rpi) web client Chrome running on the same PC (Windows 10 x64)
edit(update - the wfpiconsole (Win10)values match exactly to my other 2 wfpiconsoles running on Rpi(s)
The first thing to check is the height values on the Panel tab of ArchiveSw server.
Great work! Thanks for investigating this. Very happy to integrate your changes assuming they play nicely with the Raspberry Pi (which of course is full of its own graphical oddities!)
ok I just compared the settings in that config screen, to the values I provided in my iOS app during the original setup. Those were determined by a tape measure.
my Air is 6ft off the ground, my Sky 13ft.
edit: not sure if Peter’s conversion takes into consideration elevation?
