Likely a community integration that ignores warnings to add a manifest. Contact the developer.by commenting on this GitHub issue gfor the integration.
EDIT: someone submitted (an ignored) PR that could have resolved the issue. Try sommenting there too.
to be fair, it is written explicitly in the docs at Buienradar - Home Assistant
The sensor entities are disabled by default and should be enabled before they will be updated with data.
this worked!
True, missed that, obviously.
No, it is not solved. Now HASS is restarting again and again in an endless loop. For example, I can monitor to log file, and the log restarts every few minutes.
Here is the supervisor log
21-06-06 11:54:37 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-06-06 12:02:07 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
21-06-06 12:02:07 INFO (MainThread) [supervisor.homeassistant.core] Successful started Home Assistant 2021.6.1
21-06-06 12:02:08 INFO (SyncWorker_1) [supervisor.docker.interface] Cleanup images: ['homeassistant/raspberrypi3-64-homeassistant:2021.4.6']
21-06-06 12:02:59 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-06-06 12:03:03 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-06 12:05:12 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-06-06 12:05:13 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-06 12:07:25 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-06-06 12:07:25 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-06 12:09:02 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-06-06 12:09:03 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-06 12:11:04 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-06-06 12:11:04 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-06 12:13:06 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-06-06 12:13:06 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-06 12:14:43 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-06-06 12:14:43 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-06 12:16:17 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-06-06 12:16:18 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-06 12:17:50 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-06-06 12:17:50 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-06-06 12:19:08 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-06-06 12:19:09 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
``had changed to the partition install of HA OS and been running fine. Up to 2021.6 I fear (can not prove it, and the power status integration is always OK…)
since I upgraded to 2021.6, I saw this.
I ordered the powered USB hub now, to be sure I always have enough power, but mention it here, because, well before 2021.6 no issues arose, and maybe others can chime in on it, or benefit from the experience and found solution to the fix (that is to say, the hub arrives tomorrow, so for now it is an alleged fix 
)
Please create a bug ticket for the missing “default” theme in the frontend repo. I don’t think that this is by design.
Although, on second thought I am not sure what the use case really would be for that. Basically any custom theme overrides settings from the default theme, so simply adding the default theme to that list will probably not work.
I have exactly the same problem with Xiaomi B1 curtain covers.
Also no cure with version 2021.6.2.
The curious thing is that it is possible to control them in z2m by the state buttons,
and also that other entities of the cover appear in HA, but not the essential close or open entities.
My Tasmota based light bulb used to have an attribute rgb_color in 2021.5 and earlier. This attribute seems to be missing now.
I use this in an automation to test if bulb is currently green which no longer works:
{{ states.light.bulb01.attributes.rgb_color == ( 0,255,0) }}
These are the attributes is has now. I don’t have the list of attributes prior to 2021.6 without reverting back.
min_mireds: 153
max_mireds: 500
effect_list: 0, 1, 2, 3, 4
supported_color_modes: color_temp, rgb
color_mode: color_temp
brightness: 255
color_temp: 489
effect: 0
friendly_name: bulb01 bulb01
supported_features: 4
Anyone else having this issue?
Yes, it overrides/adds flavour. But there is currently no chance to have a complete defined default skin selectable.
Usecase for example: I have a blue/black skin, but for e.g. the Chrome-toolbar extension, I want to assign the complete white and clear default skin. Not possible, even it exist anywhere, because I’m able to select it in the user-profile as shown in the pictures. But I cannot select it there.
For me it is not clear, why it is defined anywhere, but not selectable.
And no, I cannot easily select another bright theme, because - as you said - if you set a theme for a view “on top” of a theme from the user, it is added/merged. So in such cases, I would like to assign the available complete default theme.
I still don’t get your use case. I assume this mentioned Chrome extension is a separate user session (otherwise please provide some more context; no idea what you are talking about TBH)? So you can just set a different theme to be used for the login. No need to specify anything on individual Lovelace card level?
For me it is not clear, why it is defined anywhere, but not selectable.
As I said, even if it were selectable, I am not sure if it would work technically currently (but probably could be made to work with some effort). And that again is probably why, it is not selectable in the first place.
See this one. Found this from the community highlights newsletter. No, no other session, so the user session skin is taken. That’s the problem.
And here I thought, that there is a complete defined default theme, which is then not merged with other ones and selectable.
O.k. When it is whyever not available and there is no explanation for this, I have to deal with it as I did here
I only came again on this, because of the news about the dark skin in this release.
Is there a way to disable polling for an integration that is not available in the UI? I’m trying to get Alpha Vantage to poll less frequently in order to stay within the threshold of a free account.
Anyone else having a problem with Zigbee covers, please post in the following issue to make HA experts aware of it:
It’s already 2021.6.2 and no fix!
I downgraded to 2021.5.5 to solve the issue
And I have no idea, what I could do to upgrade in the future to a newer version.
Regarding ecowitt integration broken -
Likely you are encountering this issue: #43
Manually adding the version to the manifest.json file worked for me.
It’s not a core add-on but a 3rd party one so probably why nobody looked at it.
Issue has been fixed on the zignee2mqtt site
If the add-on isn’t yet updated check the post near bottom from kkoenk about how to update.
Since 2021.6.0, I have created and successfully used a theme including both dark and light modes.
Waited long time for this option! Thanks!!!
However, since 2021.6.1 or 2021.6.2, I’m not sure, the option to select Auto/Light/Dark in the Profile disappeared, when selecting my theme.
Anything I miss?
Thanks, indeed this works for me as well, great.
That was it, I simply added default_config instead, thanks!