indeed, like that …
I have exactly the some problem with the zones.
I had some limited success using preloader but was still having some cards that would not show up on one view and would work fine on another, which was truly confusing me. All of the settings were the same, and the views were generally the same too. Site cache refreshes and restarts of HA didn’t seem to make a difference.
I started to look at the possible differences in the views while both were using panel = true I decided to change it to false on the one that wasn’t working and after a refresh the card loaded! Of course I wanted to make sure so I changed it back to true to check and again, the card loaded correctly persisting even after a few refreshes.
I’m not sure what this corrected, whether it was the preloader or something in the core that needed to be reloaded (can’t be the browser cache because I cleared that earlier in troubleshooting) but it seems to have worked for me so I’d suggest trying it at least. Can’t hurt and might help.
UPDATE: Didn’t work on a set of pages where the broken one didn’t have a panel setting. But adding a few more preloader lines and a number of successive browser refreshes with a single instance did work. My assumption is that my browser was holding ui-lovelace.yaml in cache on the one page (I was using VScode add on for editing). So slowly but surely getting all my cards back.
Ironically, not a single issue with the rest of 0.107.x beyond Lovelace. Even got my issue fixed with cert expiry so at least I don’t have to keep setting the days after every restart. LOL
Correct me if I’m wrong about this and I very well might be…
but does it make any sense that we need a custom component (preloader) to make the built-in cards show up correctly?
I’m seeing references to needing it for cards like conditional, markdown, etc.
What if for some reason development stops on that custom component?
EDIT: apparently I was wrong… 
3 Likes
As far as I know this is a bit of a special case. If these cards are placed inside a custom card, i.e., I experienced this issue with markdown and gauge cards inside a vertical-stack-in-card card, but gauge cards on their own were fine.
Seems like they could just a lovelace option to remove the optimization rather than have the need for yet another custom plugin.
1 Like
The same error with Asus ac66uB1 Merlin 384
Ok, from the above discussion it sounded like some of the built-in cards were having issues too. Maybe the conditional card?
Ouch. 250 dollars in Google API charges in a single day after upgrade to 0.107
Something wrong with google_travel_time platform
Yeah, I think it applied to any cards that could be nested inside other cards.
Mine does not run as root and works fine.
Same error here. AC86U, Merlin 384.15
The package aioasuswrt needs to be updated from 1.2.2 to 1.2.3
But what should we put there instead of /bin/entry.sh ??
I’m having the exact same problem, my HA will not start after updating.
No that doesn’t help, already an PR for that, but didn’t resolve
@SteveDinn is correct, the issue stems from custom cards not using the new helper functions to embed cards in themselves, or using the hack to place different element types elsewhere. e.g. a markdown card inside an entities card.
I’m trying to call a different Lovelace view for my google hub using 0.107 using the cast.show_lovelace_view and putting the view path as tablet (that being the new view set up and the view path is pulled from the raw config editor) but it errors with unable to find a view with path tablet. What should I be using?
I was able to stream my ezviz camera directly via IP. Now I tried the integration and it is not working. see the log:
Platform error: camera
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/config.py", line 752, in async_process_component_config
platform = p_integration.get_platform(domain)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 277, in get_platform
f"{self.pkg_path}.{platform_name}"
File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/ezviz/camera.py", line 5, in <module>
from haffmpeg.tools import IMAGE_JPEG, ImageFrame
ModuleNotFoundError: No module named 'haffmpeg'
can you help me? Many thanks
I intalled the component via pip. Now I see the camera in states but it doesn’t stream anything:
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/srv/homeassistant/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
resp = await handler(request)
File "/srv/homeassistant/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware
return await handler(request)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/http/ban.py", line 72, in ban_middleware
return await handler(request)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/http/auth.py", line 127, in auth_middleware
return await handler(request)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/http/view.py", line 123, in handle
result = await result
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/camera/__init__.py", line 492, in get
return await self.handle(request, camera)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/camera/__init__.py", line 527, in handle
return await camera.handle_async_mjpeg_stream(request)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/camera/__init__.py", line 390, in handle_async_mjpeg_stream
return await self.handle_async_still_stream(request, self.frame_interval)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/camera/__init__.py", line 381, in handle_async_still_stream
request, self.async_camera_image, self.content_type, interval
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/camera/__init__.py", line 196, in async_get_still_stream
img_bytes = await image_cb()
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/ezviz/camera.py", line 219, in async_camera_image
ffmpeg = ImageFrame(self._ffmpeg.binary, loop=self.hass.loop)
AttributeError: 'NoneType' object has no attribute 'binary'
wow. that’s how big guys make money… 8()
on a serious note - what did they charge you for?
Currently running 105.5. If I upgrade to anything over that, I get a strange problem where I lose connection to Home Assistant after a while. i.e. I will try to connect via DDNS or local IP and cannot connect. Only way to resolve it is to remove the Power from my Raspberry Pi to restart it. I then get connection for another few hours or a day before losing it again. I did have this exact same problem after an upgrade some time ago but it seemed that it was resolved on a subsequent upgrade! But here it is again… Running the latest HassOS 3.12.
Tried it a couple of times now. Also tried the latest 107 with the same problem. Went back to 105.5 again.
I have an Odroid XU4 spare and was wondering if I should give that a trial as this problem is most annoying!
Any ideas?
Cheers
Will