Lovelace errors - how to troubleshoot?

I have two recurring errors in my log relating to Lovelace. I have done a lot of customising over the last few days so I don’t know where to begin finding the root. Can someone help please?

(@mayker I don’t think they are necessarily to do with the compact-custom-header but given there has been a big update recently I thought I’d tag you in case you recognised anything)


The first one looks to do with button-card @RomRider

Tried to serve up '/config/www/github/custom-cards/button-card.js.map' but it does not exist

and

http://192.168.1.25:8123/frontend_latest/app.7bd99ba1.js:2:60391 Uncaught TypeError: Cannot convert undefined or null to object

Thanks.

If you temporarily disable button-card by commenting it out in your resources section do both errors go away? If they do, button-card is most likely the culprit. I would use this method of temporarily commenting out custom cards one by one to find where the errors spring from.

1 Like

You can safely ignore this one, the map file is for debugging purpose. I’m going to fix it in the next release. See Tried to serve up '/config/www/github/custom-cards/button-card.js.map' but it does not exist · Issue #157 · custom-cards/button-card · GitHub

For the second one, it’s probably not related to button-card, however does it disappear if you comment out the button-card? Also, do you embed button-card in some other cards, like vertical-stack-in-card? If so: GitHub - thomasloven/lovelace-card-loader

Also, check this out.

@RomRider, @mayker,

Thank you both!
With judicious use of commenting out views (another advantage of using !include ), navigating through tabs and refreshing the log I have narrowed down the problem to three views, only one of which uses vertical-stack-in-card but at least I have an idea of where to look.

Yes I do and I’m looking at card-loader now.

Thanks for the pointers…