Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RPI Kiosk Mode Issue #182

Closed
Stormtracker017 opened this issue Jun 26, 2019 · 16 comments
Closed

RPI Kiosk Mode Issue #182

Stormtracker017 opened this issue Jun 26, 2019 · 16 comments

Comments

@Stormtracker017
Copy link

I'm having an issue with the Pi Kiosk Mode. It opens up fine in the kiosk mode but:

  1. Does not switch over to "dark" mode.
  2. Displays Barometer value in "inHg" and the label is "mbar". Note main web page display the Barometer displays correctly in "mbar".
  3. Several items from the main page are missing like Dewpoint, Solar, Visibility, and Cloudbase.

In the skin .config file I did set "pi_kiosk_bold = "true"". Do I need to change something else?

General Question: If we recieve alerts from DarkSky, do they appear in the Kiosk Mode?

@biltmorelaker
Copy link
Contributor

biltmorelaker commented Jun 26, 2019

The Pi Kiosk display is designed to be shown on an Adafruit 3.5" touch screen with a resolution of 480x320. See Pat's blog article (https://obrienlabs.net/setup-raspberry-pi-kiosk-chromium/) on setting this up. There are some issues in setting the resolution on the latest version of Adafruit's display. If you have an issue doing that, let me know and I'll provide more information. I don't think there is room to easily add more observations. Here is what my display looks like on the Adafruit 3.5" touch screen.

wx kutzenco com.
Regarding dark mode - make sure you have the latest (beta) version from the "development" branch of the GitHub repository. Dark mode is set for "Auto" by default. You can set it to pi_theme = "light", pi_theme = "dark" or pi_theme = "auto" in weewx.conf. (Make sure to restart weewx or reload weewx.conf after changing weewx.conf.

Pat will need to answer the issues of inHg vs. mbar.

@biltmorelaker
Copy link
Contributor

Whoops. I accidentally closed this. Reopening.

@biltmorelaker biltmorelaker reopened this Jun 26, 2019
@poblabs
Copy link
Owner

poblabs commented Jun 26, 2019

The mbar/inHg issue is interesting. Is your site public? I'd like to take a look.

Admittedly the Pi page was a little left behind in the big 1.0 upgrade since my focus was on the charts. So like @biltmorelaker said, the new beta development version brings that back up to speed with the rest of the skin. So I'm thinking that's probably contributing to the barometer issue.

Item 3. the Pi page is a very slimmed down version, so those other items are missing on purpose - real estate is an extreme premium here. See the screenshot above 😄

DarkSky alerts will not show - again, screen real estate is the problem.

I suggest upgrading to the latest development version of the skin. it might help you out.

@Stormtracker017
Copy link
Author

Stormtracker017 commented Jun 27, 2019

As of right now, my site is on my LAN. I did update the skin to 1.1b3 and it fixed the switching between light and dark modes. I understand about the real estate. Thinking about switching to a 10 inch display.

The Kiosk still displays the Barometer value in "inHg" and the label is "mbar".
Web page and Kiosk Current Obs

Here are my settings in the weewx.conf

 [[MQTT]]
        ......
       [[[inputs]]]
            [[[[barometer]]]]
                units = mbar

[[Defaults]]
        
        [[[Units]]]
            .........        
            [[[[Groups]]]]
               ............
                group_pressure = mbar    # Options are 'inHg', 'mmHg', 'mbar', or 'hPa'

and my settings in the skin.conf

[Units]
    # This section is for managing the selection and formatting of units.  
    [[Groups]]
        ......
        group_pressure     = mbar   
        .....

@poblabs
Copy link
Owner

poblabs commented Jun 27, 2019

@Stormtracker017 I'm confused now since your screenshot looks like the normal website - not the Pi page. So in your screenshot, it looks like the main page is wrong? 1017.0 mbar?

@Stormtracker017
Copy link
Author

Sorry for the confusion, you are correct, the screenshot is the normal website which display the pressure in the correct format. The Kiosk displays the wrong value '30.07" but the label "mbar" is correct.

@poblabs
Copy link
Owner

poblabs commented Jun 27, 2019

What do you have set for unit_system under [MQTT]? Is it unit_system = METRIC?

@poblabs
Copy link
Owner

poblabs commented Jun 27, 2019

Update your Pi page to the latest one in the development branch. The changes make the station observation table match the one on the homepage. So the data should be in sync. Let me know.

@Stormtracker017
Copy link
Author

Stormtracker017 commented Jun 27, 2019

The unit_system is set to US. The updated file resolved the issue. Thanks

Update:

The daily max was being displayed as wind_today_max: on the Kiosk display. Added to the skin.conf:

[Labels]
# Labels used in this skin
[[Generic]]
......
Home Page Text and Titles
.......
wind_today_max = Today's Max

@poblabs
Copy link
Owner

poblabs commented Jun 27, 2019

Great news.

Since you're on US units, the MQTT label is still barometer_inHg, but the value of this is in mbar. A bit of a misleading configuration.

So the old file was doing the right thing using barometer_inHg since barometer_mbar wasn't available. What should have been done was also adding a name field like this:

 [[MQTT]]
        ......
       [[[inputs]]]
            [[[[barometer]]]]
                name = barometer_mbar
                units = mbar

But I made the update in the file to ignore the mqtt label and basically trust that the value was in the right unit.

@poblabs poblabs closed this as completed Jun 27, 2019
@biltmorelaker
Copy link
Contributor

@poblabs, Looks like commit 88173b changed the MQTT connected message (line 584)

from:

Connected. Received [date, time]

to:

Connected to weather station live. Data received [date, time]

This wraps that message on the top line on the pi display and pushes down the rest of the display.
Can you shorten that message again?

@biltmorelaker biltmorelaker reopened this Jun 28, 2019
@Stormtracker017
Copy link
Author

In the skin.conf, I changed "mqtt_websockets_connected = Connected to weather station live. Data received" to "mqtt_websockets_waiting = Connected. Waiting for data."

@biltmorelaker
Copy link
Contributor

To be clear, I am suggesting a change only for the pi display (in pi/index.html.tmpl). Not for the Belchertown home page.

@poblabs
Copy link
Owner

poblabs commented Jun 28, 2019

Thanks. This change was in response to a recent request in #104. I'll make an update for the Pi page headers which will be shorter and able to be translated using a label. I'll commit that shortly.

poblabs added a commit that referenced this issue Jun 28, 2019
Updates #104 for a new key
Updates #182
@poblabs
Copy link
Owner

poblabs commented Jun 28, 2019

All set in latest commit!

@poblabs poblabs closed this as completed Jun 28, 2019
@biltmorelaker
Copy link
Contributor

Perfect. All better now. Thanks @poblabs!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants