Issues with missing card after upgrade to v7.0.0

[craigwitter]

After upgrading to version 7.0, I went to upgrade my YAML to use custom:advanced-camera-card instead of custom:frigate-hass-card. The interface said that this module could not be found. Upon troubleshooting, I could see that HACS did create a new resource /hacsfiles/advanced-camera-card/advanced-camera-card.js?hacstag=394082552700, but this doesn't seem to exist in that location. It looks like HACS is still downloading it in /hacsfiles/frigate-hass-card/. Manually adding a resource pointing to /hacsfiles/frigate-hass-card/advanced-camera-card.js?hacstag=394082552700, seems to fix the issue.

Thanks for your hard work.

Craig

[dermotduffy]

On my test instance, I also see that see HACS has made that resource (and it doesn't exist). I am guessing HACS will keep doing this until the repo name is processed, which may be weeks or months away (not under my control).

Having said that, the old resource location continues to work for me, even if I use custom:advanced-camera-card, this is as I would expect as it's coded to work both ways. So I think the puzzle here is why did that not appear to work for you? Unless you had removed the frigate-hass-card resource first manually?

[craigwitter]

It was strange, as I checked the cards after the upgrade and they still worked using the old frigate name. It wasn't until I completely removed both entries in resources, removed the card in HACS and installed it again (manually added frigate-hass-card location back) that I was able to use the new name like the breaking change notification said to do. Prior to this, it just showed that the resource didn't exist when I tried to manually use the new name. I should have noted the value for /hacsfiles/frigate-hass-card/ of the js file in here. If it was pointing at the frigate-hass-card-js file, would that have caused the old name to continue to work? Thanks again, Craig

…

On Mon, Feb 10, 2025 at 10:29 AM Dermot Duffy ***@***.***> wrote: On my test instance, I also see that see HACS has made that resource (and it doesn't exist). I am guessing HACS will keep doing this until the repo name is processed, which may be weeks or months away (not under my control). Having said that, the old resource location continues to work for me, even if I use custom:advanced-camera-card, this is as I would expect as it's coded to work both ways. So I think the puzzle here is why did that not appear to work for you? Unless you had removed the frigate-hass-card resource first manually? — Reply to this email directly, view it on GitHub <#1883 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADDNYG4P35YDDDRTJJPWU3D2PDAWJAVCNFSM6AAAAABW2YPN3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBYGQYDEMBQGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dermotduffy]

If it was pointing at the frigate-hass-card-js file, would that have caused the old name to continue to work?

Yes (but the new name should have worked also, and does in my test instance).

[Phantomx2]

Also having issue with 7.0.0, at first it was not available like @craigwitter mentionned.
Then it randomly became available so I was able to presse the update button to update all of my cards.

but now going back to my home assistant I see that it became unavailable again.

[quantummobile]

No luck for me also - after update to 7.0.0 - "Custom element doesn't exist: advanced-camera-card" error.

[Phantomx2]

Update: cleared my browser cache and it's working again, also had to clear cache on the mobile app.

[quantummobile]

Clearing browser cache doesn't help. I wonder if the folder name should still be "frigate-hass-card" or should it be already "advanced-camera-card" instead?

[Phantomx2]

Clearing browser cache doesn't help. I wonder if the folder name should still be "frigate-hass-card" or should it be already "advanced-camera-card" instead?

I have both

[quantummobile]

I even tried to do clean install - removed old version completely and installed from scratch with HACS. No luck.

[quantummobile]

What am I missing here? Everything looks to be in place.

[dermotduffy]

@quantummobile That looks correct to me (assuming you have the rest of the files in the advanced-camera-card directory) Suggest opening devtools (F12) in your browser and see if something is not loading when you refresh the page.

The v7.0.0 code supports using either the new custom:advanced-camera-card or the old custom:frigate-hass-card configuration. As long as the card is loaded from somewhere, either configuration should work.

[gieljnssns]

This was my problem, the hacstag was wrong

After changing the tag in Dashboards -> resources

the card works again

[quantummobile]

This was my problem, the hacstag was wrong

After changing the tag in Dashboards -> resources

the card works again

This! Many thanks for the clue - got it working :) Though shoulnd't the proper tag be set upon the installation of the card?

[dermotduffy]

Huh, wow. Good find!

Not sure why this is only impacting some people. Perhaps depends on whether or not you still have the old frigate-hass-card entry?

This! Many thanks for the clue - got it working :) Though shoulnd't the proper tag be set upon the installation of the card?

