Not only is it not possible, it’s not necessary. It works perfectly for me from the beta.
There is no pillow issue for hassio users.
The update and requirement to install bomradarloop was continually failing for me - these steps were the only ones that worked. Wish I found them sooner. Thanks.
Love that this become an official intergration with the BOM sensor.
One feature request, could we specify the radar resolution? I’d like to see both 64km and 128km, and the component only shows 128km. For now, I need to use the old custom component.
You can specify any radar you want (except some 512km combined). All you have to do is manually specify the id, delta and frames instead of the location. https://www.home-assistant.io/components/bom/#id
WOW!!! I should really read the docs properly.
how do i get this to show up on the overview screen?
Does anyone have an issue with the Radar Image not reloading in Lovelace correctly?
I have this in my config:
camera:
- platform: bom
name: BrisbaneRadar
location: Brisbane
filename: /config/www/images/radar.gif
And in Lovelace:
hold_action:
action: none
image: /local/images/radar.gif
tap_action:
action: none
type: picture
However the image displayed in Lovelace is (Date 3/10/19)
The actual image is (Date 6/10/19)
Any ideas why Lovelace seems to be caching the image?
The updating radar image is a camera. You need to display this, not whatever gif you have in your www folder (no idea how that got there).
Try this in Lovelace:
type: picture-entity
entity: camera.brisbaneradar
show_state: false
Thanks that worked!
I got the lovelace config from another page but the www folder came from Removed integration - Home Assistant