Australian Weather Forecast using BOM Public FTP

Share your Projects!
223

BOM radar camera is out! Hell yeah!

1 Like
224

It seems to be a bit picky with the radar ids you can use. No problem with the 128km radar ids but the 512km composites return only a black image (the id, frames and delta were correct). The old custom component did not have this issue.

225

I didnā€™t even know there was a custom component! I would have been straight on to itā€¦

226

Confirm these steps fixed mine too. Ta.

227

Mine is working fine with both the name (Melbourne) and id (for the 64km close up).

228

Try it with the 512km radar for Melbourne (ID ā€˜021ā€™). Make sure you include the quotes around the id number. Thatā€™s important, particularly for IDs with leading 0s.

229

Confirm 512km radar for Melbourne (ID ā€˜021ā€™) no-worky with:

- platform: bom
  id: '021'
  delta: 360
  frames: 6
  name: 'Radar 512'
1 Like
230

Adding your experience here would be appreciated:

231

No Prob. Done.

1 Like
232

Mucking around with some macro/micro radar combinations to go on my permanent display. Working well. The animated dark sky card uses the bom forecast as per an earlier thread. I made it compact, cause I found I didnā€™t really look at the other stuff.

Is this the right thread for this? Just point me elsewhere if thereā€™s a better BoM radar oneā€¦

Something like this in lovelace.

- elements:
    - camera_image: camera.radar_256
      entity: camera.radar_256
      style:
        font-weight: bold
        height: 40%
        left: 20%
        top: 20%
        width: 40%
      type: image
  camera_image: camera.radar_64
  type: picture-elements

PNG
PNG1842Ɨ977 453 KB

233

Sorry for the abandonware everybody, wish I had time to worry about this but Iā€™m sure you can all figure out this new custom component re-jig.

3 Likes
234

@Mahko_Mahko The old thread was here: Australian Animated Radar using BOM Public FTP Though now it is a built in component might be worth stating a new one.

@BrendanMoran Creating a custom component isnā€™t just for Christmas :slight_smile: :dog2:

But seriously, its all working with the ā€œgreat migrationā€ and manifest instructions.

Lodged an issue fort the New camera though.

1 Like
235

The manifest instructions only apply to inbuilt components - not custom componentsā€¦

236

Thatā€™s not what I have found in practice. I tried the blank __init__.py file first. Made no difference. Sill got warnings/errors. Adding a manifest file stopped this occurring for three different custom components. Including this one.

1 Like
237

I have also found the same with helping folks here, sometimes the __init__.py file doesnt fix and only a minimal manifest.json file works

238

If thatā€™s the case and they really are creating the right file I still think the dev needs to give input as to the recommended solution. Manifests are for core components according to the docs.

239

they are optional for custom components

awarecanYesterday at 2:40 AM
@aidbish , this manifest.json IS OPTIONAL for custom component

240

i had to query the devs yesterday as one doco said optional and the other said required, an update to the doco that said required has been put through to say they are optional for custom components

241

Just dropping by to say thank you for the component.
I got caught out for an hour by the 0.92 requirement change listed above about 1 day ago, but after realising I installed and it ran fine.

242

Worked for me, many thanks!

1 Like