Whent back to 115.5. Then everything is fine again. From what i could tell when i had removed all card exept for whats needed to run homekit card with popup windows then my front page still vanish from time to time.
So sins 116.4 wont work with the setup that has worked with the code basicly copied from the default page i recon something is wrong with it on 116, Is a stated before in the thread first it was the header card. And then came update 0.116.4 and then the problem was back.
I suggest no one update to 116.0-4 if you want the best experiance stay at 115.5
@DBuit Needs to address the issue, the following is from the release notes of Home Assistant.
Breaking Changes
Below is a listing of the breaking change for this release, per subject or integration. Click on one of those to read more about the breaking change for that specific item.
Custom Lovelace Cards
This release contains breaking changes for custom card developers, check the developers blog for more information.
If you have a custom card that stopped working this release, please report this with the custom card author.
so the problem with the initial load of the card is probably an home assistant bug in how card are loaded.
There are some issues on the hass frontend github starting with this one:
there are related issue that are solved and merged and will be available in next version of HASS.
We need to wait i think hope that will fix the problem
Ive just updated to 117.
I had a error with swipe card, So removed it.
But still a no.
Something still making it go invisible sadly And still no error what so ever for me atleast.
(allso uppdated hacs and browser_mod to latest)
It didnāt change in 0.117, but I found a work around in some discussion from other cards facing this problem: I insert this card in a horizontal stack and first tests look promising
Try setting panel:true -> to false on your view. for me the card does load, and can you guys @Jimmy_Berglund and @claudiovillani58 test this is that also works for you?
I know it doesnt look the way it should be but than we know a but more about the problem.
Maybe this could explain why I never had this problem (still donāt have it). My default screen (Overview which is generated by HA) is still there so I guess thatās what you mean by first page. I have 3 other dashboards which all use HomeKit-panel and they all work fine, even while setting some of the HomeKit-panel screens as default dashboards for certain devices (wall mounted tablet and mobile default to these dashboards whereas all other devices like a PC will default to the Overview default dashboard (although it is heavily modified but does not use HomeKit-panel)