I’ve just been through all the integrations with the “Configure” option I have. Pretty sure none of them use multi step config flows.
I may have found an example, trying to break my HA good and proper now.
1 Like
Yep that worked 
At least home assistant is still running 
That was a bonus, it gave me a scare though as one restart took about 5 minutes.
I didn’t have any luck figuring it out and gave up for now.
1 Like
Hey all. @DavidFW1960 and I are working towards a major rewrite/cleanup of this card. One of the main goals is to provide a completely graphical configuration so you don’t need to edit reams of yaml. It is still a work in progress, but so far the top part and slots are coming along. As of right now this is what the dev version of the card looks like.
And the config editing screen. This will be changing to use a multipage setup as we need more space for other options.
The overall intention is that everyones config will continue to work. There are some undocumented options that I would like to remove to clean up the code a lot. The options all of the form
alt-*: some_entity. We need to know if anyone is actually using these. They are only implemented for some of the slots and the code for them is a dogs breakfast. If no one responds saying they use them I will be getting rid of them. As I said they are not documented anywhere (that I have looked) so I expect they aren’t being used.
5 Likes
Today a bunch of progress was made on getting the graphical config working in what I hope is a sensible way. You can now show/hide different parts of the card. It is currently still only done from the top to the slots part (forecast section tomorrow maybe).
If anyone is interested in being an alpha tester please comment or contact us. In particular I am keen to get feedback from anyone that uses any weird settings in the current card, is pedantic about the look of the card, or has feature requests/enhancements they would like to see.
For those interested in helping we have a repo on github that you can add as a custom repository in HACS.
2 Likes
Id like to encourage anyone using this card to join the alpha for the new one. Its going to be awesome and we would really appreciate feedback
3 Likes
Yay I can post again. I got blocked for being to keen!
So now for some updates.
For the aussies here the bom integration v1.1.8 has been released. There have been no changes made to the beta.
As @DavidFW1960 said we are really keen to get some people involved in testing the new card. We are adding a lot of new options (and hopefully getting rid of some that we feel are deprecated, tell us if we are wrong).
There are so many new options. You can decide to show/hide any section, we have added a title section, forecasts can now be shown vertically. Lots of new options. Here is an image of what the vertical layout looks like at present (still a work in progress), but feedback now will help guide the progress.
Tell us what you like/hate. We understand that everyone has their own feelings of what their own weather should like. With this new card we are looking to build on the knowledge learnt from the previous version and take it to a new level.
1 Like
Is the new card specific to BOM, or will it be generic?
It will be generic (as I understand it) but you will need some specific sensor entity_ids, e.g. for the forecast days the min, max and rain sensors will be required to end in _1, _2, _3 etc for the next n days forecast at the bottom of the card.
Currently, @BenCranston and I have the existing card working pretty well with the NWS integration. It still has a boatload of YAML feeding it (~300 lines). NWS has it’s own quirks that need to be accommodated, but I’d like to take a look at the new version to get an idea where it’s going. The timing might be right for what Ben has in mind.
Our plan and design criteria is that it will work with any current config. It will also continue to work with YAML but has a GUI config as well. The GUI config will make certain assumptions regarding dy numbers so you only configure the first day. There will also be a lot of new features, more slots, the ability to have 7 days forecasts, a vertical layout if you don’t like horizontal for the forecasts and summare data for those days as well in vertical mode.
2 Likes
The development version of the card is here https://github.com/Makin-Things/makin-things-weather-card
You can add that as a custom repo in HACS too so you will get updates.
1 Like
@pocket The summaries and info from @DavidFW1960 and @tom_l is accurate. I wanted to add some new features to the existing card, but parts of it weren’t particularly well written and to add the graphical config it really needed to be converted from javascript to typescript. So after some discussion I decided to start a rewrite utilising the knowledge of the existing card, mostly contributed by David.
If you do install the card from the repo David posted feel free to create issues. There are generic templates there, but at the moment I don’t care if you skip those. Issue #1 is a summary of things that I know we need to do before the card is considered ready. We also have a group chat that we can add people to that just want to discuss requirements, features etc. It would be good to have some non-aussies providing a different perspective.
I’ve only had HA for a week and installed the BOM integration today going straight for this updated version of the card.
I have a question. Is this designed to work only with Bureau of Meteorology integration sensor or be more flexible and pull the data from anywhere?
If it’s the former why not just have a setting to set the base sensor name and then set all the other entities based on that?
How do you set the entity names for the forecast days? Or (after reading issue #1) are they what you call “slots”?
EDIT: Never mind I’ve found ‘entity_forecast_icon_1’, ‘entity_summary_1’, ‘entity_forecast_low_temp_1’, ‘entity_forecast_high_temp_1’, ‘entity_pop_1’, ‘entity_pos_1’ in weather-card.ts… although I don’t know what pop and pos entries are for.
Cheers
ps. if you need help with this I am probably able to assist
Some of the other entities use templates and this card is designed to work with any weather provider that can provide the sensors
Firecast sensors are not slots. They have a whole GUI configuration section (the bottom one)
I recommend loads ng it and trying it and it should be pretty clear. The templates we use are in ny repo linked in the original post.
I’d be happy to contribute what I can. If your group chat is at a reasonable time of day on my end (New York time zone), I’d like to attend. Please PM the details.
I could also write up some things regarding how the NWS presents its data sets, which seem to be not as rich as the BOM sets. They require shifting the input assignments to the BOM card three times each 24 hours. All forecast temperatures are either daily high or nightly lows, and all changes happen when data arrive from the integration as fresh entities. Also, the forecasts get more verbose as they get more current, so I’m hoping you’ve considered a way to bust the 255-character limit for the forecast detail entities.
Unfortunately, the US uses different API endpoints for certain data such as fire risk and UV data, so there would need to be another integration to handle those (out of scope for this effort). In the meantime, it’d be nice to gracefully handle their absence. There are other quirks and details that are artifacts of the API service, and I could explain those as well, if only to make sure the card behaves in a benign way.
BTW, the end product looks very nice. Kudos for the implementation. I’ll create a new dashboard and take a test drive.
1 Like
these are optional in the card anyway… If you don’t want them use a different slot configuration. Also the card doesn’t care one whit where the data comes from or what the source is. You are ultimately passing the entity to the card so as long as it’s an entity in Home Assistant it can be displayed. We are not doing any API calls ourselves. In the case of BOM we are using an integration that grabs data from BOM but this card is not BOM specific… In fact it was originally forked from the original which used Dark Sky.
1 Like
@pocket, I have sent you an invite to join the chat. It’s just a thread that has people that are interested in having some input and helping with testing.