zha-network-card
zha-network-card copied to clipboard
Cannot Find Card
Hi, on the new versions you cannot add this to the raw code, you have to use the Lovelace config section. After adding it, I get an error when trying to create the card saying it cannot find custom:zha-network-card, I have of course verfied the js resides in my www folder, and have added it as /local/zha-network-card.js to the resources config section. Any suggestions please?
I am having the same issue.
Probably #12?
Probably #12?
That worked perfectly! Thanks
This doesn't seem to have fixed it? I assume all I need to do is change the top two lines to the one in the comment, but it still isn't working. The post also referes to a gz file, is this needed as I've not got one and isn't mentioned in the install instructions?
Probably #12?
That fixed it for me.
same issue, can't get the card working: Custom element doesn't exist: zha-network-card.
Not sure if this is related but also can't display card.
Get following error when attempting to add card in Lovelace:
Cannot read property 'map' of undefined
type: 'custom:zha-network-card'
HA Version: 0.111.4 (Running in Docker on Ubuntu 18.04)
Resource is visible in Lovelace Dashboards/Resources: /hacsfiles/zha-network-card/zha-network-card.js JS file is in directory.
Same issue here. Installed via HACS (so it put it in the Resources tab in Dashboards). I'm running 0.113.3, in Docker on Ubuntu

Same issue here. Installed via HACS (so it put it in the Resources tab in Dashboards). I'm running 0.113.3, in Docker on Ubuntu
![]()
I'm having exactly the same problem, I installed via HACS, the file exists and the resource info looks right in the Lovelace Resources Section.
The suggested amendments for Ticket 12 are already a match for the .js file and yet I still get the error: 'Custom element doesn't exist: zha-network-card.'
I got it working, I think it may have been related to my use of SSL certificates.
I removed configuration of the certificates in the configuration.yaml and set them up in the nginx plugin instead.
Suddenly it started working