- 🌡️ Records weather details such as temperature, precipitation, 🌬️ wind speed, ☀️ UV index, 📊 atmospheric pressure and 💧 humidity using the open-meteo.com API.
- 🕰️ Operates 24/7, updating every hour.
- 🚨 Sends weather alerts to a Telegram bot by:
- Checking every minute the weather for the upcoming 6️⃣ hours.
- Monitoring every minute the atmospheric pressure for the next 2️⃣4️⃣ hours.
- For each type of alert, an alert is sent only once a day
- 📊 Dispatches monthly and yearly weather summaries.
- Command /start to start receiving alerts (& List of commands)
- Command /weather to view the last entry in the CSV (past hour)
- Command /month to view report of the last month's entries in the CSV
- Command /year to view report of the current year's entries in the CSV
- [NEW] Command /all to view report of all entries in the CSV
- Command /forecast to view the next 6 hours forecast
- Command /sunshine to view sunshine reports of all entries in the CSV
- [✅] Improved support for the transition between summer and winter time.
- [✅] Add the recently introduced 'humidity' parameter to monthly and annual reports, including the least humid and most humid days.
- [✅] Add a command to view weather forecasts for the upcoming 6 hours.
- [✅] Calculate the number of sunshine hours per day for the monthly report and per month for the annual report, based on UV values.
- [✅] Add emojis for reports.
- [✅] Improved presentation for information with /weather and forecast commands, such as monthly or yearly reports.
- [✅] Add command to view a report on all recorded data
- [Nice to have] Add a custom command to view a report between two dates, and if no data is available, display "No data available for the selected period"
- [Nice to have] Visualize different years graphically for various metrics such as temperature, rainfall accumulation, etc.
The script records weather data in UTC. The Open-Meteo API is queried using the GMT (UTC) time zone, ensuring that all timestamps stored (e.g., in the CSV file) are in UTC. This standardization allows the system to consistently manage and compare data, guaranteeing that each hourly interval represents a fully completed measurement period. For example, if the current time in UTC is 12:00, a user in the UTC+1 zone who requests weather data at 13:00 local time (which corresponds to 12:00 UTC) will receive data for the fully completed previous hour. In this scenario, the returned data covers the interval from 11:00 to 12:00 UTC (which corresponds to 12:00 to 13:00 in the local Berlin time). This approach ensures that users always receive weather information based on complete, finalized hourly intervals—avoiding any partial or ongoing measurements—even though the displayed times are converted to the local Berlin time zone for clarity.
- Check logs