Australian Weather Forecast using BOM Public FTP

cheynespc · October 9, 2018, 12:30am

Mobile version of my weather module

Lovelace code

cheynespc/Home-Assistant/blob/master/wether_station_mobile.yaml

#cheynespc wether station for mobile devices 
  - title: Weather Conditions
    icon: mdi:weather-partlycloudy
    cards:
      - type: vertical-stack
        cards:
          - type: weather-forecast
            entity: weather.openweathermap
          - type: glance
            show_name: true
            column_width: calc(100% / 4)
            title: Currently Indoors
            entities:
              - sensor.realistic_kitchen_temperature
              - sensor.kitchen_humidity
              - binary_sensor.door_window_sensor_158d0001e45327
              - binary_sensor.door_window_sensor_158d0001de8c6b
          - type: history-graph
            title: Humidity
            hours_to_show: 36

This file has been truncated. show original

sparkydave · October 9, 2018, 12:34am

I have tried your new code and it seems to be working now. Initially it got rid of the error but wasnt showing up the new forecast entities. getting it to work only happened once I removed my old code that related to the standard BOM component. I guess there was also some sort of conflict there.

sparkydave · October 9, 2018, 1:09am

any ideas why the summaries are blank?

BrendanMoran · October 9, 2018, 1:20am

Just updated the code about 30 mins ago - this problem has been fixed.,

sparkydave · October 9, 2018, 1:42am

confirmed Thanks for an awesome addition to the HA world! (pity the weather in Perth this weekend is going to be crap)

sparkydave · October 9, 2018, 1:52am

however I am seeing the below error posted to the log every time I visit my lovelace weather page:

/frontend_latest/app-d4eea1e0.js:434:176 Uncaught TypeError: Cannot read property ‘_stateDisplay’ of null

RKor · October 9, 2018, 3:55am

Thank you! I’ve been getting this same error and I thought it was because of the latest HA version.
I installed this component and updated at the same time

BrendanMoran · October 9, 2018, 4:21am

Sorry guys! I have no idea about Lovelace
Anyone is welcome to have a crack at fixing this - Pull Requests are welcome on Github

sparkydave · October 9, 2018, 4:24am

I seem to have issues if I try to run both this and the standard BOM component. The standard component wont load if this FTP one is enabled… The problem then is that I cant get the current weather data from BOM

RKor · October 9, 2018, 4:38am

Other than this small lovelace issue, it’s all working great mate!
Thank you for the prompt patch ups and replies!

tom_l · October 9, 2018, 4:41am

@sparkydave it’s working for me. I’m using the “BoM Australia Sensor” Component. Not the “BoM Australia” component.

If that’s not it, have you perhaps got duplicate entity IDs?

sparkydave · October 9, 2018, 4:45am

I’m using the component rather than the sensor but maybe I will try and swap over for the time being.

BrendanMoran · October 9, 2018, 4:58am

joelphillips:

ance Today
  icon: mdi:water
  unit_of_measurement: '%'
sensor.bom_adelaide_possible_rainfall_0:
  friendly_name: Possible Today
  icon: mdi:water
  unit_of_measurement: mm
Also for anyone having difficulty getting started I had to reboot my Pi for it to see the newly added custom component folder, rather than just restarting home assistant.

Hi Joel,

Latest version has units and icons added for ‘non friendly’ sensors.

RKor · October 9, 2018, 5:20am

Forecast for just “Sydney” city is a little vague for me, is there a way to include smaller suburbs within Sydney?
I’m assuming not because BoM doesn’t make all the stations available through FTP?

But I’m almost positive that with the official HA BoM component I had my suburb working, but that was a while ago

tom_l · October 9, 2018, 6:18am

Search for your suburb here: http://reg.bom.gov.au/catalogue/anon-ftp.shtml

RKor · October 9, 2018, 7:04am

Yeah I did, but there’s only Sydney that’s closest to where I am.
This is the component I was talking about and it worked with my local suburb station.

It works by station ID instead of Product ID?

aidbish · October 9, 2018, 7:11am

Hi Brendan.
Just updated to latest release and get the below errors in the log and also the sensors do not appear anymore. i have tried with latest and beta Home assistant and same result

2018-10-09 07:09:27 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity.py”, line 242, in async_update_ha_state
device_attr = self.device_state_attributes
File “/config/custom_components/sensor/bom_forecast.py”, line 349, in device_state_attributes
ATTR_ICON: self._bom_forecast_data.get_reading(‘icon’, self._index),
File “/config/custom_components/sensor/bom_forecast.py”, line 387, in get_reading
find_query = (_FIND_QUERY.format(index, SENSOR_TYPES[condition][0]))
KeyError: ‘icon’

Semet8 · October 9, 2018, 7:40am

Hi Guys

Set this up but when I do my validation im gettting

"Configuration invalid

Platform not found: sensor.bom_forecast"

Anyone seen this before?

tom_l · October 9, 2018, 7:53am

I’m getting the same error and no sensors with the latest version and “friendly” set true:

Error doing job: Task exception was never retrieved

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 242, in async_update_ha_state
    device_attr = self.device_state_attributes
  File "/config/custom_components/sensor/bom_forecast.py", line 349, in device_state_attributes
    ATTR_ICON: self._bom_forecast_data.get_reading('icon', self._index),
  File "/config/custom_components/sensor/bom_forecast.py", line 387, in get_reading
    find_query = (_FIND_QUERY.format(index, SENSOR_TYPES[condition][0]))
KeyError: 'icon'

Interestingly the unfriendly instance is working.

sparkydave · October 9, 2018, 8:43am

I have set up the BOM sensor and found that it doesn’t conflict with this forecast, but the BOM component does. I’m happy with the sensor but it is still worth trying to figure out why the component has conflicts. I’m happy to test.