Yes. I would expect HACS to "get this right", but I am guessing this relates to the fact that the HACS maintainers have not yet processed the card rename (they seem to do these every few weeks in batches). Once that's done, I would hope this issue goes away, but will have to test.

[tir599]

I was having the same issue and nothing seemed to work until I added:

live_provider: jsmpeg

to each camera on my card. I feel like this is more of a work around and not a fix. If it matters I'm still on Frigate 13.2.

[fedd]

I have the view working in web and failing to find the asset in the companion app

-- if mentioned as "advanced camera card". Does work in the app if it's "frigate"

[askpatrickw]

Just giving a +1 on this, looking forward to the resolution.

[hocuspocus69]

It's show as 6.51 version if i modify with advanced..no custom card..,wait for hacs mainteiner

[sbeier23]

I "solved" it for myself with the following steps:

1. removed from my installation
2. looked into the resources and removed all remaining references to either frigate-hass-card and advanced-camera-card
3. got back to hacs and reinstalled the card
4. switched to all dashboards, where the card was installed and did the "upgrade"

maybe this solves the issue for some of you as well

[thomasddn]

After changing the tag in Dashboards -> resources

If we change this manually, will this impact future updates?

[thomasddn]

Changing the tag in Dashboard > resources only helped momentarily for me. Reloading the page with Dev Tools open (and Disable cache enabled) I see the following requests:

• /hacsfiles/frigate-hass-card/frigate-hass-card.js?hacstag=394082552651 (200)
• /hacsfiles/advanced-camera-card/advanced-camera-card.js?hacstag=394082552 (200)

So both script files are still being loaded. Are they interfering with each other?

The card is now loading correctly again, after updating the resource tag on the frigate-hass-card as well. But maybe the best workaround for now is the one mentioned by @sbeier23.

EDIT: The error is back, so changing the hacstag does not work for me. Tomorrow I will try sbeier23's workaround.

[rsiv]

I had the same Custom element doesn't exist error in the iOS app after upgrading and changing the card name.
The desktop browser app worked fine.

I reinstalled the card in hacs and then cleared the iOS app frontend cache:
Settings > Companion App > Reset frontend cache
Might also need to pull down the view to force a reload.
Not sure if reinstalling was necessary but now it works.

[myevit]

same. fixed by manually updating Resources to correct hacstag=394082552 for new v7. after uninstall/reinstall integration with HACS and deleting old folder in www

/hacsfiles/advanced-camera-card/advanced-camera-card.js?hacstag=394082552

[hocuspocus69]

sbeier23 solution solved for me!

[ptruman]

Chiming in that my hass docker update & frigate update broke this today (move to advanced-camera-card had already happened)
I'm also getting errors via browser to my hass via Android client and Android (Crhome) web UI - however, loading the web ui in Incognito mode in Chrome (on Android) - works.... (normal mode doesnt, even though I've deleted stored data for my site, and cleared Chrome cache)

PC is fine "as is"

Edit : Archving/Unarchiving and then pausing/unpausing the Android app has freed up the app.

[Obermayr-M]

Had the same issue.

Fixes which did not work:

• Cleaning cache helped temporary, after a while same issue.
• Correcting hacstag=394082552 in lovelace resources did not help.

Fixes that finally worked:

• Uninstall advanced-camera-card; deleting homeassistant/www/community/frigate-card folder, reinstall advanced-camera-card finally worked, even hacstag=391082552700 at the moment. Looks like hacstag does not affect.
  --> everything fine (browser & companion app)