-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom element doesn't exist (but only on a tablet) #114
Comments
All my mobile devices are Android and I don't have this problem. It does sound like a cache problem. I'm not sure if removing the app also removed the cache. Did you try manually clearing the cache? |
Hi Famous Wolf. Firstly, thanks for making such a lovely and clear way of displaying information on home assistant. I also have the exact same issues described above. I can see the calendar working as intended on both a Samsung s21 HA app. As well as perfectly in a browser. However, I have a Lenovo m11 tablet that I get the custom element doesn't exist bug. The tablet is brand new and not sure why it is not able to display the calendar as intended. Any suggestion would be really helpful. Thanks |
I have same issue on my android tablet. But the problem is only in the companion app, if I use browser on the tablet, the card shows correctly. |
Hi, been trying everything - cache, reinstalling app. It seems like perhaps its something to do with HA itself because i saw search results for the same issue on other elements too sometimes. Its an android related issue for sure. But no one seems to know how to fix it. Zero consistency saddly. |
Hi,
This works fantastic, but for some reason my android tablet running the HA app doesnt think this element exists. It works perfectly fine on my mac, but I cant understand why this wont work. I completely reinstalled the app to make sure the cache is cleared BTW... I see this issue sometimes happens with tablets with other integrations but it doesnt seem like there's a real fix for it (other than clearing cache which only helps in some cases). Could this be due to a dependency which doesnt work on an android?
thanks!
The text was updated successfully, but these errors were encountered: