Thanks Tom. I take it back it does seem to be working so thanks very much. Now I notice that another card has n/a in the temperature field because of the lack of value. Can I actually change the value of the “Max Temp C” attribute rather than what you have done above?
Also I was just thinking can the sensor value just get remembered? Something like:
todaymintemp:
friendly_name: "Minimum Temperature Today"
value_template: >
{% if state_attr('sensor.bom_forecast_brisbane_0', 'Min Temp C') | string not in ['unavailable', 'Unknown', 'None' ] %}
{{ state_attr('sensor.bom_forecast_brisbane_0', 'Min Temp C') }}
{% else %}
{{ states('sensor.todaymintemp') }}
{% endif %}
Yes my configuration validation is saying “Integration bom_forecast not found when trying to verify its sensor platform” since upgrade. And so the forecast just says entity not available.
I did make changes to my configuration.yaml by adding the BOM radar camera but I don’t think I broke anything there.
That was actually the first thing I tried but unfortunately it comes back witth:
Integration bom_forecast not found when trying to verify its sensor platform.
Integration bom_radar not found when trying to verify its camera platform.
Well the bom radar is now native supported in 0.92.0 - been running that since introduced in b0 and it’s working fine for the released version as well for me…
I have custom components that have no manifest. I believe from reading the dev docs this is only for core components… Other custom components are working fine without the manifest and personally I’d rather wait for the developer to comment on the issue instead of making changes that might have other unintended consequences.
it has been clarified that its is not a requirement for custom components to have a manifest.json
The documentation will be updated shortly.
There is however a requirement to have an emtpy __init__.py file for all custom components
Pretty much 1 out of every 2 restarts I get this problem:
2019-04-26 05:54:44 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform bom_forecast Traceback (most recent call last): File “/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py”, line 126, in _async_setup_platform SLOW_SETUP_MAX_WAIT, loop=hass.loop) File “/usr/local/lib/python3.7/asyncio/tasks.py”, line 416, in wait_for return fut.result() File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run result = self.fn(*self.args, **self.kwargs) File “/config/custom_components/bom_forecast/sensor.py”, line 251, in setup_platform bom_forecast_data.update() File “/usr/local/lib/python3.7/site-packages/homeassistant/util/init.py”, line 224, in wrapper result = method(*args, **kwargs) File “/config/custom_components/bom_forecast/sensor.py”, line 437, in update ftp = ftplib.FTP(‘ftp.bom.gov.au’) File “/usr/local/lib/python3.7/ftplib.py”, line 117, in init self.connect(host) File “/usr/local/lib/python3.7/ftplib.py”, line 152, in connect source_address=self.source_address) File “/usr/local/lib/python3.7/socket.py”, line 707, in create_connection for res in getaddrinfo(host, port, 0, SOCK_STREAM): File “/usr/local/lib/python3.7/socket.py”, line 748, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -3] Try again
@ BrendanMoran have you got some ideas on how to solve this problem?
I’ve tried the __init__.py and manifest.json but I’m getting the same errors as everyone else. The old “Integration bom_forecast not found when trying to verify its sensor platform.” error
I’ve moved your script into /config/custom_components/sensor/bom_forecast and in that folder are: