jake1164 / pico-rgb-matrix-weather-clock Goto Github PK

We need some sort of display indicating Errors.

• settings.toml file missing
• Any missing setting within toml file
• API key error (expired, rejected token..etc)

I reinstalled all code from the zip file, edited the settings.toml with my api and wifi and I'm getting an openweather error. I created a new api and still won't load pas the sun icon and dev text. I'd like to get this working but ran out of time today to fiddle with it.

Also, do you think maybe we can get a code without weather, just date and time. May be an option to revert to until the weather can get sorted out. Thanks

When the user adjusts the time we need a way to stop updating the time so the users settings stick.

Look into the feasibility of supporting a 64x64 matrix using the board for the 64x32 panel.

https://www.waveshare.com/wiki/RGB-Matrix-P3-64x64
https://www.waveshare.com/wiki/Pico-RGB-Matrix-P3-64x32

The pins are the same so in theory its just setting a flag in the settings.toml file and adjusting the placement on the screen.

During build process create a .version file with the latest version that can be copied and read by the code.

Display the latest version somewhere:
Suggestions:

• really small font
• add to the scroll
• press button to display
• add to settings

Does not set time back as expected.

Give some notification that time sync is broken so the user might be aware that the time is wrong.

A few things need to be checked here:

1. need to check if this is already being implemented in CircuitPython.
2. Need to figure out how to make sure the settings file is only read if its been modified by system.

Currently if the WIFI or Internet drops the clock continues to display the last reading. For an extended time that could be very misleading.

If an update has not happened in last n seconds or tries we should not display the setting anymore (ie Temperature).
If the WIFI is down we should also perhaps replace the temperature with a wifi symbol with a line though it.

The numerical temperature, feels like, humidity and wind will only be correct if the unit is powered of and then back on. The current conditions seem to be correct but difficult to tell as it can be clear skies the whole day for example.

Just updated everything from the old code that just had the date, time, day. I'm using the latest weather src you added. I've added all needed information in the settings.toml file. Added the whole src to my pico w and ran the code. I have the splash screen (sun) then the display goes black.

Thonny shows correct output of all info supposed to be displayed, however nothing is being displayed.

I did however see for a brief moment the display did display the weather, time, conditions. But then it went back to a black screen.

Add the following sprites to a new status bitmap:
*no WIFI connection
*Disabled weather
*No NTP update?

On startup sometimes the NTP call will fail to sync, we should not wait the full time to sync.. maybe resync in a set shorter time like 1 min after the network settles.

When the automated pipeline runs we should set the file name to include the release version.

Looking forward it would be nice to be able to change the color based on the item being displayed.

Instead of the current method of just turning LEDs off when its dark we could change the colors to red to emit less blue lights.

For first go round I am suggesting just using the dimmer and have three settings based on brightness.
The dimmer would enable turning off leds like it currently does.
Add setting for night mode that will turn on / off the red color.

Discussion welcome

After much debate I think its better to have dedicated OWM and Tempest repositories. It will mean updating common bugs twice, however, it will make things more simple from an end user perspective.

When the display is off at night it would be nice to know that it is actually running and not dead. One thought would be to display a blinking red dot somewhere on screen.

When in the set a specific setting.. like set light level or change time the display flashes on and off really fast.

Clicking on buttons is hard because of the sleep functions in the scrolling display. If we use the asyncIO we could make the button presses more responsive.

We need to add a page for turning the NTP synchronization on / off. This will be important when the users adjusts the time and wants to turn time sync back on.

Apparently, this is around the time the NTP resync happens.

Project is way to big to not have unit tests. Needs to be a priority.

I am thinking a circle with the direction colored and the wind speed in the center. Not sure how to indicate gusts yet.

Not sure if it's happening to everyone, but my clock is displaying May 1st.

Maybe it's an April Fools joke?

[show()](https://docs.circuitpython.org/en/8.2.x/shared-bindings/displayio/index.html#displayio.Display.show) is deprecated and will be removed in CircuitPython 9.0.0. Use .root_group = group instead.

https://docs.circuitpython.org/en/8.2.x/shared-bindings/displayio/index.html

Having the display turn off at night and back on in morning works, but playing with the times it does not work for all combinations.

Turn off at 8am and on at 9 am for instance does not work.

Need to check why its not switching between imperial and metric.

This appears to be related to the autodim / on & off times. When the time is outside the settings it turns off the scrolling but the display does not turn off until the light is dim enough to activate autodim.

Purchased a new pico W and I am seeing constant messages:

free memory 6592
free memory after 3488
Exception memory allocation failed, allocating 256 bytes

Need to look into this and compare with previous pico.

The whole API call gets read into memory which limits the API feeds we can use. Switching to reading the stream and pulling out the fields we are looking for would allow us to use the better_weather API.

Thanks for fixing the pico 12 hour time, I’m using the pico w code de which I should have mentioned. Could you add it to that one as well? Thanks!

Now that the temperature will go away API failures have become more evident. I now often see no temperature displayed and we probably need to try and investigate if its the API, Size related or the WIFI connection dropping.

Need to add better error handling to prevent it from stopping clock if the NTP request times out.