I just used working alternatives in HACS.
0.109 my wall tablet stay very slow every time I need to turn on or off a light I need to wait x sec to start working it freezes
Same here!
Has anyone tried to check configuration validation? It is so fast that it looks like it does not actully check if everything is ok. It makes me feel uncertain 
Hm, I don’t see where you can set up triggers on that screen.What am I missing?
The Automation-link is only offering changes of battery level:
Got some problems with ikea tradfri lights and the transition command in scenes.
A scene turn_on command with transition sets the brightness of the bulbs most of the time to the minimum brightness level. Sending the command twice with a pause doesn’t work either.
But another scene command without transition works well and sets the brightness on the bulbs correctly.
Another thing is that mired isn’t saved in the scenes editor and manually set in the yaml doesn’t work as well. The bulbs behave with the last mired setting they’ve got.
I would really like windspeed back on the card. I use windspeed and wind direction a couple times a day.
Good feedback, this had already been implemented in the 0.110 dev builds a few days ago. Integrations with multiple entries will be grouped together in 0.110. So you’ll have just one ESPHome card / logo with those 4 entries (doorbell_upstairs, ensuite_dht, etc) shown inside the card in a list format. Should cut down on clutter and make things quicker to find.
3 Likes
Haha, 4 entries 
, it’s actually 41 ESPHome entries, so yeah you can see why the page was a bit cluttered.
The grouping and list sounds like a great idea.
1 Like
That’s good news; I like the direction it’s going. I feel the current proliferation of logos takes up too much screen real-estate.
FWIW, I preferred the previous consistent ‘stamp-sized’ logo-space, like what continues to be used in the Developer Tools > Info page. That’s all the logo I need to both recognize and differentiate one integration from another.
1 Like
oops, I thought it was a hue dimmer switch. Looks like those are not implemented yet. Maybe you should open an issue in HA for the Smart Button. Is it firing any hue_event when pressed?
FWIW, I had this error and I was unable to get switches to switch (they would bounce right back) and when I logged out and tried to log back in would get “something went wrong” in red on the user interface and this error would appear again in the log. Had to roll back to 0.108.9.
Let’s see if the devs will listen the feedback here. Wind speed/direction are important as well as amount of rain to distinguish intensity of the precipitation. So it is not only about “beauty” but also usefulness.
There’s custom weather cards available to use as well.
Thanks, I know. I’ve found one that seems to have everything that was available before. There are two problems though: 1) I hardly can understand the reason why the official one was downgraded from being informative to questionable “beauty”; 2) custom cards are not always maintained, so they more often ends up in more dysfunctions or bugs.
1 Like
Where can I check for these events?
At the end of the release notes: “Click here to see all changes!” But there is NO link… 
1 Like
Is it possible that Tuya-implementation is not completed yet? I see no way to assign my Tuya-dimmer to an area…
That’s a reasonable request. At the moment though there’s still a bunch of stuff planned for the Integrations page that need to be completed first before such a thing can be considered.
To give a specific example, cards are going to have slightly different styling / controls depending on the current status of an integration (some mockups here and here). So it wouldn’t really make sense to design a compact view mode until we figure out exactly which controls are needed in which states etc…
I like the idea though, but if such a thing is implemented it probably wouldn’t happen in the immediate future.
1 Like
Although I like your color-coding idea (including your suggestion to gray-scale ignored integrations), I have to admit that I prefer a tabular list-view (as currently used to display devices, entities, etc)
It’s more space-efficient and offers the end-user more management convenience such as the ability to filter and sort integrations based on their status (Discovered, Configured, Ignored, Attention, etc).
The suggestions to use color can continue to be incorporated in the list-view. The logo can be displayed in the row’s first column and either the logo’s background or even the entire row can be color-coded. I realize this functionality may be subject to the limitations of whatever UI library is currently being used to render the list-view.
2 Likes