Migration of BOM baseline to NWS -- current issues
See original GitHub issueHi David.
As I posted, I’m currently migrating from DarkSky to NWS and using your weather card as one of choice. It’s mostly working. Here’s a current screen snippet:
There are some obvious issue, but I’ll address what I hope is the low-hanging fruit piecemeal. Here are some configuration entries for the card:
-
The value for atmospheric pressure has been truncated. While the correct value was available, … …the value was rounded, snipping two significant digits. Also, the units are wrong. This could be an artifact of HA, so I’ve submitted a bug report (third of its kind; prior submittals were allowed to expire).
-
I’ve attempted to fill up the slots and keep the data aligned–specifically the
sun next
andsun following
entries. There are two visible issues: the absence of thevisibility
entry and/or the failure of theempty
directive to leave an empty slot. Here’s the snapshot of the sensor: FYI, I’ve also attempted to replace thevisibility
sensor withempty
(i.e., having two empties in successive slots), but that didn’t realignsun following
withsun next
. -
There’s a missing prominent display of text near the top of the card for the current wx condition. In this case, I think it should be the one that selects the icon. Am I making the wrong assumption?
I think the above is enough as a start. There’s some more, but I’d like some time to investigate how NWS condition entities are rendered to text and BOM icons. I might be able to sort that out without your help.
Thanks in advance. Respectfully, Rob
Issue Analytics
- State:
- Created 2 years ago
- Comments:30 (14 by maintainers)
Top GitHub Comments
@Sudo-Rob I know the issue is closed (sorry for waking a dead issue David) but would love to work with you getting the card to work with NWS. I have no way to reach you outside of your GitHub id. My profile has my email address. Hopefully we can make a connection.
ok. 30000 lines of errors isn’t fun