thanks for reply. I just gave a try to OpenWeatherMap
I like it because offers more sensors than AEMET. I do not know which is more reliable, but I will make a comparation soon. And I will use OpenWeatherMap like backup, or who knowsā¦ maybe main because AEMET gets down frequently
The original goal of the guide was to provide alternatives to Openweathermap which donāt require voluntary disclosure of creditcard informationā¦
Although I still strongly encourage everyone to keep your creditcard information private and reduce the risk of creditcard theft, the whole point of home assistant is to give you choices.
fair enough. but you can use disposable cards(like I did) , virtual cards etc
also the service permits the first 1000/day free. and you can configure the number of calls
in the end itās a free service
Prepared new version of integration and itās now pending PR on Github.
Slovenian Weather Integration
- Home Assistant Custom Component
Slovenian Weather Integration is a custom component for Home Assistant, leveraging real-time weather data from ARSO (Agencija Republike Slovenije za okolje). It provides detailed weather information and forecasts tailored to users in Slovenia and neighboring regions.
Features
Real-Time Weather Conditions: Temperature, humidity, wind speed, gusts, pressure, visibility, dew point, and weather conditions.
3-Hour, Twice-Daily & Daily Forecasts: Up to 6 days of detailed forecasts, including precipitation and wind data.
How to install:
HACS Installation:
or
Manual Installation
- Download or clone this repository.
- Copy the
custom_components/slovenian_weather_integration
folder to your Home Assistantcustom_components
directory: - Restart Home Assistant to recognize the new integration.
Setup
- Go to Configuration ā Devices & Services in Home Assistant.
- Click Add Integration.
- Search for ARSO Weather Integration.
- Follow the prompts to select your desired location(s).
Supported Features
- Temperature (Ā°C)
- Humidity (%)
- Pressure (hPa)
- Wind Speed (km/h)
- Dew Point (current weather only)
- Visibility (km) (current weather only)
- Precipitation (mm) (forecasts only)
Supported Features
Current Temperature (Ā°C)
Humidity (%)
Pressure (hPa)
Wind Speed (km/h)
Cloud Conditions (translated to Home Assistant-compatible terms)
Daily and Hourly Forecasts
Dew point ---> only in current weather
Wind gust speed (km/h)
Visibility (km) ---> only in current weather
Precipitation (mm) ---> only in forecasts
Wind Gust Speed (km/h) ---> only in forecasts
State attributes
datetime: "2024-09-16"
temperature: 2
templow: 0
precipitation: 0
wind_speed: 38
wind_bearing: NW
wind_gust_speed: 0
condition: cloudy
pressure: 1013
Weather forecasts are not part of the entityās state, theyāre instead made available by a separate API.
he integration implements two of the async methods async_forecast_daily
, async_forecast_hourly
.
Updating weather forecast(s) - Action weather.get_forecasts
Example:
template:
- trigger:
- platform: time_pattern
hours: /1 # Sproži se vsako uro
action:
- service: weather.get_forecasts
data:
type: hourly
target:
entity_id: weather.arso_vreme_ljubljana
response_variable: hourly
sensor:
- name: Temperature forecast next hour
unique_id: temperature_forecast_next_hour
state: "{{ hourly['weather.arso_vreme_ljubljana'].forecast[0].temperature }}"
unit_of_measurement: Ā°C
Unique ID Support
Each weather entity now gets a unique ID based on its location and configuration entry. This allows you to customize and edit the entity from the Home Assistant UI.
Debugging
If you encounter issues, you can enable debug logging for the integration by adding the following to your configuration.yaml:
logger:
default: info
logs:
custom_components.arso_weather_integration: debug
Known Issues
Precipitation Data: Real-time precipitation may not always be available. But is visible as attribute to weather entitiy.
Forecast Availability: Ensure the selected location supports both 3 hour and daily forecasts.
Thanks a lot!!! Iāve been waiting for quite a while for someone with knowledge to make this integration, so thanks again!
It works perfectly, i do have one question, though: whatās that sensor in automation example? Automation wonāt accept it, if i put it under template sensor itās unavailable. Entering it under āsensorā in configuration gives me āmissing device_idā errorā¦
sensor:
- name: Temperature forecast next hour
unique_id: temperature_forecast_next_hour
state: "{{ hourly['weather.arso_vreme_ljubljana'].forecast[0].temperature }}"
unit_of_measurement: Ā°C
Thanks @Protoncek ! Shoot, I messed readme file, sorry. Will post corrected, stay tuned!
EDIT:
Itās supposed to be a template, try this:
template:
- trigger:
- trigger: time_pattern
hours: /1 # Sproži se vsako uro
action:
- action: weather.get_forecasts
data:
type: hourly
target:
entity_id: weather.arso_vreme_ljubljana
response_variable: hourly
sensor:
- name: Temperature forecast next hour
unique_id: temperature_forecast_next_hour
state: "{{ hourly['weather.arso_vreme_ljubljana'].forecast[0].temperature }}"
unit_of_measurement: Ā°C
If you wish to create a sensor
(for instance a current temperature for Ljubljana - not forcasted like above) from your weather entity, you also use a template:
- sensor:
- name: Temperatura Ljubljana
unique_id: temperatura_arso_weather_ljubljana
state: "{{ state_attr('weather.arso_vreme_ljubljana', 'temperature') }}"
unit_of_measurement: Ā°C
device_class: temperature
Another question, more like an info or suggestion: since i think that we can safely assume that this addon will be (mainly) used by slovenians: perhaps sensors should be in slovenian language by default? What do you think regarding that?
I recommend starting a topic to discuss the specific integration. Most integrations have one of those.
Moving toā¦š¦ļø Slovenian Weather Integration šøš®