Tovrin
May 21, 2019, 7:53am
1
Hi Folks,
I have a tile showing me the Current weather from the BOM.
Could someone tell me how to what I need to change the “unknown” to something more meaningful? I thought it might be name: <location> but it’s not.
The sensor config I’m using is:
- platform: bom
name: XXXXX
station: IDN60903.94926
monitored_conditions:
- apparent_t
- delta_t
- gust_kmh
- gust_kt
- air_temp
- dewpt
- press
- press_qnh
- press_msl
- press_tend
- rain_trace
- rel_hum
- vis_km
- weather
- wind_dir
- wind_spd_kmh
- wind_spd_kt
Could someone give me a hand here?
if you look at the entities in the dev state panel for the BOM sensor you should be able to see which attribute is giving you the ‘unknown’
Tovrin
May 21, 2019, 8:01am
3
It’s apparently the State. Not sure what to do about that.
Which attribute is it for? I remember having the same issue and ended up changing the station to a different one as the particular entity wasn’t being given by my nearest station. ( I had to change from Perth to Perth Airport or something like that, can’t remember exactly)
Tovrin
May 21, 2019, 8:50am
5
Dang. I seem to be getting the same with the next nearest station too.
I may have to switch back to darksky.
DarkSky weather info is rubbish for Aus. Try a major capital city and/or an airport as a test run to try and help work out what’s going on
Tovrin
May 21, 2019, 9:22am
7
I’ve tried everything within 100km of the ACT. They all come up as “unknown”. Sydney’s fine though … not that it helps. DarkSky is all I really have.
Which attributes is it that’s failing?
DarkSky gets a bad rap. I’m in Sydney and it’s within a degree or 2 of BOM and BOM is 2-3 degrees different to the reality anyway. For trends and a general idea, DarkSky works fine for me.
Tovrin
May 21, 2019, 10:39pm
10
@sparkydave It’s not one of the attributes per se. It’s the “state”, which reports high level info like “Cloudy”, “Rain”, etc. It just says “unknown” for every station in the region.
I guess that your local stations aren’t sending that value for some reason…?
Perhaps try using (if you like it) this custom card (which is named DarkSky, but can be used with BOM data) and use it with all BOM data except for that particular value which you could then get from DarkSky. That way you have the best data for most of it and only require DarkSky for the weather description bit.
I have setup like this:
weather.yaml
sensor:
- platform: darksky # DarkSky sensors (separate to component)
api_key: !secret darksky_api_key
## name: Perth Weather
# scan_interval: '00:15:00'
forecast:
- 1
- 2
- 3
- 4
- 5
## - 6
## - 7
monitored_conditions:
## - summary
## - precip_type
# - precip_intensity
## - precip_probability
# - precip_accumulation
## - temperature
## - apparent_temperature
# - dew_point
## - wind_speed
- wind_bearing
## - cloud_cover
## - humidity
## - pressure
- visibility
- icon
# - ozone
# - minutely_summary
## - hourly_summary
## - daily_summary
## - temperature_high
## - temperature_low
## - apparent_temperature_high
## - apparent_temperature_low
## - precip_intensity_max
## - uv_index
- platform: bom # Bureau of Meteorology Australia (separate to component)
# station: IDW60901.94608 # main Perth city station (doesnt seem to work for the Weather parameter)
station: IDW60901.94610 # Perth airport station
name: Perth
monitored_conditions:
- apparent_t
# - cloud
# - cloud_base_m
# - cloud_oktas
# - cloud_type_id
# - cloud_type
# - delta_t
# - gust_kmh
# - gust_kt
- air_temp
# - dewpt
- press
# - press_qnh
# - press_msl
# - press_tend
- rain_trace
- rel_hum
# - sea_state
# - swell_dir_worded
# - swell_height
# - swell_period
# - vis_km
- weather
- wind_dir
- wind_spd_kmh
# - wind_spd_kt
- platform: bom_forecast
product_id: IDW12300
name: Perth Forecast
forecast_days: 6
rest_of_today: True
friendly: False
friendly_state_format: '{min} to {max}, {summary}'
monitored_conditions:
- 'max'
- 'min'
- 'chance_of_rain'
- 'possible_rainfall'
- 'summary'
- 'detailed_summary'
lovelace:
- title: Weather
icon: 'mdi:weather-partlycloudy'
background: center / cover no-repeat url("/local/images/elizabeth_quay_perth.jpg") fixed
cards:
- type: 'custom:dark-sky-weather-card'
entity_sun: sun.sun
entity_daily_summary: sensor.bom_perth_forecast_detailed_summary_0
entity_current_conditions: sensor.dark_sky_icon
entity_humidity: sensor.bom_perth_relative_humidity
entity_pressure: sensor.bom_perth_pressure_mb
entity_pop: sensor.bom_perth_forecast_chance_of_rain_0
entity_temperature: sensor.bom_perth_air_temp_c
entity_apparent_temp: sensor.bom_perth_feels_like_c
entity_daytime_high: sensor.bom_perth_forecast_max_temp_c_0
entity_visibility: sensor.dark_sky_visibility
entity_wind_bearing: sensor.bom_perth_wind_direction
entity_wind_speed: sensor.bom_perth_wind_speed_kmh
entity_forecast_high_temp_1: sensor.bom_perth_forecast_max_temp_c_1
entity_forecast_high_temp_2: sensor.bom_perth_forecast_max_temp_c_2
entity_forecast_high_temp_3: sensor.bom_perth_forecast_max_temp_c_3
entity_forecast_high_temp_4: sensor.bom_perth_forecast_max_temp_c_4
entity_forecast_high_temp_5: sensor.bom_perth_forecast_max_temp_c_5
entity_forecast_low_temp_1: sensor.bom_perth_forecast_min_temp_c_1
entity_forecast_low_temp_2: sensor.bom_perth_forecast_min_temp_c_2
entity_forecast_low_temp_3: sensor.bom_perth_forecast_min_temp_c_3
entity_forecast_low_temp_4: sensor.bom_perth_forecast_min_temp_c_4
entity_forecast_low_temp_5: sensor.bom_perth_forecast_min_temp_c_5
entity_forecast_icon_1: sensor.dark_sky_icon_1d
entity_forecast_icon_2: sensor.dark_sky_icon_2d
entity_forecast_icon_3: sensor.dark_sky_icon_3d
entity_forecast_icon_4: sensor.dark_sky_icon_4d
entity_forecast_icon_5: sensor.dark_sky_icon_5d
entity_pop_1: sensor.bom_perth_forecast_chance_of_rain_1
entity_pop_2: sensor.bom_perth_forecast_chance_of_rain_2
entity_pop_3: sensor.bom_perth_forecast_chance_of_rain_3
entity_pop_4: sensor.bom_perth_forecast_chance_of_rain_4
entity_pop_5: sensor.bom_perth_forecast_chance_of_rain_5
entity_summary_1: sensor.bom_perth_forecast_summary_1
entity_summary_2: sensor.bom_perth_forecast_summary_2
entity_summary_3: sensor.bom_perth_forecast_summary_3
entity_summary_4: sensor.bom_perth_forecast_summary_4
entity_summary_5: sensor.bom_perth_forecast_summary_5
static_icons: true
sunset: true
locale: en
old_daily_format: false
tooltips: true
tooltip_bg_color: 'rgb( 75,155,239)'
tooltip_border_color: orange
tooltip_border_width: 1
tooltip_caret_size: 10
tooltip_fg_color: '#fff'
tooltip_left_offset: -5
tooltip_width: 100
which looks like this:
As you can see in the Lovelace code, I only use DarkSky for the visibility and icons. You can customise which entities come from any weather data source you want, in your case, fill in the missing ‘unknown’ entity with DarkSky data
1 Like
Tovrin
May 22, 2019, 4:23am
12
Very nice! I’m still a bit of a novice, but I’ll see how I can make it work for me. Cheers.
Edit: I’ve had a closer look. Yeah. I can definately make this work. Cool
Since when has bom_forecast been a platform? Is this the ftp thing?
Correct, it’s the FTP custom component. Seems to be working very well now for a few months or so
I’m setting it up for a friend… did you make any changes to the js file? I am getting errors and nothing on the screen
nope. I just used the files from the Git, however I do have __init__.py and manifest.json files which I’m not sure are on the Git repo
He seems to have added those 7 days ago
I’m still on 0.92.2 which may change the situation…
Nah… I missed renaming a few entities. Working now.
