Customising the BOM Weather and lovelace - now in HACS

Configuration
643

Awesome work guys to respond to the BOM changes good work. Upgraded ok to lastest version of HASIO. :partying_face:

2 Likes
644

Pulled the trigger and switched to this card today, now wish I had done it sooner, great work thanks @DavidFW1960.

I also replace my old BOM radar card with the tile based one from @theRat, also long overdue. And of course changed over to the @BrendanMoran API based weather feed.

I have one thing I am missing, on my main Lovelace summary page I had a small card with today’s weather summary, using the standard weather forecast card:

      - entity: weather.bom_rutherglen
        type: weather-forecast

Is there any way I can do something similar by configuring this card, without resorting to cutting code? Something like this:

image

Just an at a a glance for today that will fit with the myriad other cards on that tab.

645

I think that BOM weather component in core (as opposed to the removed sensor and Radar) still exists doesn’t it?

646

You could be right - I got so carried away with the implementation of all the fancy new stuff I may have got deletion rage
 I will check :slight_smile:

647

Nope - it’s gone.

Platform error sensor.bom - Integration 'bom' not found.
Platform error weather.bom - Integration 'bom' not found.
648

You could use “sensor.*_short_text_0”

649

I could also probably template something reasonable, it’s just that it was pretty easy to read from across the room.

I suppose I can find a way using existing data - was just hoping David would say “yeah you just do this!” :slight_smile:

Thanks guys.

650

Yeah I think you will need to template it but I’m not sure what input that simple weather card accepts
 generally needs to be in the weather domain to read it in those simple cards. I have been asked about this previously as well
 I might (no promises) take a look at this.

652

Did you sort it out? Happy to help - just ask. There was an issue with the updated package that is fixed now though (I hope)

1 Like
653

Yup - sorted it was the nodemcu pressure sensor - one sensor wrong and the whole card does not show --(4th look and i got it) - all working nicely


1 Like
654

Any thoughts on this card working on the mobile app? so far it does not seem to work (custom element does’t exist) - ok on PC browser.

655

IOS? It is working fine on that. You might try clearing the frontend cache in the mobile app
 The card has only changed by adding a couple of conditions and changing a couple of css entities
 no reason for it to not work

656

I have made a PR to add back the “old” BOM Integration exclusive of the Radar Loop:

It has been reviewed and has several other compliance issues that would require significant rework.

Ultimately, I think Brendan’s (bremor’s) integration has many advantages over the existing integration. It would however, be nice to have the BOM integration remain a core integration for those who are inclined to use it. Any consideration to add a PR to HASS?, as I am unlikely to make the changes required to fix the “old” integration as it would need rewriting.

657

It was Android version only. iOS seemed fine. All good now with a clearcache. thanks

1 Like
658

Good luck with that but it won’t happen.
You do know there is a much better radar loop already available as a custom card right?

659

I don’t use the Radar loop, given the number of issues with the existing integration it’s not going to happen without significant rework, but I can’t see why the new integration (bremor’s integration) couldn’t be merged.

660

What issues? Are you referring to the one by @theRat ?? Any issues with that are fixed almost immediately.
The existing integration was removed because it doesn’t comply with the ADR regarding web-scraping and from my reading of the PR that removed it, it was removed because they didn’t want to fix the radar part of it as well as the ADR conflict.
I don’t understand why you don’t just use the custom_component by Brendan and the Radar by Simon?

I believe Brendans plan is to submit his new BOM integration for inclusion in core but it’s less than a week old and probably needs some time to fully bed it in - but it seems to be functionally equivalent to the old core one (minus the radar). It is also Brendans call to submit/not submit to core not anyone else’s. But your PR is to restore the old one which won’t happen.

661

When I state “existing integration”, I mean the one that was removed in 0.117.

Your misinterpreting what I meant by issues, when I refer to issues, in this context I am referring to parts of code which do not meet the ADR’s. I wasn’t aware how many “code compliance issues” there were until I submitted a PR to add it back in. It’s not just the Radar Loop, 3 additional problems exist:

  1. The service specific interface code and data parsing needs to be in a standalone library published on PyPI.
  2. Web scraping is occuring in the Sensor as well as Radar
  3. The integration imports from other components.

Given this scope, its too much effort to rework it when bremor’s integration is fundamentally much better.I will be closing my PR as a result.

I believe Brendans plan is to submit his new BOM integration for inclusion in core but it’s less than a week old and probably needs some time to fully bed it in - but it seems to be functionally equivalent to the old core one (minus the radar).

That’s what I was suggesting, ultimately it would be ideal to integrate a component into HASS core when the component has been tested more.

It is also Brendans call to submit/not submit to core not anyone else’s.

I never inferred it wasn’t his call. Just like its my preference not to use custom components.

Ultimately, my PR was submitted to understand the scope of code compliance issues with the existing integration, to see the most feasible means of adding BOM back into HASS Core. I’d prefer not to add a custom component. We all have different preferences and that’s what makes the community so vibrant. I want to see Home Assistant appeal to not only those willing to run HACS and download custom components but also those who just want to use native integrations.

Finally I am aware the PR won’t be merged in its current state (well it could if I fixed the compliance issues), my intent was to understand the code compliance ramifications and the associated rework.

662

So with the new bom integration and the updated card all working for one location - was wondering how it would all go for supporting Multiple lat/long locations. Having different locations to monitor for the one HA. I think the integration will allow but is there an easier way for the card (and associated custom sensors) - any thoughts on generically supporting more than 1 location?

663

You can add multiple BOM sensors and can add multiple BOM cards as well but have to configure each one.

1 Like